Admin walkthrough · Live database records
Follow the evidence
Choose an idea and follow what Sealright recorded, how its entries link, and whether those entries have reached a closed batch and an external anchor.
1 · IdeaSubmitted content gets a ledger record.
2 · HistoryLater events get their own sequence numbers.
3 · BatchEntries are grouped under a Merkle checkpoint.
4 · AnchorA published checkpoint can be checked outside Sealright.
Recorded journey
Batch and external witness
Verification snapshot
Database checks cover the complete ledger, rather than only this idea. They do not contact external anchor providers.
What this demonstrates
Hashes reveal changes to recorded content or broken links when the checks are rerun. A batch checkpoint commits to a range of entries. A separately verified external publication can detect a rewritten database history.
An anchor row is a reference, not proof that its external destination matches. Entries awaiting a batch have no checkpoint or external witness yet. This is tamper evidence, not a claim that privileged database access is impossible.