Digital watermark, evidence & audit trail
Turn “trust me” into a verifiable delivery system: visible verification labels, immutable timestamps, blockchain anchors, and exportable evidence.
When a file changes hands, the real problem is rarely the file itself.
It’s the story around it:
what was delivered, when it was delivered, whether it changed later, and how to prove it independently.
WrittenInStone combines proof records, visible verification labels (QR/link), and structured audit exports to create a repeatable trust workflow for handoffs, reviews, audits, and disputes.
What “digital watermark” means here
In WrittenInStone, a digital watermark is not an invisible image modification.
It is a visible verification marker — a QR code, link, badge, or reference block tied directly to your proof record.
- It travels with the asset — PDF cover page, handoff pack, footer, landing page, invoice, or report.
- It reduces friction — recipients verify instead of relying on screenshots or email chains.
- It exposes silent edits — if the file changes, verification shows mismatch.
- It can support audit exports — proof + blockchain anchor + verification history.
How it works (simple workflow)
- Stamp — Generate a proof record (cryptographic fingerprint + trusted timestamp).
- Anchor — Tie that proof to an immutable registry (blockchain-backed timeline).
- Share — Use a QR, link, watermark, or verification label.
- Verify — Anyone can independently confirm match / mismatch later.
- Export — Generate evidence logs or audit-ready reports when stronger documentation is needed.
What “evidence” means in practice
Evidence is not marketing language or a long PDF of claims.
It is a compact set of verifiable facts:
- What: file fingerprint (hash).
- When: timestamp.
- Where: immutable registry / blockchain reference.
- Status: match / mismatch verification over time.
- Context: optional metadata (project ID, export ID, handoff note).
How blockchain fits (without hype)
Blockchain here is not about speculation.
Its practical value is a hard-to-rewrite timeline.
Once a proof fingerprint is anchored, backdating or quietly replacing that record becomes significantly harder.
What a recipient or auditor can see
- Verification result: match or mismatch.
- Proof record ID: referenceable asset identifier.
- Timestamp: when the proof existed.
- Blockchain reference: immutable anchor trail (where applicable).
- Optional public metadata: delivery or project context.
Exportable reports: beyond QR
QR and links are the fastest day-to-day trust tools.
For disputes, audits, or compliance, you may also need stronger structured exports:
- Verification report: proof + timestamp + result summary.
- Evidence log: chronological proof and validation history.
- Audit bundle: manifest + summary hash + blockchain references.
This allows you to show not only that a file matched once,
but how that proof existed within a broader verifiable chain.
Where this helps most
- Client handoff: prove exact delivery version.
- Reports & statements: attach trust to PDFs.
- Creative publishing: timestamp published originals.
- Audits & compliance: preserve verifiable evidence.
- Disputes: reduce arguments to measurable proof.
Privacy note
By default, proof works in hash-only mode.
You do not need to expose the original file publicly for others to validate integrity.
Keep public metadata minimal and non-sensitive.
What this proves (and what it doesn’t)
- Proves: integrity, timestamped existence, and verifiable reference history.
- Does not automatically prove: legal authorship, copyright ownership, or notarization by itself.
Verify a file
Create a proof record
