01 Origin
- source
- Customer issue record
EVIDENCE PLAYGROUND
Inspect the record.
Question the chain.
Two hands-on examples. Compare sample decisions, then change a record and see what an integrity check detects.
One record,
five faces of evidence.
Walk through the five aspects of a sample record: origin, context, policy, receipt and replay. Select a card to see its real data.
02 Context
- context
- Account tier, retrieval set and case history
03 Policy
- policy
- Support escalation v3.2
04 Receipt
- receipt_reference
- demo_rct_7v2a…e91c
- tenant_scope
- demo-workspace
- recorded_at
- 2026-09-07T09:41:05Z
05 Replay
- id
- demo-a
- recorded_at
- 2026-09-07T09:41:05Z
- tenant_scope
- demo-workspace
Origin
- source
- Customer issue record
Records
The sample record you select is included in the download.
Evidence
Origin, context, policy and receipt stay legible at all times.
Verification
Illustrative references are not production cryptographic receipts.
A change should
leave a trace.
Seal the sample, alter one field, then compare its hash with the original reference.
Try changing “1042” to “1043” after sealing the record.
REFERENCE CHECK
Ready to seal.
The original reference will be calculated from the sample text.
- Original reference
- Not sealed yet
- Current record
- Not checked yet
What exactly is this demonstration checking?
This example computes SHA-256 hashes in your browser over the exact UTF-8 bytes of the sample text. The original hash is held in this page’s memory. A match means the text matches that reference; a mismatch means it changed.
This is an educational integrity check, not a production receipt, digital signature, trusted timestamp, or a test of PHIROK’s BLAKE3 backend. Editing both the record and its reference defeats this local comparison. Production assurance requires trusted checkpoints and the relevant authorization and verification controls.
No sample text is transmitted. Reloading the page clears the local reference.
YOUR NEXT DECISION
Touch the evidence.
Trust the check.
You changed a record and watched the hash respond. That is the whole idea.