Export Bundles · Append-Only Evidence · Replay by Recomputation

Verification & Replay

High-trust systems require outcomes that can be independently verified. Norcrest uses canonical artefacts, append-only evidence, and export bundles to enable offline recomputation of publication hashes under snapshot-bound context.

Research collaboration Get in touch Connect on LinkedIn

Traceability by construction

Externally effective outputs bind to a publication wrapper: snapshot identifier, registry references, decision hash, result hash, publication hash.

Why it matters: evidence is produced, not reconstructed

Independent recomputation

An external verification node can recompute publication hashes using canonicalisation rules and exported artefacts.

Why it matters: verification does not rely on runtime trust

Determinism breach detection

If recomputed hashes differ under equivalent inputs + snapshot context, a determinism breach condition is recorded.

Why it matters: replay divergence becomes measurable

Evidence-first operation: export bundles enable verification without rebuilding logs after the fact.

Export bundle contents

Export bundles are immutable artefacts containing sufficient deterministic material to permit offline recomputation and verification.

Canonical input envelope (or canonical envelope references)
Snapshot identifier and immutable registry version references
Deterministic verification gate outputs and constraint results
Decision hash and routing artefacts (deterministic fields only)
Execution result hash
Publication wrapper and publication hash
Export hash over the canonical export bundle

The goal is direct: independent verification by recomputation under snapshot-resolved context, without dependence on mutable runtime logs.