Home › Contracts

Canonical registry · reviewed against repository sources

Contracts

Contracts define the promise at a handoff: grain, required fields, allowable transformations, gates, owners, and change policy. They do not prove that the current runtime satisfies that promise.

01 Governed data contracts

These three contracts have both a prose specification and a machine-readable gate file. Gold Permits is adopted; Silver REM and ARS remain drafts pending their own sign-off criteria.

Gold Permits

8020rei.gold.permits
Adopted · v2.2.1

The cross-trade permit event spine for model training and client lists. It governs permit grain, scalar First American linkage, classification, temporal anchors, owner occupancy, coverage, freshness, audit artifacts, and promotion.

Parties
Data Engineering produces; modeling and list build consume.
Executable gates
63 total: 32 enforce, 23 shadow, 8 dry run.
Implementation evidence
A local Gold v2 candidate emits the gate inventory. Production producer and consumer parity is still open.

Caveat: contract v2.2.1 is adopted. gates.yaml v0.2.2 is a local amendment awaiting producer acknowledgement; the adopted gate baseline is v0.2.1. Local evidence is not production conformance.

Silver Real Estate Master

8020rei.silver.real_estate_master
Draft · v1.0

The existing First American property-state spine used by features, occupancy checks, address joins, and coverage accounting. Its tolerances are grounded in the measured April 2026 baseline.

Parties
Data Engineering produces; modeling and list build consume.
Executable gates
37 total: 12 enforce, 21 shadow, 4 dry run.
Implementation evidence
Consumer-side invariants exist; producer obligations, owners, and adoption sign-off remain open.

Caveat: this is a draft contract over an existing production table. Its measured tolerances do not imply that the producer has adopted the contract.

Address Resolution Service

8020rei.ars.address_resolution
Draft · v1.0

The service handoff for address standardization: API shape, five-field equivalence, errors, reporting, certification, and service-level expectations.

Parties
ARS service owner produces; modeling and list build consume.
Executable gates
14 total: 4 enforce, 3 shadow, 7 dry run.
Implementation evidence
Adapter and small-batch smokes exist. A current certification remains the pinning gate.

Caveat: no current passing certification means ARS cannot be pinned as the permit pipeline's address-normalization version.

02 Permits pipeline contract chain

Use these handoff contracts to review what each layer receives and delivers. The Gold row is a readable layer summary; the governed Gold contract above remains the source of record.

  1. 01
    LandingAdopted v0.1 · readiness partial

    Receive: the four-file BuildZoom drop. Deliver: validated all-string shards and an atomic _CURRENT pointer.

    Read handoff
  2. 02
    BronzeAdopted v0.1 · readiness partial

    Receive: validated Landing shards. Deliver: four deterministic raw Hudi mirrors with source values preserved.

    Read handoff
  3. 03
    SilverAdopted v0.1 · full-shape amendment draft

    Receive: four Bronze tables. Deliver: guarded permit groups, lossless source lines, property-link evidence, classification, and address keys.

    Read handoff
  4. 04
    GoldAdopted v2.2.1 target · runtime local-only

    Receive: Silver permit surfaces and First American property state. Deliver: the linked, auditable Permits_Master_Gold event spine.

    Read handoff

03 Contract families still in review

These specifications remain repository drafts. They are grouped here so the frontend does not present unfinished documents as operational guarantees.

Aurora serving tier

contracts/etl/

GOLD_AURORA_SERVING, GOLD_DAILY_ETL, and SERVING divide schema, Gold-to-staging deltas, and the staging-to-Aurora load engine. Machine gate packages and adoption are still pending.

Draft

Hestia model lifecycle

contracts/roofing/

Five v0.1 drafts govern label, feature admission, folds, calibration, and output. Coverage is separately at v0.3 DRAFT (2026-08-19). All six remain pending review; none is a deployed guarantee.
Label · Coverage v0.3 · Features · Folds · Calibration · Output

Draft

04 Vendor agreement register

Vendor agreements answer licensing and operating questions, not pipeline conformance questions.

Six private source agreements

redacted frontend register

The public page records purpose and provenance for data products, data collection, and operating services. Commercial terms, signatures, contact details, and source PDFs remain in the private repository.

Open register