Command reference
oko obligations remind
One reminder pass, the one the standing routine obligation-reminders runs: it reads the operator's answers to earlier reminders, then asks him about each open obligation inside its nearest declared lead not asked yet, or late and not asked since its --overdue-every.
Invocation#
oko obligations remind [--dry-run] [--json|--plain]Inputs and options#
- --dry-run prints what would be asked and neither connects to the shared database nor writes the register.
Output and state effect#
- Each reminder is one `oko asks` ask from `oko` with subject `obligation:<id>`, the question `<title> (<authority>, <jurisdiction>) is due <date>, <in N days|today|N days late>. Is it done?`, the detail (needs, who, cost of lateness, source, task) and the choices `done` and `not done`; it reaches the channels the operator chose (Oko Desktop, Oko iOS, iMessage, mail) and the watched terminals. Dates only: no time is put before him.
- Only the nearest lead is asked: a farther lead passed while no pass ran is covered by it. The ask id is kept on the obligation; a refused ask is kept with its cause and put again next pass, the earlier refusal of the same lead replaced.
- An answer `done` closes the obligation with `the operator answered done to ask <id>` as its evidence and opens the next instance of a recurring one; `not done` is kept and the next lead or overdue interval asks again.
- Prints `today`, `settled`, `asked` and `refused`, or `today` and `wouldAsk` for a dry run. Oko never files or pays: an obligation's owner does.
Refusals and safe exits#
- The time zone refusal of list; the shared database's sign-in refusals when there is something to ask or read; every refusal of `oko asks ask` is kept on its obligation rather than stopping the pass.