Execution Plans

A Plan is optional Event-backed coordination data inside one Thread. It helps the Agent preserve an objective, acceptance criteria, steps, evidence, blockers, and the next safe action while ordinary model and Tool work continues.

Jixu does not create a ceremonial Plan for every turn. Direct execution remains valid for short or obvious work.

One adaptive hypothesis

A Thread has at most one active Plan and one in_progress step. The Plan is the Agent's best current execution hypothesis, not a fixed schedule:

• completed steps keep their identity, description, relative order, status, and existing evidence;
• later evidence may append to a completed step but cannot rewrite what was observed;
• the current in_progress step cannot disappear, be renamed, or return to pending;
• pending steps may be added, removed, edited, split, merged, or reordered as evidence changes the remaining route;
• a materially changed objective supersedes the active Plan instead of silently rewriting its history; and
• abandoning the objective records a terminal Plan revision without inventing a replacement.

Omitted fields in a revise proposal preserve their accepted values. A supersede proposal supplies the complete replacement Plan, while abandon needs only the operation itself.

Commit coordination before action

A valid Plan change becomes a durable plan.updated Event before the new projection is exposed and before ordinary Effects proposed by the same model outcome dispatch.

An invalid proposal becomes plan.rejected. The last accepted Plan, public model text, and valid ordinary Tool calls remain intact. Rejection does not give the Plan control authority over execution.

Control cannot replace work

Reserved Plan and progress controls coordinate or explain work; they do not perform it. If a model returns only a valid Plan update, Jixu commits that update and creates one execution-only continuation so the Agent can respond or call an ordinary Tool.

If Plan repair is exhausted, or a response contains only progress control, Jixu may create the same single bounded execution-only continuation. That request keeps ordinary Tools but hides reserved Plan and progress controls. A second empty or control-only outcome terminates with a typed error instead of looping.

This boundary prevents planning bookkeeping or progress narration from permanently blocking the user's requested work.

What a Plan cannot do

A Plan never:

• dispatches or schedules an Effect;
• grants Tool permission or resolves an approval;
• widens the user's scope;
• reserves compute;
• creates another Thread, Agent, Store, or state machine; or
• replaces durable Events as authority.

The active Plan survives recovery and may enter compiled model context and a Continuity Handoff. Completed, superseded, and abandoned Plans remain inspectable in Events but are excluded from default model context.

Continue with Context continuity to see how Plan state and causal receipts enter one bounded model request.