Add responsibility-lane continuity gate for agent recovery - #258
Draft
safal207 wants to merge 9 commits into
Draft
Add responsibility-lane continuity gate for agent recovery#258safal207 wants to merge 9 commits into
safal207 wants to merge 9 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
What changed
Adds RLC-001 — Responsibility Lane Continuity, an additive extension to RFC-001 / Verifiable Continuation Envelope.
The extension models recovery of task responsibility topology, not only recovered state:
Why
A reproducible Codex Desktop compaction case showed that rereading a durable checkpoint and filesystem can still be insufficient: the resumed agent can conflate separate responsibility lanes and continue under the wrong mutation/ownership topology.
RLC-001 makes that failure machine-checkable:
state recovery -> responsibility-lane recovery -> source revalidation -> scoped continuationVerification
VCE conformancerun examples: add sanitized dynamic support-safety trace fixture #113: SUCCESS, including the new responsibility-lane suite.Conformance run:
https://github.com/safal207/pythiaLabs/actions/runs/31861074959
The negative fixture deliberately binds an authoring mutation (
artifact-rfc,artifact-schema) to the verification lane, whose scope allows onlycapability:verify. The validator returnsBLOCKEDeven when the lane restore document otherwise passes.Compatibility
This is additive. RFC-001 v0.1 and its existing schemas are not modified; RLC-001 composes as an additional gate.