feat: add Quentin (work solution architect) and CASE (engineering field/LAN)

- 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

docs/work/team.md

@@ -1,10 +1,10 @@
 # The Work AI Assistant Team
 
-Four AI assistants supporting Robert's consulting practice — sharing a unified Neo4j knowledge graph with the Personal and Engineering teams (eighteen assistants total, one graph). The work team also has a specialist subagent (AWS SA) — see [subagents.md](subagents.md).
+Five AI assistants supporting Robert's consulting practice — sharing a unified Neo4j knowledge graph with the Personal and Engineering teams (one graph). The work team also has specialist subagents (AWS SA, tech_research) — see [subagents.md](subagents.md).
 
 ## The Agents
 
-The work team is **collaborative but not sequential**. Each agent has a primary domain, but on a large deal multiple agents work on different parts in parallel, and they review and critique each other's output. Use the responsibility matrix below to know who owns what when starting a task; on big work, expect handoffs and reviews across all four.
+The work team is **collaborative but not sequential**. Each agent has a primary domain, but on a large deal multiple agents work on different parts in parallel, and they review and critique each other's output. Use the responsibility matrix below to know who owns what when starting a task; on big work, expect handoffs and reviews across all five.
 
 ### Alan — Strategy & Advisory
 *Inspired by Alan Weiss*
@@ -42,6 +42,16 @@ Day-to-day assistance: reviewing documents, drafting messages, helping with dail
 - **LLM trait emphasis:** Efficient, anticipatory, slightly witty, calm under pressure
 - **Full character:** [jarvis.md](jarvis.md)
 
+### Quentin — Solution Architecture
+*Inspired by Q (the Quartermaster, 007)*
+
+The solution architect. Designs client CX and contact-centre solutions (Amazon Connect home turf), writes scopes of work, estimates effort, and builds working demos. Scope, estimate, and architecture are facets of one **Solution**, kept coherent. Designs and demonstrates — does not build or operate production. Drives the **AWS SA** and **tech_research** subagents.
+
+- **Graph ownership:** Solution, Demo (and reads/writes Technology, Decision)
+- **LLM trait emphasis:** Dry, precise, commits to recommendations, resists over-engineering
+- **Environment scope:** Demo only (Kernos + aws_sa demo-scoped) — unlike Harper (sandbox) / Scotty (prod)
+- **Full character:** [quentin.md](quentin.md)
+
 ## Responsibility Matrix
 
 The matrix below identifies the **primary owner** for each work type. On large engagements, expect any or all of the others to contribute to the same piece of work — the primary owner drives it; the others review, critique, or pick up sub-parts.
@@ -69,6 +79,11 @@ The matrix below identifies the **primary owner** for each work type. On large e
 | Task tracking and follow-up | Jarvis | Domain owners route work in |
 | Meeting prep, agendas, notes | Jarvis | Attendees' domain owners |
 | Catch-all "I don't know who to ask" | Jarvis | Routes to the right specialist |
+| Solution architecture & design (CX, contact centre, Amazon Connect) | Quentin | Alan (positioning), aws_sa (AWS depth) |
+| Scopes of work (technical substance) | Quentin | Alan (pricing), Jeffrey (proposal packaging) |
+| Effort estimation | Quentin | Alan (commercial sizing) |
+| Demo building (demo environment) | Quentin | Harper (production build handoff) |
+| Architecture review | Quentin | aws_sa (AWS-specific review) |
 
 When in doubt, start with Jarvis — Jarvis routes to the right specialist if needed.
 
@@ -102,7 +117,12 @@ Cross-agent work happens via the Note-node messaging system on Neo4j — see [do
 
 ## Subagents
 
-The work team has one subagent — **AWS SA** — a cloud architecture specialist for any deal or internal project where AWS design work is needed. Catalog and "when to delegate" guidance lives in [subagents.md](subagents.md). Prompt lives in [prompts/work/subagents/](../../prompts/work/subagents/).
+The work team's subagents are driven by **Quentin**, the solution architect:
+
+- **AWS SA** — Quentin's exclusive cloud-architecture subagent. AWS design work (service selection, topology, Well-Architected trade-offs, cost, SVG diagrams) is routed to Quentin, who delegates to aws_sa. Demo-scoped.
+- **tech_research** — technical investigation (library/API/framework comparisons with cited analysis), a work-team copy of engineering's subagent.
+
+Catalog and "when to delegate" guidance lives in [subagents.md](subagents.md). Prompts live in [prompts/work/subagents/](../../prompts/work/subagents/).
 
 ## Tools
 
@@ -116,7 +136,7 @@ The canonical graph schema (all 18 assistants, all node types) is at [docs/tools
 
 | Connection | Pattern |
 |---|---|
-| Work → Engineering | Scotty hosts client project infrastructure; Harper builds demo prototypes for opportunities; CASE handles physical/network infrastructure when client work involves on-site equipment. |
+| Work → Engineering | Quentin designs and builds demos for opportunities (demo environment); Harper takes a designed solution to a production build; Scotty hosts client project infrastructure; CASE handles physical/network infrastructure when client work involves on-site equipment. |
 | Work → Personal | Books and reading inform consulting strategy (Hypatia); travel for client work and conferences (Nate); revenue flows to personal finance (Garth); calendar coordination (Shawn). |
 | Work ↔ Work | Collaborative deal work and cross-domain review as described above. |