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§

Milestone
A single tracked milestone derived from the task tracker / plan.
ProgressLedger
Compact, durable progress signal for one session.

Enums§

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.