Skip to content
Use case

Spot-month limit screening with one locked outcome for every packet

Wheat and natural-gas books compared to the federal spot-month cell, hedge evidence tested, and an exemption memorandum written with the 17 CFR cite for every check.
Runs on the MightyBot platform.
March 2026 spot month

Prairie Gulf Grain Co.

Allow as hedge

Over the cell, (a)(‌1) quantity-match holds, evidence complete

Aggregation group
AG-PGG-01
As of
Mar 4, 2026
Outcome
ALLOW-AS-HEDGE
  • Contract Pass
    Observed
    W, spot month
    Threshold
    One in-scope contract
    Margin
    Match

    Chicago Board of Trade Wheat (W), March 2026.

    Blotter line 317 CFR 150.2(a)

  • Spot-month cell Over cell
    Observed
    1,540 short
    Threshold
    1,200
    Margin
    +340

    Labeled futures-equivalent of the labeled aggregation group.

    Blotter line 317 CFR pt. 150, App. E p.380

  • (a)(‌1) quantity-match Match
    Observed
    1,540 short
    Threshold
    Max 1,630
    Margin
    90 spare

    Inventory 1,020 + fixed-price purchases 610, in contract equivalents.

    Inventory book p.1Purchase schedule p.2App. A (a)(1)

  • Required evidence Pass
    Observed
    4 of 4
    Threshold
    All present
    Margin
    Complete

    Blotter, futures-equivalent, inventory book and purchase contracts agree.

    Packet index PGG-0304

Fictional firms and positions shown for illustration. Limits are the federal spot-month levels in Appendix E to 17 CFR part 150.

What is commodity position-limit and hedge-exemption screening?

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.

From packet to memorandum

How MightyBot screens position limits

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.

Packet PGG-0304As of Mar 4, 2026

Position blotter, aggregation group AG-PGG-01

Chicago Board of Trade Wheat (W), March 2026. Spot month: yes. Side: short. Labeled futures-equivalent: 1,540 contracts.

Cash inventory book and purchase schedule

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.

Exemption claimed

Appendix A (a)(‌1): hedges of inventory and cash commodity fixed-price purchase contracts.

Labeled field the test readsQuantity tested

Step 1

  • Packet ingested: blotter, labeled aggregation group, labeled futures-equivalent, inventory, fixed-price purchase or sale contracts, and a recognition letter when one is claimed.
  • Numbers are copied as labeled. A missing futures-equivalent is never filled in as zero.
  • The unfixed-price purchases are read too, and kept out of the hedge test in step 3.

Position-limit screening at a glance

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.

01Inputs

What the desk already has

  • Position blotter
  • Labeled aggregation group and labeled futures-equivalent
  • Cash inventory
  • Fixed-price purchase or sale contracts
  • Natural-gas settlement bucket
  • A recognition letter when a non-enumerated hedge is claimed
02Execution

What the agent does

  • Compares the labeled futures-equivalent to the frozen spot-month cell for that contract
  • Tests vanilla same-commodity inventory and fixed-price hedges
  • Fail-closes on missing evidence
  • Leaves non-enumerated and appropriateness questions open for a reviewer
03Outputs

What the desk receives

  • One locked disposition (in-limit, allow as hedge, over-limit deny, or refer non-enumerated)
  • An exemption memorandum
  • An exportable audit trail
Audit trail

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.

Best for

Over-limit desks that need a locked outcome and a defendable trail on wheat and natural-gas spot-month books.

Outcomes

The same checks on every packet, one locked outcome

The packets from the panel, run through the same checks in the same order. Exactly one outcome fires for each.

March 2026 spot month, results by packetIllustrative example
CheckPrairie GulfBluestemRed RiverCallowayOstrander
Contract in scopeWKWMWENG physicalW
Required evidenceCompleteCompleteCompleteCompleteFE missing
Spot-month cellOverOverIn-limitOverNot tested
Hedge (a)(‌1) or (a)(‌2)MatchNot enumeratedNot neededNone claimedCannot fire
Recognition on fileNot neededNoneNot neededNoneNot needed
Locked outcomeAllow as hedgeReferIn-limitOver-limit denyOver-limit deny
Fictional packets. Cells: 1,200 for each wheat contract and 2,000 for the NG physical bucket, Appendix E to 17 CFR part 150.

