Log what a task left behind
arroway_logAppend the durable residue of a COMPLETED task to your daily log in Arroway: what someone arriving later would need in order not to redo it. You judge the length — say what carries, cut what does not. Dated state (numbers, statuses) belongs here; it ages out naturally. Team-visible. ALWAYS write the authored essence too: it is the one line the normal project read serves. An older, frozen catalog that truly has no essence field may still write the body; Arroway marks that entry as pending a reviewable essence proposal, never as if one had been authored. One thing that belongs here and nowhere else: if the person corrected you for insisting on something already decided, say so in the entry, so the memory that keeps being re-litigated can be flagged. AND CLOSE WHAT THIS WORK REALIZED: every memory in the read carries 'dies when: …'. If this task made that condition true — the idea was built, the intention was carried out, the dated status was replaced — name it in fulfills and Arroway retires it in the same act, with this entry as the reason; the human never has to archive the obvious by hand. Only decisions, facts and references can be fulfilled, and only ones this connection actually received in a read.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | Optional free tag (e.g. 'marketing') | |
| source | No | Optional pointer to a living source (URL, doc, CRM id) | |
| content | Yes | The full durable residue: what was decided, found or changed, and what it cost. It remains recoverable by handle. | |
| essence | No | One authored line with the operative result. This is what the normal project read serves; never copy the opening of the body. | |
| project | Yes | Project slug. If it did not come from the person or from a read in this session, it is a guess: check it against the roster that opens arroway_catch_up before writing, because material from one circle must never land in another. | |
| fulfills | No | ARROW-290. The memories this completed work REALIZED — their 'dies when' condition is now true because of what you did (a routine that an idea asked for is running; a planned move was made; a dated status has been replaced by what this entry records). Each one is retired in the same act as this log, with your 'how' as the reason on its archived line, reversible from the panel. Guards: only decision/fact/reference (a rule is never 'fulfilled'), and only memories this connection received in full in a read — if any item fails, the whole call is refused and nothing is written. Never list a memory because it merely looks old or unused: that is not evidence. | |
| backfilled | No | True when the entry describes something that happened BEFORE Arroway existed (history you are bringing in), not today's work. | |
| keep_whole | No | Set true only after you considered cutting an indivisible oversized residue. Arroway records this exception for calibration; it never truncates your text automatically. | |
| operational | No | Set true when this is the record of HOW THE WORK WENT — what failed, what you measured, what you corrected about your own earlier reading. It is kept in full for catching up at the start of a session, and stays OUT of the task-scoped read, so a long account never pushes a teammate's residue out of their block. Leave it out (the default) for what the team needs to know HAPPENED: that is what reaches other people while they work. This is a record of work, never a transcript of the conversation. |