// works-with
Works with
SAGE is the fleet judge. Sibling tools cover other slices of the same desk. Name them in feature docs when a real integration exists; this page is the short map.
| Package | Relationship to SAGE | Links |
|---|---|---|
| status-herald | Curtain cards / status bars for agent panes. Compact/COMPACTING and session truth can line up with SAGE’s read-only fleet view. See also in-repo interop note. | herald.muslewski.com · npm · interop |
| token-oracle | Offline token/cap forecasts. SAGE can point tokenForecastPath at an oracle (or legacy) forecast feed for optional statusline / board context — see statusline recipe. |
oracle.muslewski.com · npm |
| memory-atlas | Dual superpower with SAGE. Atlas holds the past / architecture present of a repo (code-verified zone cards + frozen decisions/specs). SAGE holds the session present of the desk (who is live, territory, merge risk). File-only coupling: optional project adapter reads atlas.config.json + zone globs so board/territory show zone names and treat map/index.md as generated. This repo’s mind is agentic-sage-mind/; public product prose stays in docs/. Neither package imports the other at runtime. |
atlas.muslewski.com · npm · SETUP · desk fleet |
| llm-armory | Named executor loadouts (advisor → Grok children). Sessions armory spawns are still judged, not orchestrated, by SAGE when hooks are on. | armory.muslewski.com · npm |
| mossferry | Remote tmux/mosh “ferry” to the machine where your fleet actually runs. Optional wire: ferry calls sage about --tmux for picker preview one-liners and can spawn sage judge run via ⚖ new judge… when sage is on PATH (FERRY_SAGE=auto on the ferry side). Fact judge run auto-fills brief session_lines. |
mossferry.muslewski.com · npm |
Dual superpower — past vs present
| Tense | Tool | Answers |
|---|---|---|
| Architecture past + map present | memory-atlas | What is this code supposed to be? Which zones own which globs? What did we decide and when was it last verified? |
| Session present | SAGE (this package) | Who is working right now? Which paths collide? What should a merge-brief say before I open a PR? |
Wire SAGE first with the linear checklist in SETUP.md (required → recommended → optional). Add a vault with Atlas when you want architecture memory that survives sessions — atlas init / atlas wire in that repo, then optionally drop the with-agentic-sage adapter so territory speaks zone names.
Hands-on multi-repo path: Wire a multi-repo desk.
Rules for authors
- Contextual first — when documenting a feature that displays or depends on a sibling, say so in that page (one clear sentence + link).
- Update this table when you add or remove a real edge.
- Do not invent — if code does not wire it, do not claim it.
See also
- Statusline recipe
- Multi-harness recipe
- Desk fleet recipe
- Getting started
- SETUP.md — full human bootstrap
Past + present
| Layer | Package | Install | Soft health |
|---|---|---|---|
| Past | memory-atlas | per-repo npm i -D memory-atlas |
atlas gate / SessionStart |
| Present | agentic-sage | once npm i -g agentic-sage |
sage gate / preferred offline |
Desk wire (manjaro / power users): node scripts/fleet-desk-wire.mjs