BEA GDP source profile

Status: accepted under DEC-0027 after source, contract and consumer review. See the acceptance record (repository reference) for exact pins. This is a separate operational contract for six retained historical GDP cells. The accepted CBP profile and SC/RE/DE obligations remain unchanged. Alethic owns generated models, application review, import, GraphQL, the workbench and deployment.

BEA01 Finite native admission

The complete fixture contains these six assertions from BEA Table 3, line 1, 2024 Q4. All use Table 3, relationship rId4, and xl/worksheets/sheet4.xml. Source identity and edition are essential because coordinates repeat across workbooks.

BeaNativeCell retains exact token strings, native type, style index, formula state, value presence, workbook part, cell, source quarter token and supporting cell locators. No numeric coercion, reformatting or formula evaluation is permitted. The uncomputed XLSX display remains explicitly null. Header and merged-span source material is retained separately in evidence/selected-cells.json; that file is a projection of the accepted locator record, not original publisher bytes. Other workbook cells remain unbound supporting source material.

The validator permits nonempty subsets of this six-cell universe, with exactly one interpretation per supplied native assertion. It rejects new captures, editions, cells, unbound supplied cells and duplicate assertions. A subset is not a complete historical information set. Service query/result envelopes must disclose their requested selection and actual membership under the existing discovery obligations.

BEA02 Meaning and representation

H6 uses the C2/D3/E4/H5 header path; N6 uses I2/J3/K4/N5, together with merged spans. The profile preserves GDP level, quarterly reference period, quarterly-flow construction, current-dollar versus chained-dollar valuation, and seasonal adjustment as distinct fields. Annual-rate expression belongs to representation, separately from the quarterly period. The 2017 reference year applies to chained-dollar presentation, not a classification vintage. It is explicitly inapplicable for the selected current-dollar presentation.

Unit, USD interpretation and the exact scale string 1000000000 retain field-level source material and mapping-inference origins. No numeric conversion is performed. Literal table caution text uses explicit_field; normalized interpretations do not become explicit fields merely because their source is authoritative. The Q4 and Q4 r tokens and A79 revision note are retained. A81's chained-dollar caution remains visible. A80's real-GDI footnote does not attach to GDP line 1 through its line number.

National GDP context does not establish a complete accounting-territory contract. Required geographic-boundary, production-boundary, sector-scope, classification, historical-method and economic-precision disclosures remain unresolved. A generic US label cannot resolve them. A current explanatory page would not by itself prove unchanged historical methods. The finite profile permits unspecified or not_inspected for these gaps, with a reason; it admits no invented inapplicability or resolved values for them. The general source material shape retains conflict support, but no conflicting interpretation is adopted in these six fixtures. Adding new source material or resolving these gaps requires a separately reviewed release.

BEA03 Independent display and clocks

The PDF display belongs to a separately pinned PDF, source locator and retained transcription. For B05 H6, preserve XLSX 29719.599999999999 alongside B08 PDF 29,719.6, page 8, Table 3, line 1. Neither replaces the other. The extra XML digits do not establish greater economic precision. No generic Excel display formatter was run. The fixture records the earlier dossier's PDF reading and its limits instead of claiming a new rendering.

The releases are advance BEA25-02 on 30 January 2025 at 08:30 EST, second BEA25-05 on 27 February 2025 at 08:30 EST, and third BEA25-10 on 27 March 2025 at 08:30 EDT. Publication instants normalize those explicit zones to -05:00, -05:00 and -04:00 and cite PDF page 1. Original capture-completion clocks remain separate, with their exact strings. HTTP dates are not publication dates. Mapping-review time is another distinct clock. The same value or cell address never merges release editions.

No unqualified query selects nominal, real or an edition by default. Consumers may expose the bounded candidates or request clarification and must retain all qualifiers and gaps. Any temporal selection policy must be explicit and scoped to the supplied releases. This release asserts no globally latest observation, exhaustive archive or complete as-of set.

BEA04 Review and operation boundary

The six example bindings start as proposed for Alethic's operational review. Acceptance of this profile establishes its bounded contract and reviewed documentary interpretation; it does not authenticate an application actor or automatically publish registry records. Reviewed, withdrawn and superseded states require a scoped receipt, reviewer, review time and decision reference. The validator checks receipt shape; Alethic checks authorization and the actual decision before assigning operational authority. Preserve earlier versions.

numeric_availability is supplied, identity_assessment is not_established, and permits_numeric_operations is false. Values remain distinguishable publisher assertions. There is no nominal/real equivalence, confirmed method continuity, arithmetic, seasonal conversion, deflation, annual-rate inversion, chaining, interpolation or new EQUA engine. Existing accepted SC operation rules are not implemented or expanded by this release.

BEA05 Consumer and release obligations

Use schema.json with the offline validator in scripts/bea_profile; both are required before admission or mutation. The schema is Draft 2020-12 with only local references and closed named objects. All exported types have a Bea prefix. Five source material shapes are pinned copies from CBP 0.1.0, with renamed types/references; they have no implicit shared runtime identity. The accepted CBP schema, validator and release are unchanged.

Generate Pydantic and derive public projections from this schema. Do not maintain independent economic models. Keep nullable fields, strings, unknowns, source material, editions and precision disclosures intact. Exact source clocks and URIs must survive generation/projection. Generated Pydantic alone is not a substitute for authoritative validation: the previous consumer probe accepted integer 0 for a false-only field. JSON Schema must reject that input. Alethic's additive BEA import and complete GraphQL/workbench journey remain consumer gates.

The source manifest pins identity metadata, selected native records and edition/display associations. The release manifest pins its payload and validator. Hash declarations and green validation do not authenticate raw bytes, source interpretation or reviewers. Consumers must verify actual retained artifact bytes against the handoff and authorize source admission. The review record distinguishes prior capture/replay source material from newly executed checks.

Run the focused checks with uv run --locked python -m unittest discover -s tests -p test_bea_profile.py. Validate a bundle with uv run --locked python -m scripts.bea_profile PATH_TO_BUNDLE. Run pnpm check before delivery. These are development preservation controls, not a held-out extraction benchmark or proof of broader BEA coverage.

The acquisition-owner handoff is pinned in evidence/acquisition-handoff.json. Its independent review checked 14 local authority pins, nine source-entity metadata records, six identities, 45 unique supporting-cell projections and 15 retained GCS object references. Root rechecked all 14 local pins plus the handoff and review receipt. Those checks did not reread the raw cloud archive, run a new replay, refresh publisher responses or verify Alethic cloud access. The original accepted capture/replay source material remains the source-body authority. A later consumer read must select the exact archive generation, verify its bytes/hash, then verify individual B01-B09 member hashes. Member hashes are not independent GCS generations.

Subsequent review source material records actual local workbook/member verification and temporary consumer generation/roundtrip/projection probes. The frozen source manifest describes checks at candidate creation; later checks are recorded in the acceptance record. Consumer preflight requires format-first generation, explicit treatment of incidental string wrappers and null-only output fields, and the existing exact-integer public scalar policy. The accepted schema and validator are unchanged; these are downstream implementation obligations.