Policy-driven AI agent platform
Screens the packet
"Can every over-limit packet get one outcome and a memorandum?"
FitsMany over-limit packets, hedge claims to test, and a desk that must defend each outcome with cites.
Over the cell, (a)(1) quantity-match holds, evidence complete
Chicago Board of Trade Wheat (W), March 2026.
Blotter line 317 CFR 150.2(a)
Labeled futures-equivalent of the labeled aggregation group.
Blotter line 317 CFR pt. 150, App. E p.380
Inventory 1,020 + fixed-price purchases 610, in contract equivalents.
Inventory book p.1Purchase schedule p.2App. A (a)(1)
Blotter, futures-equivalent, inventory book and purchase contracts agree.
Packet index PGG-0304
Over the cell, non-enumerated hedge claim, no recognition on file
Chicago Board of Trade KC HRW Wheat (KW). Not combined with W or MWE.
Blotter line 117 CFR 150.2(a)
Labeled futures-equivalent of the labeled aggregation group.
Blotter line 117 CFR pt. 150, App. E p.380
Economic appropriateness and recognition stay open for a human.
Claim write-up p.1App. A to pt. 150
No Commission or exchange recognition of this strategy in the packet.
Packet index BMC-030417 CFR 150.3(b), 150.9
At or under the cell, evidence complete, hedge claim not needed
Minneapolis Grain Exchange Hard Red Spring Wheat (MWE).
Blotter line 217 CFR 150.2(a)
Labeled futures-equivalent of the labeled aggregation group.
Blotter line 217 CFR pt. 150, App. E p.380
A leftover hedge claim does not block an in-limit book.
Claim write-up p.1
Over the physical cell, no hedge claimed
Physically settled NG, across exchanges and OTC swaps.
Blotter lines 1 to 4App. E p.381 fn. 2
Separate limit. Never netted against the physical book.
Blotter line 5App. E p.381 fn. 2
Over the physical cell with no hedge that can fire.
Packet index CEM-0304
Required evidence missing, fail-closed to deny
The blotter lists W positions with no labeled futures-equivalent.
Blotter p.1Packet index OGP-0304
Missing required evidence fail-closes to deny.
17 CFR pt. 150, App. E p.380
The hedge cannot allow a book whose size is not labeled.
Inventory book p.1App. A (a)(1)
Fictional firms and positions shown for illustration. Limits are the federal spot-month levels in Appendix E to 17 CFR part 150.
Commodity position-limit and hedge-exemption screening compares a trading group’s futures-equivalent position with the federal spot-month limit for that contract, then locks one outcome: in-limit, allow as hedge, over-limit deny, or refer. On MightyBot each rule is a plain-English policy, and every check keeps its citation, the observed value against the threshold, and an evidence pointer.
One packet, followed from the blotter to the exemption memorandum. Prairie Gulf Grain Co., a short CBOT Wheat (W) book in the March 2026 spot month.
Chicago Board of Trade Wheat (W), March 2026. Spot month: yes. Side: short. Labeled futures-equivalent: 1,540 contracts.
Wheat owned in store: 1,020 contract equivalents. Fixed-price purchase contracts in wheat: 610 contract equivalents. Unfixed-price purchases of 240 contract equivalents are listed separately.
Appendix A (a)(1): hedges of inventory and cash commodity fixed-price purchase contracts.
Compare the labeled futures-equivalent of the labeled aggregation group to the 1,200-contract spot-month cell for W. Keep W, KW and MWE separate. Over the cell, a short book can be allowed as a hedge when it does not exceed owned inventory plus fixed-price purchase contracts in the same cash commodity. Missing required evidence is a deny.
| Input, as of Mar 4, 2026 | Contracts | Source |
|---|---|---|
| Labeled futures-equivalent, short | 1,540 | Blotter line 3 |
| Spot-month cell, W | 1,200 | 17 CFR pt. 150, App. E p.380 |
| Over the cell | 340 | |
| Wheat inventory owned | 1,020 | Inventory book p.1 |
| + Fixed-price purchase contracts | 610 | Purchase schedule p.2 |
| Unfixed-price purchases (not (a)(1)) | 240 | App. A (a)(1) |
| Quantity the hedge can cover | 1,630 |
MightyBot pre-screens commodity books against federal spot-month position limits and hedge-exemption evidence, locking one official outcome with an exemption memorandum and audit trail.
What the desk already has
What the agent does
What the desk receives
Every check records the 17 CFR cite, evidence pointer, observed value, threshold, result, and whether a rule or a reviewer computed it.Recorded at every step, from input to output.
Over-limit desks that need a locked outcome and a defendable trail on wheat and natural-gas spot-month books.
The packets from the panel, run through the same checks in the same order. Exactly one outcome fires for each.
| Check | Prairie Gulf | Bluestem | Red River | Calloway | Ostrander |
|---|---|---|---|---|---|
| Contract in scope | W | KW | MWE | NG physical | W |
| Required evidence | Complete | Complete | Complete | Complete | FE missing |
| Spot-month cell | Over | Over | In-limit | Over | Not tested |
| Hedge (a)(1) or (a)(2) | Match | Not enumerated | Not needed | None claimed | Cannot fire |
| Recognition on file | Not needed | None | Not needed | None | Not needed |
| Locked outcome | Allow as hedge | Refer | In-limit | Over-limit deny | Over-limit deny |
Federal speculative spot-month limits are the hard ceiling on a wheat or natural-gas book. The desk still has to compare the labeled futures-equivalent of the labeled aggregation group to the frozen cell for that contract, then decide whether a hedge claim can carry an over-limit book. Wheat contracts stay separate. Natural-gas physical, cash-settled, and economically equivalent swaps are never netted.
When that work is manual, over-limit files sit while someone re-checks the cell. Vanilla inventory hedges wait behind claims that need a reviewer. Missing blotter or futures-equivalent still gets a pass. Dispositions go out without the cite, the observed value, or the evidence pointer. Policies written in plain English and compiled into deterministic policy evaluation close that gap for the over-limit desk.
All three compare a position to its limit. Only one tests the hedge evidence and writes the memorandum.
Policy-driven AI agent platform
"Can every over-limit packet get one outcome and a memorandum?"
FitsMany over-limit packets, hedge claims to test, and a desk that must defend each outcome with cites.
Position-limit monitoring system
"Will we see when a position nears its limit?"
FitsPositions change through the day and the main need is limit alerts across accounts.
Spreadsheets and manual review
"Can our analysts keep checking each packet by hand?"
FitsA few contracts and rare over-limit books.
| Criterion | Screens the packet | Watches the limits | Leaves it to analysts |
|---|---|---|---|
| Position against the limit | Yes: Each contract's spot-month cell | Yes: Calculated against stored limits | No: Rechecked by hand |
| Contracts kept separate | Yes: Wheat separate, gas never netted | Yes: Per configured limit | No: Depends on the spreadsheet |
| Hedge evidence | Yes: Tested, judgment calls referred | No: Reviewed outside the system | No: Read file by file |
| Outcome per packet | Yes: One locked outcome | Partly: Alert, decision made elsewhere | No: Analyst's call each time |
| Audit trail | Yes: Cite, value, threshold, pointer | Partly: Alert and position history | No: Notes and email |
Over-limit desks and hedge-exemption files need a locked outcome and a memorandum the desk can defend. Agents on the MightyBot platform screen the packet against the spot-month cell and the hedge evidence, then leave the cite trail behind.
See the platform screen your own packets against the spot-month cell, with the cite behind every check.