Integrity
Content commitments detect changes to protected evidence.
ILLUSTRATIVE VERIFIER WALKTHROUGH
Don't trust the badge. Verify the evidence.
Explore how evidence verification behaves across different consequential workflows. This page illustrates the expected results; the separate synthetic evidence lab performs actual cryptographic checks.
SAMPLE EVIDENCE BUNDLE
dec_demo_720- action
- refund.create
- amount
- $720
- policy
- refund-policy v17.3
- review
- Alice · approved
- outcome
- succeeded
✓ VERIFIED
This walkthrough changes sample display states; it does not recompute hashes or signatures. Try the working cryptographic demonstration →
CHOOSE A WORKFLOW
Same verification model. Different consequential decisions.
Switch scenarios without changing the verifier. Each sample highlights a protected field that matters to a different production workflow.
VERIFICATION TESTS
Break the copy. The verifier should fail loudly.
Start from a sample export and change the displayed evidence. This walkthrough illustrates content, chain and signer failures. For actual SHA-256 and Ed25519 verification, use the synthetic evidence lab.
What a real verifier checks
The exported evidence can be checked for content integrity, signed-history continuity, and expected signer identity outside the running application.
Separate assurance questions
Verification establishes integrity and provenance of captured evidence. Correctness, completeness and capture-boundary guarantees depend on the workflow and deployment architecture.
Illustrative verifier outputUI simulation
# Illustrative output — see /demo for actual verification
LOOPGRID EVIDENCE VERIFICATION
✓ VERIFIED
content commitmentvalidchain continuityvalidsigner pintruenetwork requiredfalse
PORTABLE BY DESIGN
Verification should work with LoopGrid absent.
A bundle can carry the decision, signed events, chain witnesses and public verification material. The verifier checks the bundle without a network dependency.
Chain continuity
Workspace-scoped links expose missing or modified signed history.
Signer identity
Signer pinning checks that evidence was signed by the expected identity.
Offline
Verification does not require trusting the running LoopGrid service.