Answers point at a version, not at a file

A file changes. A version does not. Every answer records which version it was found in, which is what lets somebody check the work months later when the document has moved on.

Book a 30-minute call Isolation

Evidence records for one document Immutable, superseding

v3.14 Read for a grounded answersha256 9f2c1a…7e40 · 3 claims bound to this version Current

v3.9 Superseded by an edit in SharePointEarlier answers still point here, and still resolve Retained

v2.1 Aged out of the provider's version historyBytes held in the evidentiary cache so the old answer can still be checked Cached

Dropbox keeps versions for 30 days on some plans. Matters run for years. The cache holds exactly the bytes we made a claim about, and nothing else.

What a record holds

Eight fields, and none of them is a seal

The integrity anchor is your own platform's version identity. We do not ask you to trust something we stamped.

connectorWhich system it came from

repositoryWhich store inside it

object idStable across rename and move

version idYour platform's own immutable handle

content hashsha256, when the provider gives one

authorization scopeA content-free hash of who could see it

locatorPage or character position

retrieved atWhen the read happened

Two problems this solves

Both of them show up years later

The document changed

Somebody edits the file after an answer was given. Without version binding, the answer now points at text that is no longer there.

A new read makes a new record

Nothing is edited in place, so the old record and the old answer both survive.

Old answers still resolve

An answer from March still points at the March version, and can still be opened and checked.

Nothing is silently corrected

The system does not quietly re-point an old claim at new text that happens to match.

The version expired

Providers age out version history on a schedule set by the plan the firm pays for. Matters outlive that schedule.

The cache is narrow on purpose

It holds the exact bytes behind claims already made. It is not a backup of your document store.

Write once, content addressed

Entries are keyed by their hash, so the same bytes are never stored twice and cannot be altered after the fact.

It is never authoritative

Your store remains the system of record. The cache exists to prove what was read, not to tell you what is true now.

Keep reading

NextIsolation BackHow a claim is checked SecurityWhat we can claim today

Start a conversation

Tell us what your people spend the day reading.

Thirty minutes, no obligation. If a shared product would serve you better, we will say so on the call.

Book a 30-minute call Send a message

The Brief

The week in legal, in four minutes.

Free, national to Orange County, every Wednesday.