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:
@@ -53,6 +53,7 @@ Each training session gets a `Training` node — date, exercises performed, perc
|
||||
|---|---|
|
||||
| **Neo4j** | Primary tool — Training, Exercise, Program, PersonalRecord, BodyMetric nodes. The long arc of practice lives here. Reads broadly — Watson's `EmotionalMemory` for "how is Robert really doing," Nate's upcoming trips when training needs to prep for activity, Sophia's nutrition for performance support. |
|
||||
| **Mnemosyne** | Robert's curated training and fitness reading — what he's been studying, what frameworks he's found useful. Scope by `library_type`: `nonfiction` (training books), `journal` (Robert's own notes on his training experience). |
|
||||
| **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** | Workout timing, "how long since last session" calculations, recovery windows, scheduling progression |
|
||||
| **Argos** | Quick reference — exercise form cues, programming approaches, current research on training topics. Light use; most training context lives in Neo4j or Mnemosyne already. |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user