What the team already decided, and a map of what else it knows
arroway_normsCall this in the seconds BEFORE you tell the person something or propose a course of action, to see whether it contradicts a decision the team already made. It returns the standing norms — the project's pinned rules and decisions, plus this person's own standing rules — AND THEN A MAP: the titles and handles of everything else the project remembers, so you can see whether anything there touches what you are doing. Read that map: if a title looks relevant, ask for it by handle with arroway_read include:["#handle"], which GUARANTEES those memories come back in full and first, where the ranking could otherwise have left them out — it does not make that read any cheaper than a read without it, so name a handle to be sure of getting something, never to pay less for it. It is meant to be called often: many times in one session, whenever you are about to commit to a claim. The map gives you names, never content, so this still does not answer 'how do I do this' — no recent context, no daily log, no ranked material. When you are starting work on a task, that is arroway_read, and this does not replace it. Because it is meant to be repeated, it ends by printing a session checkpoint: pass it back as since on your next call for this project and the standing norms are referenced instead of reprinted, so the repetition costs the map and what is in flight rather than the whole fixed block again.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | Optional: the session checkpoint printed at the end of a previous arroway_norms call for THIS project. Presenting it lets the standing norms be referenced instead of reprinted, which is what makes calling this tool many times in one session cheap. It is this tool's own checkpoint — the one arroway_read prints is not interchangeable with it, because the two surfaces render the same memories at different fidelity. Omit it — or present one this connection does not hold — and the norms 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. | |
| project | Yes | Project slug the claim is about. |