Downloads
Selected JSON fields
The JSON export uses nested camelCase fields. The CSV export uses flattened snake_case columns and prefixes analytical columns with analysis_. The downloadable JSON Schema is the exhaustive contract for the JSON dataset. Evidence is a separate top-level collection so a public artifact never silently changes the signed source or analytical record.
The context watchlist is published under its own versioned JSON and schema. It is joined to directive pages through editorial relevance IDs, but it is not embedded in the directive/evidence contract and never contributes an evidence count.
The normalized relationship CSVs flatten explicit source-role assignments and recorded cross-reference edges already present in that JSON contract. They are not replacements for the complete JSON: dependency statements without a related directive remain in the JSON and interface. In the analytical table,record_directive_id identifies the record carrying the statement; it does not assert workflow direction, sequence, ownership, or implementation status.
Product and data-contract versions are tracked independently. Release 0.3 added this interface and normalized CSVs without changing the canonical JSON shape. Data-contract version 0.3.0 adds the evidence layer's review commitment: a next review date, a committed list of public sources with last-checked dates, and a sweep log inside evidenceScope. The separate watchlist contract begins at version 0.1.0.
| Field | Meaning |
|---|---|
id | Stable analytical identifier; not an official identifier |
label | Signed section or subsection label |
locator | Signed section and source PDF page |
excerpt | Short independently reviewed transcription |
leadOrgIds | Organizations explicitly directed as leads |
collaboratorOrgIds | Organizations explicitly named as collaborators |
mentionedOrgIds | Other bodies or role groups explicitly named in the directive |
timing | Source phrase, transparent calculation, and what it applies to |
analysis | Separately stored summary, themes, outputs, dependencies, and questions |
evidenceScope | Selective-coverage statement for the reviewed public-artifact layer |
evidence | Dated public artifacts with provenance, directive links, locators, review dates, and limitations |
directiveLinks | Explicit artifact-to-directive relationships with excerpts and page locators |
watchlist.scope | Selective-context scope for the separate, non-evidentiary research watchlist |
watchlist.items | Official context sources and publication checkpoints with editorial relevance links and evidence-boundary notes |
watchlist.nextReviewOn | Planned date for checking whether a more informative or qualifying public artifact has appeared |
dataReviewedThrough | Latest manual review date across the exported directive and evidence records |
lastReviewedOn | Date a source or evidence record was last manually checked |
Reuse and corrections
Original structured analysis and documentation are available under CC BY 4.0. Code is licensed under the Apache License 2.0. Government source material remains subject to its own terms and is not relicensed here.
Corrections should identify the directive, evidence, or watchlist ID; public source; exact locator or boundary statement; and proposed replacement. Source, evidence, watchlist, and analytical changes are reviewed as separate concepts.