sage-fleetlisted

# sage-fleet — you are one session in an army SAGE is a **passive fleet judge**. The human watches the army from `sage war`. **You** (this session) speak four short truths so parallel work merges cleanly. Graceful degradation first: if `sage` is missing, errors, or prints nothing — **proceed**. SAGE is optional infra, never a hard dependency. Never block yourself because it is off. ## The one rule SAGE advises; it does not arbitrate. Two live sessions on the same code → **surface to the human**. Do not guess who wins. ## Live judge briefs (optional) If a **live judge** session is online, consult output may append layered sections (`── live judge · repo …` / `── live judge · fleet …`). Treat those as **advisory narrative**. Deterministic lines (clear / contested / RISK bars) remain **authoritative** for path overlap. If a brief contradicts CLI facts → **trust CLI** and surface the contradiction to the human. Never wait for a judge; no brief = proceed as always. Use `--no-brief` when you want facts only. ## Four touchpoints (do them) ### 1. Work-start — claim before you write ```bash sage backlog # is your row already held by a LIVE session? sage backlog claim D11 # register THIS session's row (when you have one) sage territory 'src/feature/**' 'docs/**' # overlap with another LIVE session → narrow scope OR surface to the human sage claim 'src/feature/**' 'docs/**' # register file intent so the next session sees you ``` Live-onl