Every entry hash matches its canonical event and the previous hash.
CHECK / RUN HISTORY / AUDIT V1.0Check the run.
Check the run.
Verify the chain.
This is CHECK's advanced run-evidence view. A bounded browser-local SHA-256 ledger binds approvals, explicit project runs and outcomes into one tamper-evident history. Export it for independent verification or signed evidence without exposing source file contents or names.
Check run history →APPROVESCOPE HASH→RUNEXPLICIT START→RESULTPASS / BLOCK→CHAINPREVIOUS + EVENT→EVIDENCEEXPORT / SIGN
LOCAL HASH CHAIN0/240 ENTRIES0 RUN EVENTS0 APPROVALSLOCAL LEDGER / VERIFYING
The current chain head changes when any new audited approval or run event is appended.
The ledger never silently prunes its beginning. Export and explicitly start a new ledger when full.
No filenames, source paths, source SHA-256 values, file bytes, passphrases or output payloads are recorded.
01 / VERIFY + EXPORT
Prove the run history you still have.
The local ledger is append-only by product contract. Verification recomputes every entry hash from genesis to head before export.
02 / EVENT LEDGER
Approval → run → result.
HEAD / UNVERIFIEDNo audited events yet.
The next scope approval or explicit PROJECT run will create the genesis entry automatically.
REVIEW PROJECT RUN →03 / INDEPENDENT VERIFY
Check an exported ledger.
Import verification is read-only. It never replaces the current local ledger.
Editing, deleting or reordering stored entries breaks verification. A party with full origin control could still replace the whole ledger and recompute a new chain; AUDIT makes no immutable-ledger claim.
AUTOMATION verifies the current chain before consuming an approval or starting FLOW and reserves two entries for start + result.
Export evidence before starting over. A new ledger has a new genesis and does not pretend continuity with the deleted chain.