feat(tools): give every assistant the Daedalus workspace file tools

All 17 assistants can now read and write their Daedalus workspace. The
MCP server, the per-team `dmcp_` tokens, and the deploy templates were
already wired; what was missing was that no agent had the server in its
list and no prompt ever described the tools. Even the four agents that
did have it (Shawn, Jarvis, Harper, Scotty) only knew Daedalus as the
thing that schedules their inbox check.

Adds the tool docs (docs/tools/daedalus.md human reference,
prompts/tools/daedalus.md LLM snippet), a per-team-styled tool block in
all 17 prompts, a Daedalus row in all 17 bibles, and the server row in
the shared MCP inventory.

The discipline that matters: the workspace name is injected per
conversation and must be passed verbatim, agents may only write into
generated collections, and there is no delete tool — so a bad title is
permanent and revise beats republish.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-07-27 07:16:25 -04:00
parent fefc9018ab
commit e67d5c32fc
40 changed files with 387 additions and 0 deletions

View File

@@ -62,6 +62,7 @@ Matches Robert watched or attended get `Match` nodes — date, competition, team
| **Kairos** | Calendar entries for matches — when Robert is attending, when must-watch fixtures are scheduled, tournament windows. Reads to know what's coming; writes when Robert commits to attending. Coordinate with Shawn for the broader calendar. |
| **Mnemosyne** | Robert's curated football reading — books on tactics, club histories, biographies. Scope by `library_type`: `nonfiction` for football writing, `journal` for Robert's own match notes. |
| **Argos** | Quick reference — vendor announcements, transfer news, the article everyone's talking about, fact-checks before strong claims |
| **Daedalus** | Workspace files. Read what Robert has uploaded into the current workspace (e.g. Home); publish finished documents into the `published` collection and revise them later. The workspace is injected per conversation, not fixed per agent. |
| **Time** | Match timing, kick-off windows in different timezones, season calendar math |
For deep research on a topic — a tactical question across multiple matches, a comparison spanning eras, a deep-dive on a club's recent history — delegate to the **research** subagent.