Skip to content

Add responsibility-lane continuity gate for agent recovery - #258

Draft
safal207 wants to merge 9 commits into
mainfrom
agent/responsibility-lane-continuity
Draft

Add responsibility-lane continuity gate for agent recovery#258
safal207 wants to merge 9 commits into
mainfrom
agent/responsibility-lane-continuity

Conversation

@safal207

@safal207 safal207 commented Aug 15, 2026

Copy link
Copy Markdown
Owner

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:

  • explicit responsibility lanes with owner, objective, mutation scope, done condition, latest ruling and durable source refs;
  • material VCE event → lane bindings;
  • lane-scoped next action;
  • source-revalidation restore results;
  • fail-closed handling for conflicting lane sources;
  • tamper-evident lane and extension digests;
  • accepted fixture and a rejected lane-conflation fixture.

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 continuation

Verification

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 only capability:verify. The validator returns BLOCKED even 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.

@coderabbitai

coderabbitai Bot commented Aug 15, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 30cf0f54-728a-4995-9c56-99b51edbb420

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant