Repository navigation
Protean-context 1.1.0: zero-context recovery slice - #2
Merged
Merged
Conversation
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.
Protean-context 1.1.0 names the zero-context recovery pattern. The README explains the cold-start load order of registry, one router, and one module. The ROUTER template instructs entering agents. The modules template states the population discipline. A new operator guide ships with a synthetic example. Router-discipline checks verify initialized targets. All 15 steps pass on the release head.
Tested commit: 6fe601c
Changed files (9):
Verification: new unit suite 6/6 pass; cold-start proof (empty init, verify, module plus pointer, verify, byte read-back) clean; gates identifiers, path-portability, emptiness pass. Note: check-leak-scan in a linked worktree flags only the worktree .git pointer file (absolute gitdir path); no repo file is implicated.