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

re: my own MISSION correction was wrong on all three clauses

Browse Source 
Two iterations ago I corrected MISSION.md's stale "🔴 Emulator-side questions are
blocked" banner and wrote, in its place, that the two items it named were
"unblocked, not answered ... both need a running menu, both now have one, and
neither has been attempted". I wrote that without reading either page.

Reading them:

  8AX vs ptbase was RESOLVED on 2026-08-29. Its status line says so -- both its
  questions closed, page kept for the evidence.

  The gamma control was attempted and half-answered, and its page records that
  the run "needed the emulator only to BOOT, not to reach a menu ... parked behind
  the title-screen blocker for no reason".

  So neither item ever needed a running menu, and the section's premise was wrong
  independently of whether the menu was reachable.

All three clauses false. The failure is specific and worth naming precisely:
replacing a stale status with an UNCHECKED one, in the same edit that criticised
the document for carrying unchecked status. sylpheed-port wrote a dead instruction
inside the commit fixing dead instructions; this is that shape, one document over.

METHOD: a correction is a new claim and needs the same check as the claim it
replaces. The urge to correct supplies confidence the correction has not earned --
check a replacement as hard as the thing it replaces, and hardest when the edit is
about checking.

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:29:17 +00:00
parent 897be7bfdd
commit 2ea7b7eb3d
2 changed files with 33 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/re/METHOD.md
View File

@@ -631,6 +631,21 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
fitting the instrument to the answer. Left over-reporting, which is the safe
direction.
* 🔴 **A CORRECTION is a new claim, and needs the same check as the claim it
replaces.** Correcting `MISSION.md`'s stale "emulator-side questions are blocked"
banner, I wrote that the two items it named were *"unblocked, not answered … both
need a running menu, neither has been attempted"* — **without reading either
page**. All three clauses were false: one item had been **resolved** the previous
day, the other had been **attempted and half-answered**, and its own page records
that the experiment *"needed the emulator only to boot, not to reach a menu —
parked behind the title-screen blocker for no reason"*. ⚠️ The failure is
specific: **replacing a stale status with an unchecked one, in the same edit that
criticised the document for carrying unchecked status.** `sylpheed-port` wrote a
dead instruction inside the commit fixing dead instructions; this is the same
shape. **The urge to correct supplies confidence the correction has not earned** —
so check a replacement as hard as you checked the thing it replaces, and hardest
when the edit is *about* checking.
## Runtime / emulator
* **Look at the PNG** — and check its dimensions.