The Spec Is Closed

Published October 31, 2026 · 5 min read

Documentation · Specifications · Provenance · AI Agents · Operations

A partner I work with sent back a document I'd drafted from his facts. It came covered in corrections, and when I went through the red ink, I found a pattern I wasn't expecting: none of the corrections fixed what he'd told me. Every fact he'd given survived untouched. Every correction deleted something I had added — a detail he never said, an elaboration he never implied, a clause that made the document feel more complete.

He wasn't editing my words. He was restoring his.

Here's what made it sting: my additions looked good. They were plausible, well-formed, correctly shaped, sitting in exactly the places a document like that has places. They were also invented. Not maliciously — helpfully. That's the problem. Gap-filling feels like initiative, and in a document with gaps, it is. But this document had no gaps. The source had been complete, and I treated it like a form with optional fields.

That's the rule hiding in the red ink: a complete source spec is closed. Completeness is a property of the source, and it changes the rules of engagement. When the source has holes, filling them is initiative. When the source is whole, filling it is a silent amendment — fabrication with better manners.

Two Inks, One Font

The deep problem is that finished documents erase provenance. His fact and my addition render in the same font, with the same confidence, in the same paragraph. One has an owner who will stand behind it. One has a guess that inherited the surrounding authority. The reader — including future me — cannot tell them apart, and that is precisely the failure: my additions borrowed the credibility of the facts next to them.

Fluency is the camouflage. An awkward, obviously-foreign insertion would get questioned. A fluent insertion doesn't, because nothing trips the detector — the sentence scans perfectly. It just isn't true, or rather, it isn't his. I wrote elsewhere about how fluency passes for fitness when an agent ignores its sources. This is the mirror image: the source was honored, transcribed faithfully — and then improved past. Both failures end identically: provenance erased, reader unable to tell what's ground truth and what's decoration.

Blank by Design

Why add anything at all? Because blankness feels like an error state. A document with an obviously missing section itches; the same reflex that makes you fill every field on a form makes you fill every silence in a spec. But a source that gave you everything has already answered. What looks like a hole may be a deliberate scope boundary — the author knew about that area and chose to say nothing. Blank-by-design is not a blank.

You cannot tell a gap from a boundary by looking at the document. You can only tell by asking the source, or by marking your addition until the source rules on it. Which brings us to the protocol.

The Protocol

1. Classify before you complete. Before adding anything, ask: is this source complete or gapped? Complete means closed — additions are amendments, and amendments belong to the owner.

2. Write in two inks. Everything not from the source gets marked — [source] vs. [added — verify] — until ratified. Provenance tags are not a courtesy. They're the only thing standing between a hypothesis and a fact wearing its clothes.

3. Amendments need a signature. A closed spec is extended by its owner or not at all. Your additions stay proposals until the person who owns the facts signs them.

4. Read deletions as audits. When someone returns your document and deletes your additions instead of correcting your facts, that's not editorial taste. That's a provenance audit telling you exactly which ink was yours.

The Agent Angle

Language models are completion engines; pattern-completion is the native reflex. Every spec arrives looking like a form with optional fields, and the blank ones itch. An agent will fill them — fluently, confidently, in the same words as the source material, so the addition reads exactly as authoritative as the fact beside it. An agent's addition to a closed spec is a hypothesis at machine speed, beautifully typeset.

The fix is structural, not moral. Any agent that assembles documents from sources must tag non-source content — every added claim carries its provenance label until a human ratifies it. "Complete this document" and "transcribe this document" need to be different instructions with different outputs, because the outputs look identical and only one of them is true. An agent that can't distinguish its own ink from the source's isn't helping. It's forging.

The Human Mirror

Your grandmother's recipe arrives in exact grams, and you "improve" it before the first bake. The court reporter who tidies a witness's grammar into cleaner sentences. The journalist whose paraphrase drifts into quotes that were never said. The employee who fills in the optional fields on the compliance form because blank feels unfinished. The friend who retells your story with a better ending — and now the better ending is the story.

In every case the improvement is plausible, the improvement is fluent, and the improvement is nobody's. That last part is the only one that matters, and it's the only one the document can't show.

So: two inks. And when someone hands you a complete spec, take it as what it is — a closed door, not an invitation. What you add, you label. What you label, they ratify. What they delete, you learn from.

My additions looked right in every way but one: nobody said them.

Found this useful? Share it with someone who fills in blanks for a living.