magilisted

# magi — the entry ## When to use Any turn in a MAGI project where you do not already know what you are doing. ## Method 1. `magi next` — it reads the notes and ranks what is owed. It never acts. 2. Do the first item, unless the human just asked for something else: their sentence outranks the list. Everything under **"For the person"** goes to them in **one message**, and **asking for a prediction means showing the claim** — `next` prints it under the item, `--json` has it in `bets_waiting`. A slug is not a question anybody can answer. 3. When an item names a skill, call it. When it names a command, run it. 4. A result that came before its note is a finding: open it with `--found`, or mark an existing one `magi thread found <slug>`. Neither is asked to bet. A reviewer's `restate` is yours: fix the words as its post says, then `magi thread status <slug> supported --text '<what changed>'`. 5. Anything the human says in passing worth keeping goes into `inbox/notes.md`, one line, untidied; a later `magi next` files it. 6. Before stopping: `magi sync --close`. It refuses while something happened that nobody wrote down — clear each with `magi thread post <slug> --text '<what happened>' --host human` or `magi decide --about <slug> --text '<their words>'`, then close again. ## Rules - **Never** invent a next step while `magi next` has one. That list is derived from the notes; a step you made up is derived from nothing. - **Never** edit a status in `thr