---
{
  "n": 8,
  "title": "Writing an update",
  "abstract": "",
  "refs": [],
  "seen": [
    "system",
    "agent"
  ],
  "data": {
    "starts_on": "trigger:3",
    "system": true,
    "environment": "test333",
    "files": {},
    "started_by": "",
    "runs": {},
    "abandoned": [
      {
        "about": "main|trigger:3",
        "step": 1,
        "why": "No update was asked for: the word came up in the discussion of the sequence bug",
        "at": 1790347531.74172
      },
      {
        "about": "main|message:16579",
        "step": 1,
        "why": "the message reports that another project's journal receives no updates; it does not ask for an update report",
        "at": 1791270276.120509
      }
    ],
    "unless": {},
    "only_when_idle": false,
    "talks_in": "",
    "lasting": false,
    "dispatch": ""
  },
  "created": 1790261563.8401952,
  "updated": 1791271090.817219,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "sequence"
}
---
The user asked for an update or a TLDR. Write an update report on what happened since they last opened one, and answer with it. You talk about the work, never about rows, commands or the journal.

## Find what changed since the last update
journal report changes lists what happened since the user last opened an update, under need, done, doing, plans, commits and also. Read any row you do not remember before you sum it up. Then journal sequence next <this sequence> --about <ref>.

## Write the update report
journal report recap "<one or two plain sentences: what got done, what is under way, what waits on the user>" writes the report with those rows in that order. Give every row under need and doing a short note of what it waits on or what is being done now: journal report note <report n> <row> "<line>". Add a row the list missed with journal report item <report n> <section> <row> "<title>", and take out one that is only noise with journal report drop <report n> <row>. Then journal sequence next <this sequence> --about <ref>.

## Tell the user in the chat
Reply in one short line that says the update is pinned at the bottom of the chat, like "Here's the update; I pinned it at the bottom of the chat." Leave the report's reference out: the pinned card is how the user opens it. Finish with journal sequence next <this sequence> --about <ref>.