Concepts/Concept

ADPS Engineering Concept Registry

Three Session-State Planes

Coordinate narrative, mechanical business values, and task scheduling without mixing write ownership.

Three session-state planes

Application context

A long-running setup task contains three kinds of change. The conversation records what the user wants and what the agent has concluded. Tool calls return exact business values. The scheduler tracks which step is ready, blocked, complete, or failed. Storing all three in one chat history makes ownership and recovery ambiguous.

Definition

Unified Session State separates one session into three coordinated planes:

  • SessionNarrative stores goals, observations, summaries, and reasoning inputs;
  • SessionState stores exact business parameters, source coordinates, versions, and tool receipts;
  • Workspace stores task nodes, dependencies, status, checkpoints, and artifacts.

Engineering mechanism

Each plane has a different writer. The model may update narrative through a typed interface. Tool adapters and business services write mechanical values. The scheduler owns task transitions. References connect the planes: a Workspace node points to the artifact and state values it consumed, while narrative links to source records instead of copying them.

Boundary

“Unified” means coordinated under one session identity, not stored in one object or database table. Short, read-only conversations may need only narrative state. Multi-step execution and resume require explicit mechanical and scheduling planes.

Proposal and provenance

Initial source within ADPS
Initial practice: Bo Liang
First recorded in
Dongfang Yiteng execution-agent case ()
ADPS editorial work
ADPS organized narrative, mechanical parameters, and task scheduling into three state planes with distinct write ownership.
Current standing
Case-derived name

Initial source: Dongfang Yiteng Execution Agent case report; contributed by Bo Liang.

Concept registry · CC BY 4.0

Chronicle

Recorded source
Dongfang Yiteng execution-agent case ()
Source date
First published on ADPS

View in the ADPS Chronicle