Week 8: The Canonical Version

Authority. Who gets to say which copy is real, and on what grounds, once a hash or a timestamp can no longer settle the question

12 April 2027

Open the slides

Somewhere between “these two files differ” and “someone acts on one of them,” a decision gets made about which one counts. That decision isn’t a technical fact. It’s a claim about authority, and it has to be grounded in something.

Four grounds people actually use#

• Possession. Whoever holds the master copy: the signed contract in legal’s filing system, the “source of truth” spreadsheet on one person’s laptop. Authority by custody, regardless of who else has a copy.
• Position. Whoever’s role entitles them to decide: an editor, a maintainer, a manager with sign-off. Authority by standing, independent of who actually touched the file most recently.
• Recency. Whoever edited last. The most commonly used ground, and the weakest: “latest” is a timestamp, not a judgement, and a timestamp can’t tell you whether the last person to touch the file had any standing to.
• Consensus. Whoever most people currently defer to. This can shift without the file changing at all: a version becomes canonical because enough people started treating it that way, not because of anything that happened to its bytes.

Why they conflict#

The grounds are not ranked, and in an ordinary dispute they point at different copies:

copy                            ground        the claim
──────────────────────────────  ────────────  ───────────────────────────
signed PDF in contract system   possession    this is the executed one
the DOCX legal is editing       position      legal owns the wording
the version emailed at 4pm      recency       nothing is newer
the build the delivery team     consensus     everyone works from this

All four are the same agreement, and each holder can state a real ground. The disagreements are consequential in exactly the way the grounds are independent: the most recent edit isn’t authoritative if the editor lacked standing to make it, the copy in one department’s possession can lose to a court’s reading of a different copy, and a team can build consensus around a draft the person with formal position never approved.

None of this is settled by comparing bytes. Run week 2’s tests across those four copies and you learn which of them differ, which is not the question. Identity is a fact about files. Authority is a fact about people, and it has to be argued for.

Where this goes#

Every one of these grounds is something a human applies with judgement, case by case. Next week looks at what happens when a machine has to make this same decision automatically, in real time, with no human available to ask, because that is exactly what a file-sync service does, constantly, and mostly gets away with.