`cdno commit`

Manage standalone commitments — dated promises kept as their own notes. To view all commitments (from every source), use cdno commitments.

cdno commit [OPTIONS] <COMMAND>

Subcommands

Subcommand	Description
`create`	Create an active commitment at `commitments/<slug>.md`
`done`	Mark a commitment completed and archive it
`drop`	End a commitment that was not kept
`reschedule`	Move an active commitment’s due date

All four honour --json ({path, message}, non-interactive).

`cdno commit create`

Create an active commitment note. Optionally attribute it to a project or stewardship.

Flag	Description
`--title <TITLE>`	Commitment title (the slug derives from it).
`--due <YYYY-MM-DD>`	Deadline.
`--context <CONTEXT>`	Life domain (`work`, `personal`, …).
`--project <SLUG>`	Optional associated project.
`--stewardship <SLUG>`	Optional associated stewardship.
`--var <NAME=VALUE>`	Value for a custom template’s prompted variable (`[variables.prompt]`). Repeatable. See Prompted variables.

cdno commit create --title "Pay rent" --due 2026-06-01 --context personal
cdno commit create --title "Review Erik's draft" --due 2026-05-20 --context work --project projects/icml-paper

`cdno commit done`

Mark a commitment completed: stamps status and completed, and moves the note to commitments/_done/<year>/<slug>.md.

Flag	Description
`--slug <SLUG>`	Commitment slug.

cdno commit done --slug pay-rent

`cdno commit drop`

End an active commitment that was not kept — cancelled, superseded, or overtaken by events.

Flag	Description
`--slug <SLUG>`	Slug of the active commitment.
`--reason <TEXT>`	Why it ended. Optional, and never prompted for.

cdno commit drop --slug quarterly-report
cdno commit drop --slug quarterly-report --reason "the client cancelled the engagement"

Use this rather than done when the promise was not fulfilled. done writes commitment completed [[slug]] into the daily log, which every weekly and monthly review reads back from, so using it for a cancelled promise makes the vault assert something nobody did. Deleting the note is not the alternative either: that destroys the record that the promise was ever made, and desyncs the index on the way out.

The note is archived to commitments/_done/<year>/ like a completion, stamped status: dropped with completed cleared — so it never appears as completed work. The log entry says what happened, with the reason on its own line:

- **16:30**: commitment dropped on [[quarterly-report]] — Quarterly report
  reason: the client cancelled the engagement

A dropped commitment can afterwards be neither completed nor rescheduled. Nothing is destroyed — the note keeps its body and its created date — but a drop is re-decided rather than undone: if the promise comes back, make it again, and the record shows both decisions.

`cdno commit reschedule`

Move an active commitment’s due date, recording the move in today’s daily note.

Flag	Description
`--slug <SLUG>`	Slug of the active commitment.
`--due <YYYY-MM-DD>`	The new due date. Must differ from the current one.

cdno commit reschedule --slug quarterly-report --due 2026-06-15

Commitments slip, and that is normal rather than an error state. Use this instead of deleting and recreating the note: recreating destroys the body — the notes on who was chased and what was promised — and resets created, the one field that shows how long something has been slipping.

The log entry carries both dates:

- **09:30**: commitment rescheduled on [[quarterly-report]] — Quarterly report
  was: 2026-06-01
  now: 2026-06-15

That is what makes repeated slippage visible instead of silently rewritten: a commitment moving once is a checkpoint, a commitment moving for the fourth time is a signal. Moving a date earlier is allowed; moving it to the date it already carries is refused, since the entry would assert a slip that never happened.

create_commitment, complete_commitment, drop_commitment, reschedule_commitment. (View via get_commitments.)

Cuaderno