docs: compound learning — attestation gates must re-verify anchors - #15
Merged
Merged
Conversation
First docs/solutions entry (best-practices) + CONCEPTS.md seed for the certification domain. Captures the two principles validated by review run 20260930-030735-c0aa86ef: verify the anchor record on every run (never write-once-trust), guard the first run's pinned state. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: sess_c59696de-2f36-4d7c-99cd-ad4102b8cc4e
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.
What changes
First compounded learning in
docs/solutions/plus aCONCEPTS.mdseed for the certification domain — institutional knowledge from the v0.4.0 review, searchable by future agents working in this repo.Why
lfg step 7 (ce-compound): the v0.4.0 adversarial review validated two principles that the code and tests demonstrate but do not teach — attestation gates must re-verify their anchor record on every run (write-once-trust launders tampered anchors), and the first run's pinned state must be guarded (strict flag replay converts a skipped review dimension into a permanently locked-out one). Losing this would repeat the silent-green class at the next gate built here.
Checklist
-O(documentation-only change; no code touched)CHANGELOG.mdhas a line underUnreleased(docs/knowledge store, not a behavior change — no entry needed)SKILL.md/references/updated if behaviour the agent sees changed (unchanged)