G2: propose bounded reset-2 recovery amendment - #47
Merged
kmccleary3301 merged 1 commit intoAug 12, 2026
Merged
Conversation
kmccleary3301
merged commit Aug 12, 2026
e306080
into
north-star/recovery-execution
89 of 90 checks passed
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.
Decision requested
Approve or reject the inert
G2/reset-2planning amendment. This PR does not activate reset-2, select or merge a seed, mutate runtime state, or close/supersede any packet.Exact scope
d03324f9d44f1318b1a4ffb37ab62c6ebe250eaed2e5c486295d98956e8d3111239e917ba88b25d86a31143dfd0255bebb1a26130d96d95eb53e4ca3EXECUTION_PLAN.md,LOOP_SPEC.yamlPurpose
Reset-1 is exhausted and immutable negative evidence. This amendment defines the only bounded lawful reset-2 path while preserving the logical G2 packet, tracker issue, dependency graph, product scope, and completion criteria. Activation still requires fresh exact planning reviews and distinct authenticated human action/consumption records for scope/budget, governance schema, and security boundary. Seed/candidate merge and closure remain separately gated.
Verification
scripts/check_phase20_freeze.py: PASSgit diff --check: PASSG2Reset2DigestFinalSpec)G2Reset2DigestFinalSecurity)Human gate
Merging changes packet-control governance and security-boundary planning. Do not merge without Kyle's explicit exact-scope approval. Approval of this planning PR alone does not authorize reset-2 activation actions, seed/candidate merges, packet closure, claim publication, or release.