Re-pin assurance profile to v0.5.0 - #18
Merged
Merged
Conversation
Move the OpenDevs Agentic Assurance Profile pin from v0.4.0 to v0.5.0 at all three adopter pin sites. v0.5.0 is a backward-compatible minor that changes no adopter obligation (PROFILE.md, validate.py, all schemas, templates, and the reusable adopter-validate.yml are byte-identical to v0.4.0), so this is a clean, mechanical re-pin. - .agentic-assurance/adoption.yaml upstream.version: v0.4.0 -> v0.5.0 - .agentic-assurance/adoption.yaml upstream.commit: 00e2fe46... -> 759e4a9c06cdba876d5099e5760251d42a74a88c (the commit the v0.5.0 tag peels to) - .github/workflows/assurance.yml caller @-ref (adopter-validate.yml): same 759e4a9c... commit Validated before commit from a v0.5.0 checkout with scripts/validate.py adopter --repo-visibility public: exit 0, 0 ERROR/WARN (version/commit mismatch cleared, reading-order OK). drift with the 'Assurance policy change: re-pin to v0.5.0' directive: exit 0 (pin move -> warning). Co-Authored-By: Claude Opus 4.8 <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
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.
Assurance policy change: re-pin to v0.5.0
Re-pins the OpenDevs Agentic Assurance Profile adoption for
linksfrom v0.4.0 to v0.5.0.What changed
A re-pin touches three pin sites, moved together:
.agentic-assurance/adoption.yaml—upstream.version:v0.4.0→v0.5.0.agentic-assurance/adoption.yaml—upstream.commit:00e2fe46…→759e4a9c06cdba876d5099e5760251d42a74a88c(the commit thev0.5.0tag peels to).github/workflows/assurance.yml— caller@-ref foradopter-validate.yml: same759e4a9c…commitAssurance-metadata only — no functional/site code changes.
Why this is a clean re-pin (impact analysis)
v0.5.0 is a backward-compatible minor that changes no adopter obligation. Verified three independent ways:
PROFILE.md,scripts/validate.py, all six JSON schemas, thetemplates/tree, and the reusableadopter-validate.yml(the exact file this repo calls) are byte-for-byte identical between v0.4.0 and v0.5.0 (matching git object hashes). A v0.4.0-conformant adoption cannot newly fail under v0.5.0.linksproduced only the expected version/commit mismatch — zero other errors, zero warnings — so the re-pin requires nothing beyond the pin bump.assurance.yml, nowith:inputs, default adoption path) stays compatible — only the@-ref bumps. Still exactly 3 pin sites.v0.5.0's only adopter-usable addition is the optional local
aap checkCLI; everything else (design/ADR/evidence records, review-only verifier scripts, tests) is profile-internal. v0.4.0 remains supported/conforming per the profile's SECURITY.md, so this upgrade is elective hygiene, not a compliance requirement.Validation (before opening this PR)
From a v0.5.0 checkout of
agentic-assurance-profile(pinned commit759e4a9c…), against its own schemas/validator:scripts/validate.py adopter --repo-visibility public→ exit 0, 0 ERROR/WARN. Notably:OK: pinned version matches the profile checkout VERSION file ('v0.5.0')OK: pinned commit and consumed validation resources match the profile checkout HEAD ('759e4a9c06cdba876d5099e5760251d42a74a88c')OK: AGENTIC_ASSURANCE.md present at project root with assurance reading orderThe prior version/commit mismatch is cleared and no new obligation surfaced.
Review
Adoption stage: DRAFT. Do not merge without owner review (§0 handoff). The leading
Assurance policy change:directive acknowledges the pin move so the drift gate records it as a warning rather than an error (PROFILE.md §16: a pin move must be an explicit, dedicated change).