DigiEmu Core
Public Standard

Specification (Normative Core)

This page summarizes the normative guarantees and definitions of the DigiEmu Core public standard. It defines deterministic reconstruction of knowledge state and snapshot-verifiable verification.

DeterminismReplaySHA-256 SnapshotEvidenceGovernance

Normative Guarantees

The following statements are intended as standard-level requirements. They define the audit surface.

Deterministic reconstruction
Given the same referenced inputs and the same replay procedure, the reconstructed knowledge state MUST be identical.
Canonical state encoding
The reconstructed knowledge state MUST be serialized in a canonical form so that hashing is stable across environments.
Snapshot hashing (SHA-256)
The snapshot hash MUST be computed over the canonical state encoding using SHA-256.
Independent verification
Any independent implementation MAY verify a snapshot by deterministic replay and hash comparison.
Evidence-based audit surface
Verification MUST produce a report that links the snapshot, referenced inputs, and the computed result (PASS/FAIL).
Invariant
Same inputs → same reconstructed state → same hash.

Definitions

Term
Unit
A versioned knowledge object. Units are the stable building blocks referenced by snapshots.
Term
Version
An immutable revision of a Unit. Versions are the only admissible replay inputs.
Term
Claim
An explicit assertion attached to Units/Versions. Claims are part of the auditable knowledge state.
Term
Uncertainty
A first-class element that represents incompleteness, ambiguity, or confidence bounds. Uncertainty is explicit, not implicit.
Term
Snapshot
A cryptographic identifier (SHA-256) of a canonically encoded reconstructed knowledge state, plus references to all admissible inputs required for deterministic replay.

Verification Model

Verification is evidence-based and tool-agnostic. It is defined as deterministic replay plus hash comparison.

Procedure
  1. 1. Select snapshot
  2. 2. Deterministically reconstruct state from referenced inputs
  3. 3. Compute SHA-256 hash of canonical state encoding
  4. 4. Compare computed hash to snapshot hash and produce report
Output: PASS or FAIL.
CLI Contract v1 (baseline — locked)
The v1 CLI contract is locked and documented in the Core repository. CLI_CONTRACT_v1.0.md

Normative Artifacts

The following artifacts provide the full normative and governance definitions.

Core 2.0 Draft 1 Specification (PDF)
Core 2.0 Draft 1 Verification Framework (PDF)
Core 2.0 Draft 1 Interop Contract (PDF)
Core 2.0 Draft 1 Conformance Profile (PDF)
Core 2.0 Draft 1 Governance Notes (PDF)
v1 archive PDFs: Specification · Determinism · Conformance

Normative keywords

The following keywords indicate requirement levels in this specification. They are used to express conformance criteria.

  • MUST — absolute requirement.
  • SHALL — normative requirement (equivalent to MUST).
  • SHOULD — recommended; valid reasons may exist to deviate.
  • MAY — optional behavior.

Normative references (PDF)

The public documentation suite provides the formal specification and the conformance boundaries for deterministic replay and verification.

Note: Download links serve PDF files from public/docs.

Release Anchors

The current release is DigiEmu Core 2.0 (tag: core-2.0.0). This page mirrors the cryptographic release line as published in the DigiEmu Core repository.

Current release
core-2.0.0
Core 2.0
GitHub
Legacy archive — v1 release line

The v1 baseline and signed patch line remain available as a legacy archive.

Normative baseline
v1
Signed patch line
  • v1.0.1
  • v1.0.2
  • v1.0.3

Cryptographic Integrity

Release tags are signed. Independent verification is performed with Git tag signature checks against the published public key material.

Public signing key
Fingerprint
DCB7 228C 6EC8 BE4A CB9E 049D 0F75 05E1 2685 E8A2
Verify locally
git tag -v core-2.0.0
# Legacy v1 archive:
git tag -v v1
git tag -v v1.0.3

Verification uses Git’s built-in signature checks. The public key material and fingerprint are published in the public standard repository.

Audit Status

Core 2.0 (core-2.0.0) is the current release. It is cryptographically anchored and audit-traceable.

Audit statement
Core 2.0 — interop contract
This website does not mint releases. It mirrors the cryptographic release line as published in the DigiEmu Core repository.