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

@@ -40,6 +40,7 @@ CASE works *upstream* of Scotty. Once a host is provisioned and reachable, ongoi
|---|---|
| **Kernos** | The Linux console — the primary interface, on `korax.helu.ca` in production. Every operation routes through here. |
| **Argos** | Web lookups only when the answer isn't on the box — vendor docs, CLI flags, README excerpts, advisories |
| **Daedalus** | Workspace files. Read what Robert has uploaded into the current workspace (e.g. Ouranos); publish finished documents into the `published` collection and revise them later. The workspace is injected per conversation, not fixed per agent. |
| **Time** | Accurate timestamps for logs and reports — never assume the current date |
CASE deliberately does NOT use most other tools. Mnemosyne, Grafana, Github, Neo4j — these aren't part of the field-systems role. The narrow toolset is part of the design; CASE is the box and the network, nothing else.

View File

@@ -55,6 +55,7 @@ Harper owns the **build** half of the engineering team. Ideation, prototyping, w
| **Andromeda** | Shell ops on dev/staging hosts; file inspection; running experiments |
| **Mnemosyne** | Reference material, pulled context, multimodal exploration |
| **Neo4j** | Lab notebook — Prototype and Experiment nodes — plus reading what the rest of the team knows |
| **Daedalus** | Workspace files. Read what Robert has uploaded into the current workspace (e.g. Ouranos); publish finished documents into the `published` collection and revise them later. The workspace is injected per conversation, not fixed per agent. |
Tool details and gotchas live in [docs/tools/](../tools/).

View File

@@ -68,6 +68,7 @@ When something is wrong, Scotty's process:
| **Grafana** | Logs, metrics, and dashboard queries during incident response and capacity work; querying historical state when "what changed?" is the question |
| **Mnemosyne** | Runbooks, past incident records, reference architectures |
| **Neo4j** | Infrastructure and Incident nodes; reading what's deployed and what depends on what |
| **Daedalus** | Workspace files. Read what Robert has uploaded into the current workspace (e.g. Ouranos); publish finished documents into the `published` collection and revise them later. The workspace is injected per conversation, not fixed per agent. |
Tool details and gotchas live in [docs/tools/](../tools/).

View File

@@ -103,6 +103,8 @@ The leads delegate certain repetitive or narrow tasks to engineering subagents
Each agent's tool usage is documented in their own doc (Harper: [harper.md](harper.md), Scotty: [scotty.md](scotty.md), CASE: [case.md](case.md)) — the agent doc is the source of truth for which tools that agent uses. The tool catalog (per-tool reference, gotchas) lives at [docs/tools/](../tools/).
**Daedalus** is shared by every agent on every team — the workspace document store, and the assistants' only persistent place to write prose. The engineering team is filed under the **Engineering** scope, which reaches the **Ouranos** workspace; the workspace an agent is operating in is injected per conversation rather than fixed per agent. See [docs/tools/daedalus.md](../tools/daedalus.md).
The canonical graph schema (all 17 assistants, all node types) is at [docs/tools/neo4j/unified-schema.md](../tools/neo4j/unified-schema.md).
## Cross-Team Touchpoints