Skip to main content
View source

Authoritative Overlay

View as Markdown

The authoritative_overlay node is a pipeline filter that cross-checks extracted financial numbers against the live US SEC EDGAR company-concept API for a configured CIK. It forwards an answer only when it matches an official value for the requested filing period. Part of the Audit-grade financial extraction node suite.

What it does​

  • Input: Pipeline answers (or text containing a JSON payload).
  • Process: The node queries https://data.sec.gov/api/xbrl/companyconcept/CIK{cik}/us-gaap/{concept}.json and compares the extracted number against measurements that match the requested filing period.
  • Output:
    • If the extracted number matches an official value for that period, the answer is forwarded downstream (once).
    • If there is a mismatch, missing period, failed lookup, or unrecognized regulator, the node abstains by dropping the answer and logging a warning.

Lanes​

Lane inLane outDescription
textanswersA JSON payload arriving as text is parsed, cross-checked against EDGAR, and forwarded on answers when it matches.
answersanswersAn upstream answers payload is cross-checked against EDGAR and re-forwarded on answers when it matches.

Configuration​

See services.json for node configuration schemas.

The live services.json test block hits data.sec.gov and is excluded from the default builder nodes:test run (opt in with ROCKETRIDE_INCLUDE_SKIP=authoritative_overlay). Unit tests under nodes/test/authoritative_overlay/ mock the API and do not require the network.

Notes​

Supported regulators​

Currently supported regulators:

  • US SEC (EDGAR)

Period-scoped matching​

A match is not "this number appears somewhere in the company's filing history." The answer payload must include at least one filing-period selector: form, fy, fp, start, end, or frame. An optional unit filter narrows measurements but does not count as a period. All provided filters are applied together. When a filing contains multiple durations ending on the same report date, such as quarter-only and year-to-date totals, provide start or frame; otherwise the node abstains rather than accepting either value. It also abstains when multiple filings publish conflicting values for the selected period, because the payload does not identify a filing version. Typical payload:

{
"concept": "AccountsPayableCurrent",
"value": "$69,860,000,000",
"form": "10-K",
"fy": 2025
}

Without a period the node abstains. A value that is correct for a 2010 10-K will not verify a 2025 extraction.

[!NOTE] Strict Matching: The node uses exact matching (math.isclose with rel_tol=1e-9). This ensures that only exact financial figures are passed through. Filings restated to the nearest thousand will not match a value extracted to the unit.

Schema​

FieldTypeDescriptionDefault
authoritative_overlay.cikstringCompany CIK
The SEC Central Index Key for the company.
"320193"
authoritative_overlay.profilestringProfile
Overlay profile
"basic"
authoritative_overlay.regulator_typestringRegulator Source
Which regulator database to cross-check against
"sec"