ULTRAPLAN State Machine (running/needs_input/plan_ready/approved/rejected)
- Entity ID:
ent-20260419-a015d6e7f8a9 - Type:
concept - Scope:
shared - Status:
active - Aliases: ultraplan state model, ultraplan lifecycle states
Description
The full five-state ULTRAPLAN lifecycle: running (remote cloud browser session researching/planning) → needs_input (blocking question) → plan_ready (planning complete, ready for local review) → approved (user approved, local agent executes) OR rejected (plan discarded, revised brief solicited). User reviews and approves/rejects the plan in a browser UI before any local execution — explicit human-in-the-loop for the 30-minute deep planning session.
Key claims
- ULTRAPLAN is fire-and-fetch, not fire-and-forget
Relations
- ULTRAPLAN State Machine (running/needs_input/plan_ready/approved/rejected) --[implements]--> ULTRAPLAN