SEC Company Monitor

Give an AI one exact company and a bounded period. Get an explicit SEC monitoring DAG, evidence-linked signals, and a machine-verifiable execution receipt.

This is the first outcome-oriented frontdoor above the 36 SEC Suite backend Actors. It turns CIK + period + limits into:

• parallel 8-K event, filing-change, and corporate-action runs;
• optional exact-name enforcement matching;
• deterministic, versioned compatibility projections in a disclosed staging Dataset;
• a final disclosure-risk feed;
• one receipt with every Actor, input hash, dependency, charge ceiling, run ID, Dataset binding, result count, and coverage gap.

planOnly is the default and calls nothing. Its small starter plan uses only the corporate-actions source and reserves its 0.26 USD ceiling plus the 0.51 USD required by the final risk-feed Actor if you later choose execute (0.77 USD total). Add 8-K events or filing changes deliberately; each adds a 0.50 USD child-run ceiling. Optional exact-name enforcement adds

0.26 USD

The workflow makes zero internal LLM calls. compact output omits long evidence bodies while retaining IDs, rules, provenance, and gaps, so an AI can usually carry less context than with raw filings. Actual token savings depend on the model, tokenizer, selected evidence, and prompt; no fixed percentage is claimed.

Safe plan

{
  "executionMode": "planOnly",
  "requestId": "apple-monitor-plan",
  "company": {"cik": "320193"},
  "periodFrom": "2026-01-01",
  "periodTo": "2026-07-31",
  "sources": ["corporateActions"],
  "maxCorporateActions": 5,
  "maxSignals": 10,
  "outputMode": "compact",
  "maxWorkflowChargeUsd": 0.77
}

The Default Dataset contains final secDisclosureRiskSignal records. EXECUTION_RECEIPT, SUMMARY, and ERRORS are stored in the default KVS.

The Actor is implemented, locally tested, and uploaded as a private beta. Its safe plan-only Cloud run passed; two execute acceptance paths stopped at the explicit cross-run Dataset boundary and produced no final signal. Selecting Apify Cloud storage inside A03 did not bypass LIMITED_PERMISSIONS: a child run cannot read the parent run's staging Dataset. The local Monitor now keeps that Dataset as the disclosed auditable projection and sends the same bounded records through A03's native inline input contract. A fresh Cloud acceptance is still required, so the Monitor is not promoted, public, or monetized. See ./docs/session-handover.md for the exact build, run, receipt, and cost evidence.