A Section 16(b) short-swing demand letter is typically built by a plaintiff firm scanning Form 4 filings for a lowest-price-in, highest-price-out match, and the recipient, whether the insider or the issuer's general counsel, has had no deterministic free tool to independently recompute that number. This pack turns the recipient side into evidence. Stage 1 recomputes the matchable-pair profit figure from a declared transaction list using the same maximal-recovery construction the demand letter relies on, and compares it against the claimed figure where one is supplied. Stage 2 wraps that receipt in a shareable evidence bundle stamped with the tier label the caller's declared gate results qualify it for. Every transaction is declared by the caller: the pack reads no Form 4/5 filing and no brokerage record, so it evidences whether the declared list produces the claimed figure, never that the declared list is complete or accurate.
recompute_section16b_profit{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "recompute_section16b_profit",
"arguments": {
"insider_ref": "SYNTH-INSIDER-001",
"issuer_ref": "SYNTH-ISSUER-CO",
"currency": "USD",
"insider_status": {
"officer_or_director": true,
"ten_pct_owner": false,
"foreign_private_issuer": false
},
"transactions": [
{"txn_id": "txn-1", "type": "buy", "date": "2026-01-10", "price_minor_units": 1000, "shares": 100},
{"txn_id": "txn-2", "type": "buy", "date": "2026-02-10", "price_minor_units": 1200, "shares": 50},
{"txn_id": "txn-3", "type": "sell", "date": "2026-04-01", "price_minor_units": 2000, "shares": 150}
],
"demand_letter_claimed_profit_minor_units": 140000
}
},
"id": 1
}
assemble_ocg_evidence_bundle{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "assemble_ocg_evidence_bundle",
"arguments": {
"artifact_tool_id": "art-573-section16b-short-swing-profit-recompute",
"artifact_execution_hash": "<execution_hash from Stage 1>",
"gate_results": {
"envelope_well_formed": true,
"execution_hash_recomputes": true,
"chain_execution_valid": true,
"mandate_gates_valid": true,
"compute_integrity_proof_valid": false
},
"proof_refs": []
}
},
"id": 2
}
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.
Question: An issuer officer bought in January and sold in April. What does the recompute disgorge if the sale had settled in August?
Run the AINumbers MCP tool `run_chain` with {"chain":"sec16b-early-warning-pack"} and read `art-573-section16b-short-swing-profit-recompute.total_profit_minor_units`.
Re-run with `inputs` for `art-573-section16b-short-swing-profit-recompute`, reusing the values that result echoed, with `transactions` changed so the sale date moves to 2026-08-01, past six months. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/sec16b-early-warning-pack.html