Signed snapshots, not a moving database

Each downstream plane reads a frozen, digested payload. This public digest is FNV-1a of the feature summary — inspectable, not a substitute for KMS signatures in the production exporter.

manifest.json

{
  "atlas": "v1.0",
  "evidence": "indus-atlas-evidence-0.1.0",
  "features": "indus-atlas-features-0.1.0",
  "digest": "ef3c330b",
  "gates": true,
  "corpus": "compiled-icit-style-2026.09"
}

digest 019a6c63

indus-atlas-evidence-0.1.0
z1 → z2
Published, current artefact and inscription rows only. Drafts and superseded revisions excluded.
indus-atlas-features-0.1.0
z2
Q_robust, directional scenarios, positional entropy, n-grams, sensitivity grid.
indus-atlas-graph-0.1.0
z2 → z3
Named projection: SignType, Site, Artefact, PRECEDES with evidence weights.
indus-atlas-model-0.1.0
z3
Markov baseline, site holdouts, explicit caveat if deeper models do not generalise.
indus-atlas-features-synthetic-0.1.0
z2 (crash-test)
ART-001–004 plus poison-pill scan. Must be green before any live ingestion.

Independent sign-off (protocol)

Security lead — RLS, audit events, ontology leak scan.
Statistical lead — FDR, nulls, directional partition, duplicate n_eff.
Archaeological review lead — metadata fidelity of the evidence freeze.

The atlas goes live as a measuring instrument. It does not promise to read the unreadable.