Recorded, deterministic proof

Make stale prose fail loudly.

One binding connects a command in source to its README claim. When the source changes alone, the check fails with the exact stale region; repair rewrites that region and nothing else.

Evidence sha256: a654988941be1e2c8111ddb17cd4a6351f3ca2ccfa3b8d92215b984db299f4ce

Binding: public-command

Source · command.txtclean-docs check --changed
mismatch
Document · README.mdclean-docs check

The complete loop

One binding. Three observable states.

The source changes in state two. The document is left untouched until the declared repair runs in state three.

01

Current

Source and README agree. The gate has nothing to repair.

clean-docs check exit 0

[current] public-command: README.md
02

Drift caught

The source changed; the README did not. The gate names the stale binding.

clean-docs check exit 1

[drift] public-command: README.md
--- README.md
+++ README.md (derived)
@@ -7,5 +7,5 @@
 ## Command
 
 <!-- clean-docs:begin public-command -->
-clean-docs check
+clean-docs check --changed
 <!-- clean-docs:end public-command -->
03

Repaired and verified

The declared region is regenerated, then the same check passes.

clean-docs drive exit 0

[repaired] public-command: README.md
--- README.md
+++ README.md (derived)
@@ -7,5 +7,5 @@
 ## Command
 
 <!-- clean-docs:begin public-command -->
-clean-docs check
+clean-docs check --changed
 <!-- clean-docs:end public-command -->
drive: repaired 1 document(s); implemented policy checks passed

clean-docs check exit 0

[current] public-command: README.md

Why this demonstration exists

See the failure before adding the gate.

Maintainers deciding whether source-bound documentation is worth adding to a repository.

What is running

  • No account, credentials, backend, or database.
  • The outputs below come from a generated temporary repository.

Evidence boundary

What this proves.

Try the same loop in a repository.