Regulatory state, not filing alerts

Most EDGAR systems answer one question: did a filing happen?

Regulatory state answers a better question: what does the filed record say now, and did that record change?

That distinction is the difference between collecting document events and maintaining a record that can support decisions later.

A filing is only the event

A filing event tells you:

• a document arrived
• at a specific time
• with a form type
• with an accession number

Those facts matter, but they do not say whether the document is now the current record, whether it amended a prior filing, whether it superseded an earlier disclosure, or whether an expected filing is missing.

A notification feed can be correct and still leave the team with stale state.

State is the maintained record

Regulatory state tracks what the filed record says after the system accounts for:

• the latest annual and quarterly filings
• relevant 8-K events
• amendments after publication
• exhibits that were added or replaced
• expected filings that did not arrive
• predecessor records and timestamps

The output is not a sentiment score, investment opinion, or claim that a disclosure is correct. It is a maintained view of the filed record and the evidence behind that view.

Where filing alerts break down

A common failure pattern is simple:

1. A 10-Q posts.
2. A team updates its model or spreadsheet.
3. A 10-Q/A arrives later.
4. Part of the workflow keeps using the older version.

Another pattern is quieter:

1. An issuer misses an expected filing window.
2. No alert fires because no new document arrived.
3. A downstream process keeps treating the old record as current.

Event systems only react when something arrives. State systems also track whether the record is current, amended, stale, or degraded.

Transitions matter more than raw alerts

An alert might say:

New filing detected.

A state transition says:

The maintained filing record changed because the latest 10-Q was amended after publication.

Examples of useful transitions include:

• CURRENT -> AMENDED_AFTER_PUBLICATION
• STALE -> CURRENT
• LATEST_10Q_UPDATED
• EXPECTED_10K_MISSING

Those labels are easier for people to review and safer for agents to consume than a stream of raw document notifications.

Materiality comes later

Teams often ask whether a filing change is material. That is the right question, but it is not the first one.

Materiality is a judgment layer on top of state. A team cannot evaluate materiality cleanly until it knows:

• which filed disclosure is current
• whether a prior record was superseded
• what changed
• when the change became knowable
• which source documents support the update

State is the substrate. Materiality, analytics, and opinions sit above it.

Evidence makes the record defensible

Maintaining state is not enough. The state update needs a receipt.

A defensible state transition should include:

• source accession numbers
• source URLs
• publish and retrieval timestamps
• predecessor pointers
• method notes
• delivery history

That evidence lets a reviewer ask why a team believed a record was current at a specific time and get a reconstructible answer.

What a scoped outcome should define

A scoped production outcome should define:

• the issuers or entities covered
• the filing types in scope
• the cadence and trigger rules
• the state model
• the evidence included with each update
• the delivery surface for humans and agents

It should not claim that filings are correct, that future amendments will not happen, or that a disclosure change is automatically material.

The job is narrower and more valuable: preserve the timeline of what was filed, what changed, and what the team could know at the time.

Why this matters for agents

Agents do not need a loose pile of PDFs. They need a maintained state record with health and evidence signals.

An agent can use state safely when it can check whether the record is:

• CURRENT
• AMENDED_AFTER_PUBLICATION
• STALE
• DEGRADED

Without that context, an agent may cite an old filing, miss an amendment, or act on a stale assumption.

Common questions

Why are filing alerts not enough?

Filing alerts tell a team that a document arrived. They do not preserve which disclosure is current, whether an amendment superseded a prior document, or what evidence supports the current record.

What is a regulatory state transition?

A regulatory state transition is a recorded change in the maintained filing record, such as a latest 10-Q update, an amendment after publication, or an expected filing becoming stale.

Does regulatory state decide materiality?

No. Regulatory state preserves the current filed record and the evidence behind changes. Materiality is a later judgment made by a team, model, or review process.

What should an agent use regulatory state for?

An agent can use regulatory state to know whether a filed record is current, amended, stale, or degraded before citing it or triggering downstream work.

Related reading

• What is regulatory state?: a plain definition for investment, risk, and agent workflows.
• Data reconciliation in finance: why source, timing, definition, and method explain number differences.

See it as an outcome

• SEC filing monitor: track 10-K, 10-Q, 8-K, and amendment state.
• Disclosure interpretation state: monitor interpretation changes across filed disclosure.