-
v0.4.1 - the documents describe what is running
released this
2026-09-14 05:50:46 -04:00 | 0 commits to main since this releaseNo capability was added. Every change since v0.4.0 is in docs/ and README.md;
src/, tests/, fixtures/ and deploy/ are byte-identical, and the composer this
tags is the composer v0.4.0 tagged. Suite 643 passed, oracle unchanged at
ddd0f154.v0.4.0 said this project tags on a change in kind. This is one, though not to
the software: before this tag the documents and the machine disagreed in
eleven places and nothing recorded that they did.All eighteen documents were read against the code. What came out:
-
DIVERGENCES.md, a register of requirements that stand and are not met.
FAILURES.md records something that went wrong; this records something that
is wrong now. Six entries, one already closed - and closed because it had
been written backwards, against the one document that had the fact right. -
ENVIRONMENT.md gains DIVERGENCE as a seventh marker. It had six ways to say
how strong a requirement was and none to say it was not being met. That gap,
not carelessness, is why five unmet REQs went unrecorded for weeks. -
PROCESS.md records the delivery chain end to end, explained to every new
assistant for months and written in no document until now. -
Derivable state is deleted rather than corrected. HANDOFF sections 3 and 12,
PROCESS section 10, STAGING-STATE section 5, ROADMAP section 4: commit
hashes, test counts and a transcribed commit log, all reported by git and
pytest, all wrong. Every stale claim found in this audit was written in the
present tense. FAILURES.md is the only document here that cannot rot, and
the reason is its form rather than its discipline. -
Three statements in IDENTITY-CONTRACT.md that an outside implementer would
have taken as descriptions of what runs. G-1 warns against exactly that, in
the document G-1 was filed against. -
ROADMAP section 7 is marked binding. Eighteen principles cited by number as
settled law sat inside a document whose header said nothing in it was a
promise. -
PRECISION section 7's prismatic entry is labelled a limit rather than a
boundary, with the reason recorded: the oracle is a two-dimensional oracle
with a scalar length multiplier, and volume equals rounded section area
times length to within 3.6e-12 across all 113 accepted cases.
DIV-001 is the first thing the next session should fix. AGPL section 13
obliges a source link on a deployed web tier, the composer has been public
since 2026-09-11, and the served page carries none. It is stated as unmet in
three documents and is the only finding here with a consequence outside the
project.Downloads
-