A second pair of eyes.
Check who signed a commitment and whether its earlier history was preserved. Real signatures and Merkle proofs, in a local demonstration you can export and verify yourself.
How the review works
You present an opaque commitment
Present a Merkle root over record commitments, declared counts, a sequence and timestamp, plus a signature and consistency proof. Private journal content is not included in the request or export.
Three local instances review
The browser creates three separately keyed witness instances. Two distinct keys are required for the demonstration quorum. Independent ownership, deployment and network fault tolerance are not established by this local panel.
They check control and consistency
Each witness binds the subject label to an explicitly configured key. It checks signatures, valid and nondecreasing counts, advancing sequences and cryptographic preservation of the previous committed prefix.
You keep portable proof
Export the signed claims, consistency proofs and endorsements. A standalone verifier checks them against keys the verifier trusts separately. Identity, counts and reported timestamps are covered by the signatures.
What it closes
for Reputation & the Mirror
Explore how portable evidence could support reputation while keeping journal contents private. This session does not enroll a real Echo identity, confer reputation or certify the truth of experiences.
for the Transparency Log
Merkle consistency links each submitted root to the previously accepted root. It preserves committed prefixes within the reviewed sequence. Durable checkpoints and comparison between independent operators are required across real sessions.
The sharp edges, shown
Committed history, bounded claims
A proof establishes consistency of commitments and signatures under configured keys. It does not establish real-world identity, truthful journal contents or that declared integration counts reflect real learning.
Counts are minimal metadata
Counts, identity labels, sequences, timestamps and public keys are visible in exported evidence. They can reveal activity. Local journal commitments use a random salt that stays on the device to resist guessing their contents.
Independent operation is a deployment requirement
Production witnesses need separately controlled keys, persistent checkpoints, verified enrollment and rotation, and a stated fault model. Counting browser-generated keys cannot substitute for those operational guarantees.
Endorsement is a moment, not forever
An endorsement covers one claim and a witness-reported time. This page resets keys and checkpoints on each run. Reviewing your journal reconstructs prefixes of its current contents; it cannot recover or authenticate past states.