Reference implementationDeterministic replayVerification reportTool-agnostic

Reference & Verification

The goal is independent verification: a third party can reconstruct a knowledge state from referenced inputs and confirm the expected SHA-256 snapshot hash. Same inputs → same reconstructed state → same hash.

Verify in 60 seconds

Workflow

This is the minimal verification loop. It is intentionally simple and auditable.

Pick a snapshot

Choose a snapshot hash and collect its referenced inputs (units, versions, claims, uncertainty, artifacts).

Replay deterministically

Reconstruct the knowledge state from the referenced inputs using deterministic replay.

Compute the hash

Compute the resulting SHA-256 state hash from the reconstructed state.

Compare + report

Compare computed vs expected hash and emit a verification report (PASS / FAIL + details).

Verification Example

Illustrative public flow

A minimal public example of the verification flow. Independent implementations performing deterministic replay must obtain the identical snapshot hash.

$ digiemu verify demo_bundle_v1.json

Snapshot: 9c6a1e4e8d5c...
Computed: 9c6a1e4e8d5c...

Result: PASS

This example is illustrative and shows the expected public verification shape: select inputs, replay deterministically, compute the canonical SHA-256 state hash, compare against the expected snapshot, and emit a result.

Download demo bundle Download verification result

CLI Contract v1 (reference interface)

Defined by tag: cli-contract-v1.0.0

This interface reflects the locked CLI contract v1. It documents the normative input/output shape and does not imply a distributed binary release.

cli-contract-v1.0.0 (tag)

# Placeholder (interface example — not a released CLI yet)
digiemu verify \
  --snapshot <SHA256> \
  --inputs ./inputs \
  --out ./report.json

# Expected output:
#  report.json (PASS/FAIL, computedHash, expectedHash, referencedInputs, metadata)

GitHub — Core GitHub — Reference

Audit artifacts

These artifacts define the verification mechanics, test expectations, and decision provenance. Drafts are published as downloadable PDF while the public spec stabilizes.

Specification

Normative

Authoritative definition of data formats, snapshot semantics, and verification APIs.

DownloadV1.0

Determinism (Formal)

Evidence

Formal definition of determinism, replay invariants, and reproducibility guarantees.

DownloadV1.0

Audit Framework

Mechanics

Procedures for capturing, storing, and validating audit evidence and decision provenance.

DownloadV1.0

Conformance

MUST/SHALL

Testable requirements and acceptance criteria implementers must meet for compliance.

DownloadV1.0

Certification

Policy

Technical evidence and assessment steps used during certification and audits.

DownloadV1.0

Governance

Process

Roles, change control, and release practices that ensure traceability and accountability.

DownloadV1.0

Security Model

Model

Threat assumptions and protection goals.

DownloadV1.0

Threat Model

Model

Adversaries, attack surfaces and mitigations.

DownloadV1.0

Deployment Guidelines

Ops

Operational guidance for reproducible builds and verification.

DownloadV1.0

Independent verification principle

Verification must be possible without privileged access. A third party should be able to implement replay independently and still obtain the identical hash for the same referenced inputs.

Tool-agnosticDeterministic replayEvidence-based PASS/FAILReferentially closed inputs