Lifecycle design · 15 September 2026

Proposed flow · not a completion status

  1. Step 1Persist task
  2. Step 2Bind runtime session
  3. Step 3Execute permitted work
  4. Step 4Record terminal or unknown state
  5. Step 5Review or explicitly retry
On this page

Execution, recovery, and progress tracking

Scope

Coordinate approved project work through the existing AIOS runtime, record progress and preserve correct behavior when clients disconnect, tools fail or services restart. This is task coordination, not another agent engine.

Existing foundation

The reviewed host has durable task storage and session/event correlation. It launches the existing runtime independently of the dashboard. A saved conversation alone does not establish safe execution recovery.

Decisions

Implementation tasks

ID Deliverable Status
EXEC-01 / MCP-P04 Bind scoped tool access to independent task preparation Pending
EXEC-02 / MCP-P06 Persist tool activity and authorized result references Pending
EXEC-03 Reconcile crash/disconnect and uncertain outcomes Pending
EXEC-04 / MCP-P07 End-to-end acceptance and rollback checkpoint Pending

Acceptance evidence required

Close the dashboard during a tool call and confirm the independently owned task continues. Reconnect without resubmission. Kill an upstream fixture and confirm bounded failure/unknown state. Revoke access before a later call and confirm denial. Try to fetch another project's artifact and confirm rejection. No current test establishes this complete lifecycle.

Related areas