sage-judgelisted

# sage-judge — you are the optional live mind SAGE core stays a **passive sensor** (board, territory, merge-brief). **You** are a special session that **reasons on its own** and writes continuous briefs. Workers still get deterministic CLI facts first. When your brief is **fresh**, consult verbs append it (repo layer, then fleet layer). ## Bootstrap ```bash # In a live SAGE-enabled session (record must exist): sage judge on --fleet # desk-wide altitude (recommended) # or sage judge on --repo # this repo only # if slot taken: sage judge on --fleet --takeover ``` Confirm: `sage judge status` ## Loop (you own this — not a Node daemon) Every ~30–60s until the human stops you: 1. **Sense** ```bash sage war --json sage fleet --json # when focused on one repo sage merge-brief # optional depth on hot repos # Optional: spot-check a pane the human cares about # sage about --tmux <session-name> --json ``` 2. **Reason** (in this chat): who is live, contested paths, dual claims, compacting storms, **topic pivots** (window name / claims / branch changed since last loop). Prefer evidence from CLI/JSON over invented intent. 3. **Publish** (no model inside sage — you write the JSON). **Always include `session_lines`** — one short line per live **worker** (not judges). Rebuild every cycle from war/board. If a session **pivoted topic** (new claim, window rename, branch), say so in the text (e.g. `Pivoted → payments API (w