Skip to main content

Module progress

Module progress 

Source
Expand description

Durable, compaction-safe progress ledger.

Long-horizon agent capability requires a persistent signal of goal progress that survives compaction, fork, and resume. The live conversation is never reloaded into context from disk, but the progress ledger is a tiny derived artifact (like manifest.json) that the harness can read on each turn to decide whether work is actually advancing toward completion.

The ledger is stored under <session_dir>/derived/progress.json and overwritten on each update — it is a single mutable summary, not an append-only log, which keeps reads O(1) and cheap.

Structs§

GoalHistoryEntry
A single history entry for a goal lifecycle event.
GoalOrchestration
Full persisted state for a goal orchestration.
GoalTracker
Pure state machine for goal tracking.
Milestone
A single tracked milestone derived from the task tracker / plan.
ProgressLedger
Compact, durable progress signal for one session.

Enums§

GoalClassifierVerdict
Aggregate verdict produced by the goal-verification stage.
GoalEvent
Lifecycle event recorded in the goal history.
GoalPauseReason
Reason for pausing a goal. Maps 1:1 to one of the paused variants on GoalStatus.
GoalPhase
Phase of goal execution.
GoalStatus
Lifecycle status of a goal.
MilestoneStatus
Lifecycle status of a single milestone toward the session goal.

Functions§

load_progress
Load the progress ledger for a session, if one has been persisted.
progress_path
Resolve the on-disk path of the progress ledger for a session.
save_progress
Persist the progress ledger for a session, creating derived/ if needed.