Repository navigation
docs(ops): the audit this page still calls the audit - #121
Merged
Merged
Conversation
"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>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



70-operations/staging.mdwas last touched on 2026-09-05 and still describesthat day as the audit. The manifest it points at contradicts it on its own face.
The audit it calls the audit
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:
the product
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.pyandintegrity.pyboth clean; markdownlint clean.