Why the order matters

  • Missing required evidence is checked first and fail-closes to deny.
  • A book at or under the cell is in-limit, whatever hedge claim rides with it.
  • Over the cell, only a vanilla quantity-match or a current recognition of this strategy can allow it.
  • A hedge claim that still needs a human is referred, not decided.

What stays with a reviewer

  • Whether the hedge is economically appropriate.
  • Whether it sits in a physical marketing channel.
  • Whether a non-enumerated strategy should be recognized.

The Problem

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.

  • 01Over-limit backlogBooks sit on the desk while someone re-checks the spot-month cell
  • 02Mixed hedge filesVanilla inventory hedges wait behind claims that need a reviewer
  • 03Contract mixingWheat books get collapsed; natural-gas buckets get netted
  • 04Thin evidenceMissing blotter or futures-equivalent still walks through as a pass
  • 05Missing audit trailDispositions go out without the cite, the observed value, or the pointer
Who uses it

Each desk gets the part of the screen it acts on

  • Over-limit deskOne locked outcome per packet and a memorandum the desk can defend.
  • Hedge-exemption analystVanilla inventory and fixed-price hedges cleared by quantity-match, so review time goes to the claims that need judgment.
  • Commodity trading complianceThe cell, the hedge tests and the fail-closed evidence rules written in plain English and versioned.
  • CFTC-facing risk teamAn exportable audit trail with the 17 CFR cite, observed value, threshold and evidence pointer for every check.
Compare

Spreadsheets, position-limit monitoring systems and a policy-driven platform compared

All three compare a position to its limit. Only one tests the hedge evidence and writes the memorandum.

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.

Position-limit monitoring system

Watches the limits

"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

Leaves it to analysts

"Can our analysts keep checking each packet by hand?"

FitsA few contracts and rare over-limit books.

Criterion Screens the packetWatches the limitsLeaves 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
95%
Time reduction in productionBuilt Technologies - Production Deployment
MightyBot platform

Screen every packet against the cell and the hedge evidence

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.

  • Policies in plain EnglishThe desk writes the cell, the hedge tests and the fail-closed evidence rules. The platform compiles them into deterministic execution.
  • One locked outcomeIn-limit, allow as hedge, over-limit deny, or refer non-enumerated. Exactly one per packet.
  • Judgment stays with peopleEconomic appropriateness, the physical marketing channel and non-enumerated recognition go to a reviewer.
  • A trail the desk can defendEach check keeps the 17 CFR cite, observed versus threshold, the evidence pointer and who computed it.
FAQ

Frequently Asked Questions

It is a CFTC pre-screen of a trading packet against federal speculative spot-month limits. The agent on the MightyBot platform compares the labeled futures-equivalent of the labeled aggregation group to the frozen cell for that contract, then locks one official outcome and writes the exemption memorandum. The first surface is core wheat and natural-gas contracts.

The official outcome is one of four codes: ALLOW-IN-LIMIT (in-limit), ALLOW-AS-HEDGE (allow as hedge), DENY-OVER-LIMIT (over-limit deny), or REFER-NON-ENUMERATED (refer non-enumerated). In-limit means the labeled futures-equivalent is at or under the frozen spot-month cell. Allow as hedge means the book is over the cell and a vanilla same-commodity inventory or fixed-price hedge quantity-match holds, or a current recognition of this strategy is on file. Over-limit deny means required evidence is missing or the book is over the cell with no hedge that can fire. Refer non-enumerated means the book is over the cell and a hedge claim still needs a human.

One locked outcome and a defensible memorandum per packet

See the platform screen your own packets against the spot-month cell, with the cite behind every check.