Verified against the live Virgo dev instance while testing Sophia: with no
bearer token, Hecate answers 401, fast-agent reads that as an auth
challenge and falls back to OAuth dynamic client registration, then blocks
waiting for a browser callback on 127.0.0.1:3030 that never arrives on a
headless host. The agent never finishes starting — so a missing PAT is a
startup failure, not a per-tool one. Same trap as the Daedalus MCP server.
Also noted that /mcp answers 307 to /mcp/, so the trailing slash avoids a
redirect on every call.
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>
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
Restructure cousteau.md from a verbose AI system prompt into a concise
human reference document describing the agent's character, role, and
behaviors. Point readers to the actual system prompt location and
condense content from ~571 to ~175 lines while preserving key
philosophy, personality, and operational details.
Refactor documentation to distinguish character reference from AI
system prompt. Removed user context and persona definitions.
System prompt instructions moved to prompts/personal/bourdain.md.
- New docs/tools/athena.md documenting CRM capabilities and MCP tools
- Refactor docs/work/alan.md to separate system prompt from persona
reference
- Clarify Athena scope, vocabulary, and operational gotchas
Watson replaces Seneca as of 2026-04-28, shifting to a warmer, less goal-oriented approach.
Retained Reflection, Value, Habit, LifeEvent, and Intention node types under Watson.
Added new node types: EmotionalMemory, RelationshipTheme, DialogueNote, and DynamicPattern.
Updated the unified schema table to reflect ownership changes for these nodes.
- 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.
