Knowledge Replay, IGRM

Current state: implemented synthetic conformance foundation. No production canonical world-state ledger exists yet. The committed production signer registry is empty, so this interface cannot silently convert the demonstration into a claim about real events, exposure or institutional adoption.

Two clocks, never conflated

What was valid—and what was knowable?

Valid time asks which state applied on a date. Knowledge time asks which complete, signed release had entered the separately signed receipt chain by a cutoff. IGRM selects on the second clock first, then evaluates the first. A later correction is therefore incapable of leaking into an earlier knowledge cutoff.

Knowledge cutoff: Chooses the latest separately receipted complete release
Valid date: Evaluates lifecycle and effective intervals inside only that release

Deterministic public test vector

Hold the event date fixed. Move only knowledge time.

Loading the hash-locked synthetic demonstration…

What the engine refuses

A cutoff before the first separate receipt or after the signed ledger closes.
A missing receipt, broken hash chain, invalid signature or release byte mismatch.
A changed record under the same object ID, a revision without its prior parent, a forked revision line or an unexplained deletion from a complete snapshot.
Labels, source text, URLs, exposure values, confidence scores, causal attribution, forecasts or advice in the structural replay result.

Machine contract

python -m src.knowledge_replay LEDGER.json \
  --knowledge-cutoff 2026-08-08T14:30:00Z \
  --valid-on 2026-08-08 --object-type event

The validator rechecks the ledger and receipt signatures, every complete canonical release, each historical governance snapshot, immutable object lineage, the replay implementation and all three schemas. A successful result is a structural snapshot, not a finding that an event is true.

What must happen before production

The engine requires distinct identities and public keys for canonical release, availability and replay-ledger signing. Even that separation does not establish institutional independence. IGRM must establish externally controlled availability and ledger-signing keys, issue rights-reviewed production canonical releases, retain versioned governance snapshots and publish the receipt chain through an external transparency or timestamp service. Until then, this page proves executable behavior only.