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>
Update Quentin's documentation and prompts to reflect that his Kernos
workbench runs on `ergon.helu.ca` as user `quentin`. Add a Location
column to the MCP server table and clarify that Ergon is his dedicated
demo host.
- Add Quentin as work-team lead agent for solution architecture & demos,
with aws_sa repositioned as Quentin's exclusive subagent (tool, not peer)
- Add CASE as engineering lead agent for field/physical layer (LAN, hardware)
- Bump unified Neo4j schema to v2.4.0:
- Add Solution and Demo node types under Quentin's domain
- Update assistant ownership table with Quentin, CASE, and AWS SA scoping
- Update README and neo4j shared docs to reflect new team rosters and
subagent boundaries
