cdno commitments
List aggregated commitments across the vault — the hard milestones of active projects, standalone commitment notes, stewardship periodic commitments, and self-imposed action-note deadlines — sorted by date, with overdue items flagged.
cdno commitments [OPTIONS]
Options
| Flag | Description |
|---|---|
--weeks <WEEKS> | Lookahead window, in weeks. Default 2. A standing 30-day overdue look-back always applies on top. |
Plus the global options. With --json, emits the list as structured
data.
Examples
cdno commitments # next 2 weeks + anything overdue
cdno commitments --weeks 6 # next 6 weeks
cdno commitments --json | jq '.[] | select(.overdue)'
How it’s computed
This is a derived view, not a single file. It merges four sources (see
Business rules):
project milestones marked --hard, stewardship periodic commitments, standalone
commit notes, and action notes with a self-imposed due:. A project’s own dates count while the project is open, active or parked: a hard date on a parked map is still a promise. Completing or dropping a project takes its milestones and action due dates out of the view until it is activated again. A standalone commitment that names a parked or closed project keeps surfacing, since it is a promise to someone else.
Related MCP tool
See also
- Commitments and deadlines.
commit— create a standalone commitment.