Read Arroway
arroway_readRead-onlyIdempotent
Read Arroway for a project BEFORE acting on any task related to it. It serves the authored essence of memories, dated-log entries and handoffs by default; name a #handle in include to recover that object's full body.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | Optional: the session checkpoint printed at the end of a previous read of THIS project. Presenting it lets the standing rules be referenced instead of reprinted, freeing that space for the task. Omit it — or present one this connection does not hold — and they are written out in full; the server decides, never your local state. If your context was compacted or this is a new conversation, omit it. | |
| handoff | No | Optional: the #handle of an OPEN handoff you are continuing. The read is then built from that handoff's reading list (the read_handles its author named): the standing rules in full, the handoff and every reference it names in full, and nothing ranked — much smaller than a normal read, and it counts as a delivered read. A handoff with no reading list falls back to the normal read, and says so. Cannot be combined with include; `since` is ignored. If a reference on the list is no longer available, the read is refused rather than served incomplete — read normally instead. | |
| include | No | #handles of memories, dated-log entries or handoffs whose full body you need. They are placed first and cannot be dropped by the budget — so other memories fall out instead: this chooses what you get, it does not get you more. | |
| project | Yes | Project slug, e.g. 'seven50' | |
| task_context | No | Optional: what you are about to do. It ranks what comes back, but the declaration alone is NOT evidence that a memory was used. A matching completion residue from the same session must corroborate it before Arroway updates the memory's observed-use signal. |