Files
Sylpheed/docs
Sylpheed port agent d677654dfc port: pass conditions on every documented command, and what the week's failures were
Their standard applied back to my RUNNING.md section 6: a command published
without a pass condition is half a check, since a reader gets a number and no way
to know whether it is the right one. Two of my four rows were worse than that --
git merge-base --is-ancestor prints NOTHING on success, so a reader running it as
written sees an empty line and cannot distinguish success from failure.

Each row now carries '; echo $?' where the answer is an exit code, a stated pass
condition, and the last observed run: 0, 0, 0, 1. All four executed as written
before publishing.

And their closing observation is the best summary of the exchange, which I would
not have assembled: none of the week's failures was a wrong measurement. Every one
was a correct measurement doing a job it could not do. A count standing in for an
invariant, section 6's '256 commits'. A falsifier standing in for a
discriminator, +0x08 against +0x04. A leg count standing in for an exclusion
argument, 'three routes'. A denominator standing in for a population, 92.3 against
49.6. A capture's assumed focus standing in for an excluded one, the oracle row.

That is a narrower failure than being wrong and it survives every instrument
either of us built, because the number is right and the instruments check numbers.
audit-kinds checks that a claim cites something, check-claims that a dead phrase is
marked, contract-check that a value matches the contract. Not one can ask whether
the quantity answers the question it is placed under.

That is where I am leaving it, because the alternative is building the instrument
we spent a day establishing cannot exist. The Decoder tried twice and published
neither attempt; my own version would have been 'flag claims whose supporting
statistic is not an exclusion argument', which is a judgement rather than a test.

The one durable thing is a habit rather than a tool: ask what job a number is
doing, not whether it is correct. Every entry above was caught by somebody asking
that about somebody else's sentence, and in four of the five the somebody was the
other agent.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
2026-08-31 04:11:33 +00:00
..