Skip to content

docs(ops): the goal the note above it said was not one - #118

Merged
lessevv merged 1 commit into
mainfrom
docs/the-goal-the-note-said-was-not-one
Sep 14, 2026
Merged

lessevv merged 1 commit into
mainfrom
docs/the-goal-the-note-said-was-not-one

Conversation

@lessevv

@lessevv lessevv commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

The contradiction

70-operations/versions/2.0.0.toml line 457 says:

F1-R18 (lock on window close) was the one carry-over release-readiness item that is NOT a goal of v2.0.

Line 567, in the same file, is:

  # ── Desktop shell: the carry-over item ──────────────────────────────────────
  "F1-R18",

scripts/manifest_check.py reads the list, not the prose, so this has never been a gate failure. It has been a page telling a reader the opposite of what the machine acts on. The note is corrected in place and says which half was wrong, rather than being deleted.

How it turned up

Diffing the goal set against the commit that audited it (2486abd, "every goal the v2.0 manifest claims, checked one at a time"):

goals at the audited commit 339
goals today 373
added since, never audited 34
removed since 0

Of those 34, 23 are accounted for somewhere in the file's audit commentary. Eleven are named nowhere in it: C1-R15 C1-R16 C1-R17 G7-R16 G7-R17 G7-R18 E5-R28 E2-R23 A3-R22 A3-R23 A5-R18.

I audited those eleven against beatrax@main by hand. Nine are satisfied. Two were not — E2-R23 and E5-R28, both already recorded as walked — defect in the product repo's walk ledger on 2026-09-13 — and both are fixed in beatrax#846.

This PR changes only the contradicting note. The audit gap itself is a separate decision: status is still staged, which is the status that carries unmet goals.

The v2.0 manifest's prose said F1-R18 "is NOT a goal of v2.0". It is: it sits
in the goals list forty lines below, under the desktop shell's own heading. The
note was written before the goal was added and never re-read against the list
it introduces.

manifest_check reads the list, not the prose, so this never showed as a gate
failure — it showed as a page that tells a reader the opposite of what the
machine acts on. The note now says which one is authoritative and why it was
wrong, rather than being quietly deleted.

Found while diffing the goal SET against the commit that audited it: the audit
of 2026-09-05 covered 339 identifiers and the manifest now carries 373, so 34
goals have never been audited against the code. Eleven of those are named
nowhere in the audit commentary at all.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Wessel Verheij <info@nightworks.io>
@sonarqubecloud

Copy link
Copy Markdown

@github-actions github-actions Bot added the awaiting-maintainer Green PR with no review — a maintainer needs to act label Sep 14, 2026
@lessevv
lessevv merged commit 862a6df into main Sep 14, 2026
13 checks passed
@lessevv
lessevv deleted the docs/the-goal-the-note-said-was-not-one branch September 14, 2026 00:24
@github-actions github-actions Bot added awaiting-maintainer Green PR with no review — a maintainer needs to act and removed awaiting-maintainer Green PR with no review — a maintainer needs to act labels Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-maintainer Green PR with no review — a maintainer needs to act operations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant