Repository navigation
docs(affirmation): re-anchor at 6d19ce0e, refs #787 - #1215
Merged
Merged
Conversation
Drafted by Claude from local runs at the anchor; affirmed by the owner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013omQK26s4uDjJMkdqNEvEG Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 31 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
K9 contract conformancerun https://github.com/hyperpolymath/standards/actions/runs/37907987240 K9 normative contract typecheckK9 contract self-testK9 conformance fixturesK9 corpus conformance (L2) |
|
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
1 participant
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.
Summary
Refreshes
docs/AFFIRMATION.adoc(profile B) at anchor6d19ce0ebae047027dcfd594c7810bf35c642faa, and keeps the 2026-10-07 file verbatim atdocs/affirmations/AFFIRMATION-2026-10-07.adoc. Claude re-ran the checks at the anchor on 2026-10-09 between 08:05Z and 08:27Z and drafted the file. The owner affirms it with the signed commit in this PR, whose parent is the anchor.Why a refresh. The 10-07 affirmation (#1203) did not land anchored.
scripts/verify-affirmation-anchor.sh hyperpolymath/standards 1203printedDRAFT(rc=1) at 08:07:49Z for three reasons:f777d7c4has parent58db3356, not the anchor85aa1934;e35431d5has first parenta709d3a6, becausemainmoved (docs(roadmap): point the Projects board at metadatastician/projects/2 #1202) before that PR opened;The new file says so in "Changes since the 2026-10-07 affirmation", and it calls itself a draft unless it lands as its "When this file is anchored" note describes.
Refs #787. Closes: none.
Type of change
📌 New pins
76773445d8b0c3a2558f33cc426bacc638206a6f. This is the owner's signed commit, the one CI runs on.6d19ce0ebae047027dcfd594c7810bf35c642faa. It is the head's parent, and it wasmainwhen this PR opened.uses:SHAs,actions.lockentries, lockfiles or container digests are added or changed.canon.lockis untouched.How has this been verified?
The two files:
asciidoctor -S safe --failure-level=WARN -o /dev/nullreturned rc=0 with no output on both files. A planted out-of-sequence section returned rc=1, so the gate can fail.<<xref>>resolves to an anchor in its own file, checked withcomm -23, because Asciidoctor 2.0.26 does not report a dangling xref.cmpagainste35431d5:docs/AFFIRMATION.adocreturned 0.Commit (HEAD)appears exactly once in the new file, holding the full 40-hex anchor.verify-affirmation-anchor.shreads the anchor from that row. The archive still carries the old SHA in its own row, so pass the anchor explicitly (below).The repo's own hooks, with a throwaway unsigned commit of exactly these two files in a scratch clone at the anchor (never pushed):
.githooks/pre-commit: rc=0. With a.envholding a plantedghp_token staged beside the two files, it returned rc=1 and flagged.env:github-pat:1. Its gitleaks pass cannot see these two files, because gitleaks 8.16.0 skips every path ending indoc(inbox, 2026-10-09). So this rc=0 says nothing about secrets in them..mdcopies of both files, with.gitleaks.tomland itsconfig/gitleaks/estate-baseline.tomlfrom the anchor: no leaks (rc=0). With a plantedghp_token beside them, it returned rc=1 and flagged only the plant. CI'ssecret-scanner-reusable.ymlruns its own AsciiDoc pass..githooks/commit-msg: rc=0 on the full messageowner-actions.shwrites, with one warning that the subject is over 50 characters. A 90-character subject gave rc=1..githooks/pre-push: rc=0, all seven validators passed. A planted workflow with no SPDX header gave rc=1.What the file records at the anchor:
check-canon-lockstep.sh: 7 passed / 0 failed / 3 skipped by design.check-rsr-profile.shandcheck-standards-map.sh: Gate D, 124 records.check-uuid-v8.sh --strict, anduuid-v8-test.shwith PASS=32.check-ijson-jcs.sh(report-only) found 0 of 62 JSON files canonical.build-registry.sh --checkreports DRIFT. The registry and scorecard tests report 7 passed / 2 failed each, and three scorecard rows claim PASS while their check exits 1.Registry + topology in syncandRepo self-tests. All 8 were already failing at85aa1934, and none is required. All three required contexts passed.Checklist
git commit -Sviaowner-actions.sh reanchored. Claude made no commit. Before opening this PR, the opener checked thatgit log -1 --format=%G?printsGon the head; it refuses to open the PR otherwise.SPDX-License-Identifier: both files are prose and start with// SPDX-License-Identifier: CC-BY-SA-4.0. No existing file was relicensed.Notes for reviewers
Deferred red check (§5c):
Registry + topology in syncfails on this head (7677344) and at the anchor6d19ce0ealike. It is the registry drift that the file itself records, it is not required, and this PR does not change it. Tracked in #1161 (section 2).Deferred red check (§5c):
Repo self-testsfails on this head and at the anchor alike, on the same assertion:scripts/tests/build-registry-test.shreports 7 passed, 2 failed (job 113745995059 here, 113612738347 at the anchor). This is the same registry drift, tracked in #1161; #1174 attributes this self-test failure to it. Not required, and not changed by this PR.This lands only while
mainis still6d19ce0e. Ifmainhas moved, do not merge and do not press Update branch; ask for a re-anchor.mainrequires linear history and allows squash only. The three required contexts are not strict, so automerge is deliberately not armed: it would fire aftermainmoved. There is no pull-request rule and no signatures rule (read 2026-10-09). Branch-Floor (deletion+non_fast_forward, ruleset 24339404) was re-enabled at the owner's request at 2026-10-09T08:45Z. It does not block a fast-forward.The file names two landings that keep it anchored. The owner chose the fast-forward (2026-10-09). The squash is kept below only as the fallback.
mainis the signed commit itself, and the push fails safe:bash owner-actions.sh land-standards. It re-readsmain's required contexts and checks each one on this PR's head: the latest check run, or failing that the legacy status. It refuses until all three have passed.git push origin <head>:refs/heads/main, without--force. Git refuses the push ifmainhas moved.git log --show-signature -1 origin/mainandgit rev-parse origin/main^, which should print the anchor.mainmoves first, which is what happened to docs(affirmation): refresh the standards affirmation at 85aa1934 #1203):git ls-remote origin refs/heads/mainimmediately before, and merge this PR alone.bash scripts/verify-affirmation-anchor.sh hyperpolymath/standards <N> 6d19ce0ebae047027dcfd594c7810bf35c642faa. It should printANCHORED.🤖 Generated with Claude Code
https://claude.ai/code/session_013omQK26s4uDjJMkdqNEvEG