You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a high-level work-continuity loop so the same work can be delegated, transferred, acknowledged, and completed across human-to-human, human-to-Agent, and Agent-to-Agent boundaries.
The shared narrative is:
Work Contract -> Work -> Handoff -> Continue + Acknowledge -> Task Outcome
PowerContext already supports Prepared Handoffs, immutable committed Handoff revisions, evidence validation, Continue, and Handoff Report. Integrations still have to assemble the low-level lifecycle themselves, and the current product model does not explicitly capture:
the objective, scope, completion criteria, and authorization boundary for newly delegated work;
whether the receiver accepted, needs clarification on, or declined an exact Handoff;
what actually happened after continuation, including partial, blocked, failed, cancelled, or unknown outcomes;
the evidence boundary between a task observation and a reviewed reusable Experience.
Implement one minimal Source-backed loop:
create_work_contract records a grounded delegation baseline;
handoff_current_work captures inspected current state and returns an uncommitted Prepared Handoff;
acknowledge_handoff resolves the same exact selection again and rejects accepted when evidence is unavailable;
record_task_outcome preserves the exact outcome and check states for later Handoff evidence and reviewed Experience incubation.
Expose these operations consistently through the Runtime, HTTP API, Python Client, and MCP. Keep existing explicit Handoff commit, immutable revision, compare-and-swap, and Review boundaries unchanged.
Acceptance criteria
Human-to-human transfer can use a human-readable committed Handoff and record an acknowledgement against its exact revision.
Human-to-Agent delegation records a Work Contract without treating historical notes as execution authority.
Agent-to-Agent transfer can pass canonical Prepared Handoff JSON without the original session transcript.
Unavailable Handoff evidence prevents an accepted acknowledgement but permits a reasoned clarification or decline.
Task Outcome preserves succeeded, partial, blocked, failed, cancelled, and unknown states without upgrading uncertainty.
Task Outcome remains compatible with the existing task-outcome Experience-incubation boundary and still requires Review.
Existing Handoff, Memory, PreparedContext, Experience, and Report behavior remains compatible.
OpenAPI, generated bindings, SDK, MCP, focused Runtime tests, and an SQLite end-to-end journey cover the loop.
Alternatives considered
Add a separate Task or Workflow database. This duplicates Handoff identity and persistence before the minimal loop is validated.
Generate a Handoff or Outcome at every SessionEnd or Stop event. Those events do not reliably mean the work is complete and would make the Codex integration intrusive.
Transfer complete session transcripts. This is unbounded, transport-specific, and does not provide exact evidence semantics.
Require integrations to keep composing capture, activate, inspect, and finalize manually. This preserves the current user-facing gap.
Feature description
Add a high-level work-continuity loop so the same work can be delegated, transferred, acknowledged, and completed across human-to-human, human-to-Agent, and Agent-to-Agent boundaries.
The shared narrative is:
The detailed design is captured in RFC 1223: Human-Agent Work Continuity.
Problem and proposed solution
PowerContext already supports Prepared Handoffs, immutable committed Handoff revisions, evidence validation, Continue, and Handoff Report. Integrations still have to assemble the low-level lifecycle themselves, and the current product model does not explicitly capture:
Implement one minimal Source-backed loop:
create_work_contractrecords a grounded delegation baseline;handoff_current_workcaptures inspected current state and returns an uncommitted Prepared Handoff;acknowledge_handoffresolves the same exact selection again and rejectsacceptedwhen evidence is unavailable;record_task_outcomepreserves the exact outcome and check states for later Handoff evidence and reviewed Experience incubation.Expose these operations consistently through the Runtime, HTTP API, Python Client, and MCP. Keep existing explicit Handoff commit, immutable revision, compare-and-swap, and Review boundaries unchanged.
Acceptance criteria
acceptedacknowledgement but permits a reasoned clarification or decline.task-outcomeExperience-incubation boundary and still requires Review.Alternatives considered
Additional context
scope_id, MCP visibility, receiver labels, and authorization notes are not ACLs.Are you willing to contribute?