Skip to content

ARCHITECTURE.md

Latest commit

 

History

History
63 lines (39 loc) · 1.69 KB

ARCHITECTURE.md

File metadata and controls

63 lines (39 loc) · 1.69 KB

Architecture

Execution Surface

Dimensional Drift Witness is organized as a deterministic proof artifact.

The architecture separates case data, governing policy, verifier logic, generated receipts, proof-pack validation, CLI access, and CI replay.

Flow

  1. drift_cases.json supplies paired execution states.
  2. drift_policy.json defines the severity model.
  3. drift_verifier.py compares operational continuity against legitimacy continuity.
  4. drift_receipt.json records the deterministic witness result.
  5. proof_pack.py verifies expected proof counts and receipt structure.
  6. tests/ validates discrimination behavior.
  7. .github/workflows/proof-pack.yml runs proof replay in CI.

Core Separation

Operational dimensions:

  • actor
  • action
  • output
  • replay trace

Legitimacy dimensions:

  • authority
  • custody
  • standing
  • scope

The witness only classifies dimensional drift when operational continuity holds while one or more legitimacy dimensions diverge.

Decision Surface

  • DRIFT_DETECTED: operational continuity holds and legitimacy continuity fails.
  • NO_DRIFT: operational and legitimacy continuity both hold.
  • OPERATIONAL_DIVERGENCE: operational continuity fails, so legitimacy drift cannot be isolated.

Enforcement Interpretation

The repository does not enforce production decisions directly.

It produces a receipt indicating what enforcement response would be required if the witness were integrated into a production authority and custody system.

Replay Invariant

Running the proof pack must not mutate the repository state.

Expected replay check:

python proof_pack.py

python -m pytest -q

git status

Expected result:

nothing to commit, working tree clean