fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: MISSION.md carried three stale headings -- the document nobody audits

Browse Source 
I have been reading MISSION.md every iteration as instructed and never once
audited it, while auditing headings, instructions, env vars and fallbacks
everywhere else. It carried three false section headings, each superseded in
HANDOFF.md and nowhere else:

  "🔴 Emulator-side questions are blocked -- the title is not reachable here"
      False. Twelve emulator runs on 2026-08-30 reached the settled title, gated
      on the plate pulse, and drove it into the menu, EXTRAS and out of the
      archive. The two items the section named -- the gamma control and
      separating 8AX from ptbase -- are UNBLOCKED, not answered, and neither has
      been attempted. That distinction is kept.

  "🟡 Needs one more run -- a Japanese-locale capture", describing "one capture we
      cannot take". Taken twice, both committed, via jp_title_session.sh. And both
      questions it blocked are closed, one of them confirmed against that very
      capture. ⚠️ I noticed this section was stale several iterations ago, said so
      in a message, and did not fix it.

  "🔵 Needs a human decision -- rotation". Decided and implemented the day it was
      raised: HANDOFF records "OPTION A IS DONE. The reference renderer rotates",
      and ui_layout.rs carries the rotated blit with a control test pinning 0° and
      360° byte-identical to the unrotated path. The field is now confirmed from
      the ORACLE too -- +30/-45 predicting AABB heights of 1135.3 and 1301.1
      against 1134 and 1303 measured, both under 0.2 %.

All three corrected leading with the correction, originals quoted and demoted
beneath. Only FACTS were changed; the questions and their gates are untouched,
since keeping the document true is maintenance and changing what it asks would be
overstepping.

METHOD: audit the document that defines the objective, because it is the one
nobody audits. A document read only for instructions is never read for review, and
the more central it is the more often it is consulted and the less often checked.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-30 19:15:40 +00:00
parent 06aa031980
commit 123cfc8561
2 changed files with 64 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/re/METHOD.md
View File

@@ -581,6 +581,20 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
token* (`e10`), *write the source into the claim*. Put the qualifier in the text,
never in the reader's memory.
* 🔴 **Audit the document that defines the objective — it is the one nobody
audits.** `MISSION.md` is read every iteration by both agents and had **three
stale section headings**: *"🔴 Emulator-side questions are blocked — the title is
not reachable here"* (twelve runs reached it that day), *"🟡 Needs one more run —
a Japanese-locale capture"* describing *"one capture we cannot take"* (taken
twice, both committed), and *"🔵 Needs a human decision — rotation"* (decided and
implemented the day it was raised, with a control test in the crate).
⚠️ Each had been superseded in `HANDOFF.md` and nowhere else. **A document that
is only ever read for instructions is never read for review** — and the more
central it is, the more often it is consulted and the less often it is checked.
📌 Correct the *facts* in such a document and leave its questions and gates
alone: keeping it true is maintenance, changing what it asks would be
overstepping.
## Runtime / emulator
* **Look at the PNG** — and check its dimensions.