feat: harden compliance core policy versioning - #88
Open
0xMuang wants to merge 2 commits into
Open
Conversation
Constraint: Preserve legacy numeric RecipeBinding compatibility and existing local Anvil plus GIWA testnet flows. Rejected: Runtime-mutable recipe aliases without compiled enforcement plans | it leaves production policy behavior mutable after activation. Confidence: high Scope-risk: broad Directive: Treat recipeKey as canonical and version-independent; never rebind activated Element IDs, recipe key/version slots, or compiled token policy plans. Tested: Element/Recipe/TokenPolicy registry targeted tests; ComplianceEngine targeted tests; RegD integration; full forge suite; toolkit and CLI smoke tests; isolated scripts/check; local Anvil E2E profiles for reg-d and buidl-like. Not-tested: External production RPC execution, Safe transaction submission, and live venue/maker/signer approvals.
Constraint: PR #88 is stacked on #87 and must include the clean-runner Toolkit installation order. Confidence: high Scope-risk: narrow Directive: Preserve stacked branch ancestry when correcting shared CI prerequisites. Tested: Merge completed without conflicts; downstream CI pending. Not-tested: GitHub CI rerun pending push.
0xMuang
added a commit
that referenced
this pull request
Aug 23, 2026
Constraint: PR #89 is stacked on #88 and must inherit the clean-runner Toolkit installation prerequisite. Confidence: high Scope-risk: narrow Directive: Preserve stacked branch ancestry when shared CI prerequisites change. Tested: Merge completed without conflicts; downstream CI pending. Not-tested: GitHub CI rerun pending push.
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.
Immutably version Element and Recipe registrations, add canonical recipe-key collision guards, compile bounded strengthen-only enforcement plans, preserve exact Element reason codes, and update onboarding Toolkit/CLI plus docs. Verified: 86 registry tests, 37 engine tests, 6 RegD tests, full 870-test Foundry suite, Toolkit/CLI smoke, isolated scripts/check.sh, and Anvil reg-d plus buidl-like E2E. Not tested: live production RPC, Safe submission, or live venue/maker/signer approvals. Stacked on #87; does not target main.