Turn “trust me” into a verifiable trail: timestamps, immutable anchors, and exportable evidence.
When a file changes hands, the real problem is rarely the file itself. It’s the story around it: who produced what, when, and whether anything changed after approval. WrittenInStone helps you build a repeatable evidence trail you can export and reuse in reviews, audits, and disputes.
Evidence is not a long PDF full of claims. It’s a small set of verifiable facts:
Blockchains are good at one thing: providing a shared, hard-to-rewrite timeline. We use that property to anchor your proof records. Once a fingerprint is anchored with a timestamp, it becomes difficult to backdate or quietly rewrite the record later.
Think of each proof record as a small “event” in an evidence chain. For each event, we write a compact bundle of data:
Later, these events can be discovered by record ID (or through your dashboard) and used to generate exports: logs, timelines, and verification summaries.
For audits and disputes, you often need a single artifact that summarizes many events. Instead of rehashing everything repeatedly, we can produce an evidence manifest:
This gives you a compact “one-page” proof: the manifest can be shared, archived, or attached to a report. If anyone questions it later, they can recompute the manifest hash and confirm it matches the anchored reference.
Evidence works best when it’s shareable. Keep the public part minimal: a fingerprint, a timestamp, and a verification link/QR. If you add metadata, treat it like a public label—avoid secrets and personal data.
This is technical evidence of integrity and time. It doesn’t replace legal advice, formal signatures, or notarization. But it does remove a huge class of ambiguity: whether a file changed after a specific point in time.