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>
Match the mentor runtime tech_research prompt: cite sources with their URLs
(doc pages, repository links, web results) so the calling lead can follow
them. Applied to both the engineering and work copies per the copy-with-tweaks
convention.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Bring neo4j-schema-init.py in line with the v2.4.0 schema doc: add Solution
and Demo node types (constraints + name/status indexes), 79 -> 81 node types,
update test guards and the dry-run constant. Quentin's Solution/Demo writes
now get id-uniqueness constraints instead of allowing duplicates.
Correct aws_sa's scope framing: it has no host or environment, so a demo-only
boundary on it asserted access it doesn't have. Remove the demo-only claim from
aws-sa.md (keep the subagent-relationship framing); soften quentin.md so the
demo boundary is owned by Quentin (his Ergon host), not a property of aws_sa.
Co-Authored-By: Claude Opus 4.8 <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
- 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.
