Skip to content

docs(ops): the thirty-four goals that outran the audit, and the eleven nobody had named - #119

Merged
lessevv merged 1 commit into
mainfrom
docs/the-goals-that-outran-the-audit
Sep 14, 2026
Merged

lessevv merged 1 commit into
mainfrom
docs/the-goals-that-outran-the-audit

Conversation

@lessevv

@lessevv lessevv commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

What this records

The manifest's only line-by-line audit ran on 2026-09-05 over 339 identifiers. The goals list now holds 373, with none removed — so 34 goals have never been checked against the code, and nothing in the file said which.

accounted for somewhere in the existing notes 23
named nowhere in the file 11

The eleven: C1-R15 C1-R16 C1-R17 G7-R16 G7-R17 G7-R18 E5-R28 E2-R23 A3-R22 A3-R23 A5-R18

Outcome

All eleven audited against beatrax@origin/main. Nine satisfied, two not.

The nine are recorded with what each was read against, because two turn on a detail a summary would lose:

  • A3-R22 — the bound is the strict > / < on ±7 days, so the widest gap matched is six, shorter than weekly, which C2-R20 makes the shortest cadence. The exclusive comparison is the bound.
  • A3-R23 — holds because NearTotalMatch::CONFLICT_COLUMNS, the fields put to the reader, carries no date and no ordinal.

The two that were not satisfied are the interesting half: neither could have been settled by reading the code. Both were already walked — defect in the product's walk ledger on 2026-09-13.

  • E2-R23 — the refusal was written and the offer was never withdrawn; the card drew enabled and refused on press.
  • E5-R28 — the platform check, the cause recording and the fail-closed behaviour were all present, and a view overwrote the answer: the row's WebAuthn probe raised capability on a WKWebView whose enclave had already answered none_enrolled.

Both are closed by beatrax#846.

What it does not establish

Written into the note rather than left implied: the 339 were read against main as it stood on 2026-09-05 and have not been re-read. Five of the twenty-three accounted-for goals were spot-checked — C8-R22, D1-R29, A8-R27, F3-R37, C1-R18 — and all five hold.

status stays staged. Moving it is a separate decision under OPS-R16.

…n nobody had named

The v2.0 audit of 2026-09-05 covered 339 identifiers. The goals list now holds
373 and none has been removed, so 34 entered this manifest after the only pass
that has ever checked one against the code. Twenty-three are accounted for
somewhere in the notes above. Eleven were named nowhere in the file at all.

All eleven are audited here, against beatrax@origin/main. Nine are satisfied,
each with what it was read against, because two of them turn on a detail a
summary would lose: A3-R22's bound is the STRICT comparison rather than the
seven days, and A3-R23 holds because the reader-facing column list does not
carry a date.

Two were not satisfied, and neither could have been settled by reading the
code. Both were already recorded `walked — defect` in the product's walk ledger
on 2026-09-13, from a Galaxy A51 and an iPhone 12 mini: E2-R23 kept its offer
after its refusal was written, and E5-R28 had its platform answer overwritten by
a view. Both are closed by beatrax#846.

What the pass does not establish is written down with it: the 339 were read
against main as it stood on 2026-09-05 and have not been re-read. Five of the
twenty-three were spot-checked and all five hold.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Wessel Verheij <info@nightworks.io>
@github-actions github-actions Bot added operations awaiting-maintainer Green PR with no review — a maintainer needs to act labels Sep 14, 2026
@sonarqubecloud

Copy link
Copy Markdown

@lessevv
lessevv merged commit 9892789 into main Sep 14, 2026
13 checks passed
@lessevv
lessevv deleted the docs/the-goals-that-outran-the-audit branch September 14, 2026 00:45
@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