◈ Situations, not customers
Nobody records a file on the day it matters.
By the time the question arrives, the only dates left on a file are ones you could have set yourself. Everyone below is months past the moment they would have needed to act.
The week they’re having
Eight situations- Legal
A paralegal logging evidence on a Tuesday morning
Nobody will question the file today. They’ll question it in eighteen months, when everyone who touched it has moved on and the only date left is the one the file server wrote.
She recordsA fingerprint of the intake file while the surrounding log is current.
Still needsThe exact file, plus intake and custody records. The anchor is one checkpoint inside that process, never a substitute for it.
- Media
A reporter comparing a disputed clip with an ingest file
A cut-down version is circulating and being called the real one. His ingest files sit on a drive whose dates anyone could change.
He recordsThe ingest file before beginning an edit.
Still needsThat exact file, plus capture and ingest records. The chain record does not show that it was first or that a camera made it.
- Contracts
An operations lead, two years into a five-year agreement
The other side quotes a clause she does not remember agreeing to, and attaches a PDF. Both copies look equally official.
She recordsThe agreement file the team retains for the term.
Still needsThe exact file, signer identity, and agreement evidence. The anchor does not show who signed, what they agreed, or whether it is enforceable.
- Original work
A designer who showed the deck before the pitch
Months later the same concept turns up under someone else’s name. Her drafts are on a drive; every date on them is one she could have set herself.
She recordsThe draft file before the pitch.
Still needsThat exact draft, plus authorship and delivery context. The anchor does not show who made the work, whether anyone copied it, or grant a right.
- Creative
A freelancer whose final invoice is suddenly in dispute
The client says what they received was not what the invoice describes. The only date on the delivery is the one his own laptop wrote, and he is the one being asked to prove otherwise.
He recordsThe exact deliverable before sending it.
Still needsThat file, his contract, and transmission records. The anchor does not show that the client received it or who owns the work.
- Research
A researcher nine months into peer review
A reviewer wants the exact model behind figure four. The weights have been retrained twice since, and the config file has moved on with them.
She recordsThe weights and config selected for that run.
Still needsThose exact files, plus run logs tying them to figure four. The anchor distinguishes the recorded version; it does not establish what produced the result or whether it holds up.
- Infra
An engineer answering a customer’s security questionnaire
They want to know that what is running in production is what came out of the pipeline — not something patched in by hand one evening and never written down.
He recordsThe release artifact retained after the build.
Still needsA signed release and provenance record. The anchor can show that held bytes match the recorded artifact, not that it ran or is safe.
- Finance
A controller eight months after handing over an export
The auditor has a file and a question: is this the one you sent us in March, or has something moved since?
She recordsThe export before the handoff.
Still needsThat exact export, handoff records, and approval controls. The anchor does not show that it was sent, received, complete, or correct.
- 01 · Record
The file body stays on your device.
Your browser hashes the file locally and sends its SHA-256 digest, not the file body. Filename, size, type, topic, or external ID can also reach us. A public digest is not encryption or automatic anonymization; predictable inputs can be tested against it.
- 02 · Keep
You keep the file and the receipt.
Keep both together for a later comparison. A digest cannot reconstruct the file or stand in for the exact bytes you recorded.
- 03 · Check
A verifier can check without relying on us.
With the retained file, receipt, and Base access, they can recompute the digest and compare its named transaction slot without our API or database. Unrelated digests can share that transaction, disclosing only that their records were submitted in the same short window.