wt-update

name	wt-update
description	Updates an existing commitment when the user reports progress: completion, a new deadline, a stall, or abandonment. Use when the user says "I did that", "finished X", "still waiting on Y", "push that to next week", "I started it", or "forget it, I'm not doing X". Finds the matching open action, applies the change, and routes any knowledge the report carries to the knowledge base. Do NOT use to file a new commitment (that is wt-capture) or to find time for one (wt-schedule).
metadata	{"aos":{"origin":"work-tracker@0.1.2"}}

update

Three steps. The third is the one an implementation forgets, and the one that keeps the whole design honest.

1. Find what was meant

kb --base commitments find --where type=action --where status=next

The open set is small, so match by title against what the user said. Add --where status=waiting when the report sounds like waiting ("still nothing from Robin").

Genuinely ambiguous between two actions → ask which. Guessing here writes the wrong page and the user finds out later, if ever, which is worse than one short question.

Nothing matches → this is probably a new commitment. Hand to wt-capture rather than inventing a page here.

2. Apply it

kb set for every change — it validates against the base's schema and makes its own attributed commit:

The user says	Apply
"I did that", "finished X"	status=done and expires=<today + retention>