US securities examination readiness
Answers "if I generate the SEC/FINRA examination package now, what will be in it and what will it have to disclose?" WITHOUT creating a report job.
It returns COUNTS, PRESENCE and DISCLOSURES, never evidence rows. The rows come from the compliance report facade (POST /api/v1/compliance/reports with regulator=ussecurities) and only from there, so this is not a second export path.
It exists because the facade cannot answer this question: asking it means creating a job, spending one of an Evaluation tier's three daily reports, and waiting on an async render, purely to learn whether the package is worth generating.
SCOPE: the summary covers the requesting TENANCY, with two DISCLOSED exceptions rather than two silent ones (ADR-064 section 4). The RLS-gated sources - the approval queue and the signed decision chain - are additionally bounded by ORGANIZATION, because both enforce that boundary in the database. The configured supervisory controls are scoped by organization outright, because that is the scope the engine that enforces them reads them under; a tenancy-scoped inventory would publish a set of controls that is not the set being applied. The scope field states all three in one sentence.
AUTHORITY: gated on tenant-wide read authority, the same gate as the evidence and compliance exports. It returns aggregates rather than rows, but an aggregate over audit_logs still describes whole-tenant activity.
Enterprise Feature. Community builds register no route (404).
Request
- Base URLhttps://orchestrator.getaxonflow.com
- Authnone declared
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Response
Examination readiness summary
Example response
{
"window_days": 90
}Changes
No recorded changes to this operation across all 1 revision of this API.