Carry work across agents · Agent continuity

Start every agent from accepted state.

Without it, each session rebuilds context from scratch and can treat a cancelled or pending decision as settled.

OrgX hands the next session the accepted state and flags what still needs judgment.

Functional handoff demo

Carry accepted state. Hold open judgment.

Switch the receiving client and inspect what it may reuse, what it must not assume, and the next valid action.

Claude CodeSession closed

Agency leads the buyer pathAccepted

Four responsive widths requiredAccepted

Annual price needs owner judgmentNeeds judgment

CodexContext loaded

Agency leads the buyer pathCarried

Four responsive widths requiredCarried

Annual price needs owner judgmentDo not assume

Next valid actionComplete the 375px evidence passNo context reconstruction required
What changes in the work

The handoff preserves the boundary.

01

Accepted state travels

The next agent starts from decisions that already cleared judgment.

No re-briefing and no second interpretation of settled direction.
02

Open judgment stays held

A pending decision cannot become an accidental instruction.

The handoff marks the boundary as do not assume.
03

The next action is bounded

The receiving client knows what can continue safely.

Continuation follows the current record rather than a generated summary.
What OrgX records

The next session receives objects, not a summary.

Accepted state
Terminal decisions and approved direction.
Held state
Pending judgment the next agent must not assume.
Next action
The valid continuation from the current record.
NextContinue the product storyEnter through the tools you already use.
One real initiative

Start with the outcome. Keep the record.

Start with accepted state Inspect the live handoff
Agent continuity | OrgX