Continuity Memory Todo and Plan

Temporal Memory, Todo, and Plan

Language: English · 简体中文

v0.18.5 scope changes

Plan supports targeted objective and step revisions with stable identities, CAS and history. Waived and replaced work is distinct from completed verification. Reconcile returns read-only candidate evidence and never silently advances work. Inspect lwc contract plan-revise before writing. Discussion preserves the visible clarification that precedes a plan.

LWC separates three kinds of continuity so that historical events, deferred work, and the current execution plan do not become one ambiguous task list.

Capability	Owns	Does not own
Temporal memory	Sparse events: decisions, changes, outcomes, unresolved observations	Stable Wiki knowledge or task state
Todo	Independent future or deferred work	The steps of the active execution plan
Plan	One current coarse plan with progress, blockers, revisions, evidence, and completion criteria	Unrelated backlog items

Temporal memory

Temporal memory is built in. Recording is intentionally fast and sparse; LWC applies age and capacity retention without asking the Agent to maintain a log manually.

lwc remember --json @event.json
lwc memory recall "query" --limit 5
lwc memory show <EVENT_ID>
lwc memory status
lwc memory maintain

Use it for events where when and what changed matter. Put stable, reusable conclusions in the normal Wiki instead. Protected unresolved, contradictory, or pinned events survive ordinary retention until their protection is resolved.

Todo

Todo is opt-in and independently configured. It stores durable future work indexed by title and tags, with optional target time and one direct parent.

lwc --scope project config set --todo enabled
lwc todo add --json @todo.json
lwc todo list --limit 20
lwc todo search "keywords" --limit 20
lwc todo show <TODO_ID>
lwc todo update <TODO_ID> --if-revision <REVISION> --json @update.json
lwc todo done <TODO_ID> --if-revision <REVISION> --result "result"

Use cancel when work is no longer wanted and reopen when a terminal item becomes relevant again. Revision checks prevent stale Agents from overwriting newer state.

Plan

Plan is also opt-in and independent from Todo. It tracks the current execution path through coarse steps rather than mirroring every action or tool call.

lwc --scope project config set --plan enabled
lwc plan create --json @plan.json
lwc plan current --limit 20
lwc plan brief <PLAN_ID>
lwc plan advance <PLAN_ID> --if-revision <REVISION> --done <STEP_ID> --result "result" --next <STEP_ID>
lwc plan block <PLAN_ID> --if-revision <REVISION> --step <STEP_ID> --reason "blocker"
lwc plan complete <PLAN_ID> --if-revision <REVISION> --result "result" --evidence "evidence" --done-when-checked

revise replaces only unfinished work and records the reason. Completion requires every step to be terminal plus explicit result, evidence, and confirmation that the done criteria were checked.

Agent and Hook behavior

Lifecycle Hooks expose bounded readiness, due Todo reminders, and the most recently updated active Plan. They never create, advance, complete, or recall raw records automatically. The Agent decides when a durable operation is useful and keeps command details out of the user's foreground conversation.

Next: Learning Suite · Common workflows