---
{
  "n": 29,
  "title": "Filing and sharing a document or report",
  "abstract": "",
  "refs": [],
  "seen": [
    "system",
    "agent"
  ],
  "data": {
    "starts_on": "",
    "system": true,
    "environment": "main",
    "unless": {},
    "started_by": "",
    "only_when_idle": false,
    "talks_in": "",
    "lasting": false,
    "dispatch": ""
  },
  "created": 1791271090.780052,
  "updated": 1791272776.600379,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "sequence"
}
---
The closing steps of a document or report: file it where it belongs, link what it relates to, offer the user a next step where one fits, then answer with it.

## Add the document or report to a collection
If a collection the user keeps fits what you wrote, add it: journal collection add <collection n> <ref>. Look with journal collection all first. When none fits but other documents or reports on the same subject sit in no collection, make one named for the subject with journal collection create "<subject>", add this and them, and say so in one line. A row with nothing related gets no collection of its own. Then journal sequence next <this sequence> --about <ref>.

## Link the items behind the document or report
Link the rows it answers or was built on, such as the to-dos, plans, documents, reports or messages it is about, with journal <type> link <ref n> "<row>" for each. Leave out rows it only mentions in passing. Then journal sequence next <this sequence> --about <ref>.

## Offer the user a next step
If it asks the user to decide or approve something, give it buttons: journal <type> update <ref n> --set buttons='[{"label": "Accept this proposal", "say": "I accept this proposal", "choice": "answer"}, {"label": "Change it first", "say": "I want changes first", "choice": "answer"}]'. A button with say sends those words to you as the user's message; one naming a type, n and action runs that command. Buttons of one decision share a choice, so the others go once one is pressed. Skip this when nothing waits on the user. Then journal sequence next <this sequence> --about <ref>.

## Tell the user in the chat
Say in one or two plain lines what it concludes, then its reference on a line of its own, like doc 41 or report 98, never in backticks. Finish with journal sequence next <this sequence> --about <ref>.