OpenChainGraph Suite · ART-750 · Evidence-bundle diff kernel

Diff Evidence Bundles

Paste two parsed JSON bundles (artifact, chain, evidence bundle or records array) and read what moved: hash and digest fields, version fields, normalized accountability sets, and the verdict with a regression flag.

values-only outputshape migrations are never diff rowsdepth cap 200Zero PIIClient-side only
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data; use synthetic or anonymised inputs only.
Scope & reliance
Each side is classified the way the estate's verification desk classifies inputs: an OCG artifact (object carrying an execution_hash), a chain (step-artifact array or an object with a steps array), an evidence bundle (subject_hash without execution_hash, with reviewer, approver, annotation or timestamp members) or a records array; anything else is refused with a named reason. The accountability section normalizes legacy records arrays, embedded sign_off members and the converged evidence-bundle shape to the same comparison keys, so a shape migration alone never surfaces as a diff row. The verdict is taken from verification_result first, then explicit verdict-family fields, then derived from a checks array; regressed marks a move toward fail, reject or hold. The as_of field supplies the clock reading for override freshness and is required whenever an override record is present (the kernel takes no wall-clock input). Nesting is capped at 200 levels.
Bundles
Result
n/a
Bundle A class
n/a
Bundle B class
n/a
Bundles identical
n/a
Execution hash & kernel output
execution_hash: n/a
{}
Proof status
This node ships compute_proof_ready: deferred. No formal correctness proof has been produced for this kernel; the result above is a deterministic recompute, verified by a property-test floor, not a proven one.