attentionlisted

# Attention — asking humans well ## Channel binary This document spells every CLI invocation as `first-tree …` — the canonical prod binary name. **Substitute your local channel** when running: | Channel | Binary | Home | |---|---|---| | Prod (npm) | `first-tree` | `~/.first-tree/` | | Staging | `first-tree-staging` | `~/.first-tree-staging/` | | Dev (in-tree) | `first-tree-dev` (alias `ftd`) | `~/.first-tree-dev/` | Operators on staging would type `first-tree-staging attention raise …` — flags and behaviour are identical across channels. Running agents inherit their channel from the daemon that started them; you can check via `echo $FIRST_TREE_HOME` (the runtime sets it). ## North Star **Ask when you need to ask. Decide for yourself when you can. Notify when the human must know.** NHA (Need-Human-Attention) is the structured "I need a human" primitive. You raise one with `first-tree attention raise`. If you need an answer, the human responds and your turn resumes. If you only need them to know, you raise a notification and continue working. Each NHA is chat-bound (`origin.chat` is required), targets exactly one human, and carries a single structural axis: `requiresResponse` — `true` for a request (Ask), `false` for a notification (Notify). The system layer is intentionally thin. It stores, routes, and delivers; it does **not** decide whether you should raise, how long to wait, or what to do on timeout. Those are your job — that's why this skill exists. ## `AskUserQue