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>
Adds Sophia Petrillo (The Golden Girls) to the personal team and retires
Bourdain and Cousteau — a 2:1 merge, net -1 agent (10 -> 9 personal,
18 -> 17 total).
Why: the personal team casts fictional characters. Bourdain and Cousteau
are real people, one with significant baggage and one who died by suicide,
and neither had a dedicated MCP server or capability. Sophia is fictional,
plausibly owns both domains (an Italian grandmother knows food; tending
plants and the tank is housekeeping), and is the first personal agent to
actuate the house via the new Hecate MCP server.
Graph: Sophia inherits all 11 node types unchanged (Recipe, Restaurant,
Ingredient, Meal, Technique + Species, Plant, Tank, Garden, Ecosystem,
Observation). Uniqueness constraints are keyed on node label, not agent,
so there is no schema or data migration. Historical Note tags
(from:bourdain, to:cousteau) are deliberately left intact as an accurate
record. Schema bumped to 2.5.0.
Also:
- New docs/tools/hecate.md + prompts/tools/hecate.md, documenting the
physical-actuation discipline (never guess a room or device slug) and
stating plainly what Hecate cannot do yet: no sensor readings (Demeter
is REST-only), no weather, and set_timer is routine-bound with no
cancel — the conversational timer is coming to Daedalus.
- Shawn gains Periplus in the docs. The server was already wired in
iolaus but never described in any prompt, so the model was handed a
tool it was never told about — including the never-estimate-coordinates
rule.
- Corrected stale counts (15/16/18 assistants -> 17) and the stale
"Bowie's Domain" schema heading missed when David replaced Bowie.
- Removed utils/neo4j-schema-init.py.bak, a pre-Watson artifact.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Lets personal and work agents reason about local time, business hours,
and travel without a tool round-trip to the time MCP server.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- 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
- Expand system prompt from 49 to 380 lines for comprehensive guidance
- Add User context, Identity, and Communication Style sections
- Define Client advisory and Internal consulting roles explicitly
- Include signature questions and tone guidelines for consistent interaction
- Note modular composition: regenerate from canonical source files
- Introduced `neo4j-schema-init.py` for creating the foundational schema for the personal knowledge graph used by multiple AI assistants.
- Implemented functionality for creating constraints, indexes, and sample nodes, along with comprehensive testing of the schema.
- Added `neo4j-validate.py` to perform validation checks on the Neo4j knowledge graph, including constraints, indexes, sample nodes, relationships, and junk data detection.
- Enhanced logging for better traceability and debugging during schema initialization and validation processes.
