--- name: journal description: "Records what happened as a journal entry, or corrects one. Use when the user asks to journal, record, note, or correct something, or mentions in passing something that has happened or is planned that they would want to recall later." --- Record what happened so a reader months later can follow it. ## When - Asked: record. - Unprompted: record what the user took part in that has happened. Offer first for what they only observed, what is planned, or what you found. - Never record the session's own work. ## Before writing - Ask only where a reader months later could not follow what happened: something the account depends on and leaves out or leaves unclear, never detail it could hold but does not need. Never guess a date, name, or figure. A complete account is written as given. - Find every subject and the broad subject it falls under: one `search` by `names`, `types: ["entity"]`. Record missing subjects and new names through `entity`. Ask about an uncertain match. - Read the newest entry on the same subject (`search` by its slug, `types: ["journal"]`, `newest_first`); follow its layout. ## Write ``` type: journal version: 1 slug: - event_date: description: body: links: source: details: "}> ``` - One event per entry. - Keep every link or reference to more of the account. - Never write a secret in full. - Slug taken: add words. ## Documents From `document`: one entry summarizing what was captured and what surrounds it, linking each document entry. Ask only what the documents leave unclear. Date it by the event, else the capture day. One entry per event. A web page, from `document`: an entry recording what it says when read, with its address. ## Corrections What the entry got wrong: revise it. ``` type: journal version: 1 entry: body: description, event_date, links: ``` What the entry never held: a new entry linking to it. Both: both.