Skip to content
Induscript

Induscript · Structural Atlas v1.0

Epistemic valve

Four zones, one direction

Evidence can be snapshotted into analytics. Analytics can be projected into a graph. A graph can train a structural model. Ontology cannot walk back up the chain.

  1. Z₁ · Evidence plane

    Canonical ledger

    ↓ one way

    Sites, artefacts, inscriptions, tokens, quality assessments, scholar assertions. Append and supersede only.

    Stack: PostgreSQL / PostGIS (specified topology)

    Never: No UPDATE/DELETE of live rows. No narrative labels. No DVM opcodes.

  2. Z₂ · Analytics plane

    Analytics & features

    ↓ one way

    Immutable evidence releases, Q_robust, directional scenarios, n-grams, positional entropy, sensitivity grids.

    Stack: DuckDB on signed Parquet snapshots

    Never: No network route back to the ledger. No draft or superseded rows.

  3. Z₃ · Model plane

    Graph & model

    ↓ one way

    SignType, Site, Artefact nodes; PRECEDES / EXCAVATED_AT edges; Markov and holdout scores.

    Stack: Named graph projections / structural baselines

    Never: No ontology tables. No DATABASE_URL. Failure to beat a Markov baseline is published as a caveat, not hidden.

  4. Z₄ · Quarantine

    Hypothesis ontology

    quarantine

    Speculative DVM / Mahadevan-range labels, narrative fit tests, warnings.

    Stack: ontology.m_code_hypothesis

    Never: Cannot be read by analytics_runner, graph_loader, or model_runner. Public toggle carries a persistent banner.

Fail-closed posture

  • PUBLIC has no schema grants. Roles are provisioned empty, then granted the minimum.
  • analytics_runner, graph_loader, and model_runner are revoked on canonical and ontology.
  • model_runner is denied SELECT on ontology even if a query is smuggled through information_schema.
  • There is no shared DATABASE_URL for the model plane.