THE BOOK DRIFTS FROM THE CODE

The system changes.
The sentence stays.

Documentation is a copy of the system, and copies rot. Every count in it was true on the day it was typed.

How do you stop documentation drifting from the code?

Derive what the system already knows, and check identities rather than totals alone. HAUSE builds its collection from a pinned library manifest and an ingested documentation snapshot. A manifest entry without documentation fails the build. This chapter compares those two inventories, deliberately removes an entry from a copy, and restores it. That checks a specific release: it does not prove the site follows every later library change or that every prose claim is current.

01 / EXPERIENCE THE DIFFERENCE

Derive the facts the system already knows.

REAL MANIFEST + DOCUMENTATION SNAPSHOT / INGESTED 2026-09-26

Break the copy, then restore the source
PINNED MANIFEST37
INGESTED DOCUMENTATION37
HeroStatementObservationClaimEvidenceQuestionTimelineConnectionRefusalExcerptAnswerSnippetAnatomyDecompositionExpertFieldComparisonVariantsLadderAgreementDerivationByteMapFollowRevealTerminalGatingProvenanceLensCitationStagedTransitionTextCorrectionTransformationUnfoldingCompilationProcessionMagnitudeChannelQuantisationFilm

The identities agree.

Names match in both directions. This checks the documentation snapshot against the pinned manifest; it is not three independent measurements.

PINNED MANIFEST37
ALTERED COPY36
Hero / MISSINGStatementObservationClaimEvidenceQuestionTimelineConnectionRefusalExcerptAnswerSnippetAnatomyDecompositionExpertFieldComparisonVariantsLadderAgreementDerivationByteMapFollowRevealTerminalGatingProvenanceLensCitationStagedTransitionTextCorrectionTransformationUnfoldingCompilationProcessionMagnitudeChannelQuantisationFilm

Hero has disappeared.

One entry was deliberately removed from a copy. The identity check exposes the gap. The real files have not changed.

PINNED MANIFEST37
INGESTED DOCUMENTATION37
HeroStatementObservationClaimEvidenceQuestionTimelineConnectionRefusalExcerptAnswerSnippetAnatomyDecompositionExpertFieldComparisonVariantsLadderAgreementDerivationByteMapFollowRevealTerminalGatingProvenanceLensCitationStagedTransitionTextCorrectionTransformationUnfoldingCompilationProcessionMagnitudeChannelQuantisationFilm

The identities agree.

Names match in both directions. This checks the documentation snapshot against the pinned manifest; it is not three independent measurements.

Matching totals alone are not enough: the check compares identities and detects missing or unexpected names. This site uses a pinned library revision. Automated source checks verify every shared file against that revision.

02 / HOW YOU MEET IT

A specimen book cannot drift from its library when it is the library.

This site had it. A specimen page read twenty-eight of twenty-eight while the library held thirty-five forms, and all seven performances while there were eight. Both sentences were true the day they were typed, both were quietly false a fortnight later — on a site whose entire argument is that the book cannot drift from the library.

03 / BENEATH THE SURFACE

Why the failure keeps returning.

Prose is faster to write than a projection, and a number inside a sentence has no owner. Nothing fails when it goes stale: the page still builds, still renders, still reads well. Drift is the only kind of bug that gets more convincing with age, because the sentence around it keeps sounding authoritative long after the number stopped being true.

TAKE THE RESPONSE WITH YOU

Give it a form.

Agreement

N independently-derived values that must be identical — with a FAIL row.

Evidence

Rows of labelled findings with status marks — receipts, not decoration.

Claim

An assertion that knows it must answer to evidence.

Derivation

A value folded down a graded scale by caps — derived, never asserted.

PUBLISHED 31 AUG 2026 · REVISED 9 SEP 2026 · VERSION 1.1

CITE

site build fb3ec31 · built 2026-09-26

CITE THIS

Article · 1.1

Hay, C. (2026). The book drifts from the code. In HAUSE — the problems (Version 1.1). hause.design. https://hause.design/problems/the-book-drifts-from-the-code

An argument is a published object: dated, versioned, and referenceable — which is the subject of one of these pages and the practice of all of them.

HAUSE · THE SPECIMEN BOOK / 2026

GITHUB →VINDEX3.ORG →CHRISHAYUK →