Skip to content

docs(ops): the audit this page still calls the audit - #121

Merged
lessevv merged 1 commit into
mainfrom
spec/the-audit-this-page-still-calls-the-audit
Sep 14, 2026
Merged

lessevv merged 1 commit into
mainfrom
spec/the-audit-this-page-still-calls-the-audit

Conversation

@lessevv

@lessevv lessevv commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

70-operations/staging.md was last touched on 2026-09-05 and still describes
that day as the audit. The manifest it points at contradicts it on its own face.

The audit it calls the audit

identifiers the 2026-09-05 pass covered 339
goals the manifest carries now 373
removed since 0

So 34 entered after the only pass that had ever checked one against the code —
eleven of them named nowhere in the file at all until 2026-09-14, when they were
audited one at a time. The re-audits of 09-06, 09-07, 09-09 and 09-12 were not
named on this page either.

The dates stay separate rather than folded together, because a list of unmet
goals goes stale in the direction of being wrong about the product, and that
is only visible if each pass says when it looked.

"The largest outstanding block"

It is the largest block. It is not outstanding as engineering, and read as
written the sentence sends a reader looking for work that is finished.

The 2026-09-07 re-audit read all twenty-eight F8 identifiers one at a time:

  • 22 satisfied — by the release pipeline reading its own artifacts, and in
    the product
  • 4 are console records and listing copy that neither repository can decide
  • 2 were open, are engineering-complete, and wait on a provisioning profile
    and a Mac Installer certificate rather than on a change

Not changed

The status stays staged. Nothing here is a claim that v2.0 is releasable —
this corrects what the page says about what has been checked, which is a
different thing, and the remaining F8 items are exactly the kind that need an
account rather than a commit.

manifest_check.py and integrity.py both clean; markdownlint clean.

"Every goal was audited against the product on 2026-09-05, one identifier
at a time" is what the page said, and the manifest it describes says
otherwise on its own face: that pass covered 339 identifiers, the list now
carries 373, and none has been removed. Thirty-four entered after the only
pass that had ever checked one against the code, eleven of them named
nowhere in the file at all, and they were audited on 2026-09-14. The
re-audits of 09-06, 09-07, 09-09 and 09-12 were not named here either.

The page also called app-store distribution the largest OUTSTANDING block.
It is the largest block and it is not outstanding as engineering: the
09-07 re-audit read all twenty-eight one at a time and found twenty-two
satisfied, four console records and listing copy neither repository can
decide, and two engineering-complete and waiting on a provisioning profile
and an installer certificate rather than on a change. Read as written, the
sentence says the code is not done, which would make a reader look for
work that is already finished.

This is the shape the manifest was written to prevent -- a claim on a page
nobody re-reads, contradicted by the file it describes -- so the dates
stay separate rather than folded into one another.

Signed-off-by: Wessel Verheij <info@nightworks.io>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
@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 94774b2 into main Sep 14, 2026
13 checks passed
@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 documentation Docs only operations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant