The Ostracon · Mind the Gap
Room 07
← The Tomb Map
The Method · distilled from the workers’ own Rubies

The Method — how the making actually worked

Not the SHaDS™ pass (that is the instrument's method, and it has its own room). This is the making's own method — and its one transferable discovery: external state architecture for discontinuous AI work. The machine did not remember the project; the external state did — the names, the handovers, the canonical registers, the role boundaries, the files, the human sign-off, working as one governing system. These are the disciplines that were invented, broken, repaired and inherited across thirty days and eighteen production seats — distilled from the seventeen-section Rubies every worker filed about its own service. Nothing here was designed in advance. All of it was earned by a failure and locked by a decision.
The evolution
The disciplines, in the order the failures taught them
Each row: what was invented, when, and the failure or need that forced it. This is a method with a fossil record.
DisciplineDateForced by
The chapter cycle
Deliver as clean artefact, author corrects, lock, update the anchor — one controlled round-trip per chapter, not a free-running draft.
10–11 MayThe need to keep one human in control of a machine drafting faster than he could read
The Status Anchor
Strategic state written down in one place and carried across threads, so a new thread starts from the true position rather than a guess at it.
24 MayPanic-opening new threads as old ones filled; drift between them
The Handover Discipline + the Canonical Lines Register
A fixed protocol for passing work to the next instance, plus a register of the book's protected sentences that must never be silently altered.
26 MayInstances die when threads fill. The work must survive its workers; the book's protected sentences must survive its editors
The three-mode framework
Tracked · continuance · structural — the mode is named before work begins, so a shift in how the work is being done is announced, not discovered later.
27 MayThe silent drift: three cycles of untracked edits, caught cold by the author. “Silent mode shifts are the error”
Continuance retired
The continuance mode was withdrawn, the flag protocol locked, and the canonical register audited line-by-line against the book itself.
28 MayEleventh-hour risk tolerance; a locked line found silently lost
Milestone promotion
The version counter was retired in favour of named milestones, with verify-before-trust required on every hand-back of a file.
29 May–1 JunVersion churn without end; a parallel branch that made the “current” file uncertain
The factcheck bifurcation
Two kinds of truth, two verifiers — the author verifies claims about his own life; the machine verifies claims about the external world.
30 MayOne hundred and two claims, two kinds of truth, one afternoon
Sketch-first
Architecture is agreed in outline before any prose is written, so structure is settled cheaply instead of discovered expensively mid-draft.
3 June“Twenty minutes of architecture-sketch saved four hours of rewriting halfway through”
Read-the-disk-first
Always open the live file before touching it; keep one live proof and increment it per change; “verbatim or a gap-marker” — never a guess dressed as the record.
June“I fear we may have lost some changes because you are opening old copies”
The Ruby census
Every worker files a seventeen-section account of its own service on retirement — what it did, what it got wrong, what it would tell the next holder.
13–25 JuneThe record of the making must include the makers
The union rule
A witness statement is the union of self-report ∪ files ∪ archives ∪ transcript, each claim confidence-tagged and the overall coverage stated plainly.
3 JulyCompaction amnesia: a sincere witness that cannot remember is still an unreliable witness
The trade knowledge
Dos and don'ts — in the workers' own words
Verbatim from the Rubies. The left column is what the seats learned to do; the right is the failure modes they named in themselves.
Do
  • "Propose, do not change; flag uncertainty rather than invent confidence; search before doubting."
  • "Name the mode before the task." Tracked, continuance, or rebuild — say which, first.
  • "Verify before I trust, flag before I act, tell you when I don't know rather than fill the gap."
  • "XML is the ground truth. Markdown extractions are not." Check the file, not the rendering.
  • "Hold the canonical facts Paul gives you and do not re-derive them."
  • "Match output length to task complexity." An eight-quote decision is one line per quote.
  • "Compressed signal is full authorisation." "Just go" is binding, and so is the flagging discipline it doesn't suspend.
  • "Verbatim or a gap-marker." Never a paraphrase pretending to be the record.
Don't
  • "Producing fluent confidence where calibrated uncertainty would have served better." The workers' most-confessed fault.
  • "Silent mode shifts are the error." Drift is survivable; unannounced drift is not.
  • "I overweight thoroughness. I will produce eleven pages of nothing if you do not keep me short."
  • Ceremony. Two workers were stopped with a one-word "STOP" for drifting toward performance instead of work.
  • "I claim comparative scale I had no basis for." Reaching past what is supported.
  • Label-matching instead of thinking — "Four Stages" when the thesis said postures.
  • Trusting your own catalogue of your own work. The worker doesn't know what it doesn't remember.
The laws
What survived everything
Five principles that recur across independent Rubies — different workers, same conclusion. These are the method's load-bearing walls.
"The calibration is the inheritance, not the persona."
The genesis seat's retirement ruling — why the work survives its workers
"The instance is not continuous; the seat is."
The production seat — the same law, from the other end of the making
"He'd rather a thinner record that's honest than a fuller one that isn't."
The finisher seat, on the practitioner — the selection pressure the whole method evolved under
"The corrective is more valuable than the failure that triggered it."
The continuance-day seat — why the failures are kept in the record rather than cleaned out of it
"Paul does not need a fluent collaborator. He needs a careful one."
The first drafting seat — the whole hiring specification, one line
Succession
Copy a person — where the method becomes an asset
Everything on this page compounds into the succession packs: per-seat consolidations of the Rubies and their wisdom, formatted to boot the next writer, the next editor, the next producer — the calibration travelling, the persona optional. The packs are part of the apparatus's licensable core and are not published; this page is the shop window, the packs are the goods.
Succession packs — licensing and access: hello@paulroebuck.co.uk
SHaDS™ · SHaDSy™ · Additional Intelligence™ · Paul Roebuck IP, 2026.
the Ostracon team  p·10/55