task_note
Destructive
Create structured briefs or free-text notes for tasks and items to capture goals, context, steps, pitfalls, dependencies, and completion criteria.
Instructions
A note a task owns: an item's brief, a rule its items share.
Not a memory: only task_read() returns it. A note on items is a brief:
goal, context, steps, pitfalls, done_when and depends_on are required,
extra_info is optional, and they read back under the labels GOAL: /
CONTEXT: / STEPS: / PITFALLS: / DONE WHEN: / DEPENDS ON: / EXTRA INFO:.
A note on the whole task is free text in body.
Free text cites another item only as [[#id]], which reads back as its current number and label; a label -- a title, an item's text -- never carries one. To a person, name it item n of its task.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | the task. | |
| body | No | a note on the whole task, up to 4000 characters; it errors beside a brief field. | |
| goal | No | what the item must achieve. | |
| items | No | the ids of the items the note is on, such as "4812,4815"; empty or "-" is the whole task. | |
| steps | No | how to do it, in order. | |
| title | No | up to 120 characters. | |
| delete | No | with note_id, removes that note. | |
| context | No | what the work needs to know: where it lives, what binds it. | |
| note_id | No | 0 creates a note; another id edits that note, where an empty field keeps its text and a field given replaces only its own. | |
| pitfalls | No | what goes wrong, and how to avoid it. | |
| done_when | No | how to tell the item is finished. | |
| depends_on | No | none, or the ids of the items this one waits for, each with an optional reason in parentheses ("4812 (why), 4815"). A deleted item reads back as deleted "its text". | |
| extra_info | No | anything else worth knowing; optional. |