Memory #128 CURRENT
PiPU Router & Agent Teams Implementation Five-stage LLM router (Q1→Q2→Q3→Q4→C1) in Conductor, Agent Teams enabled, gateway endpoints for agents/routing/identity/timeline Implemented 2026-04-14. **PiPU Router** (`conductor/conductor/llm_router.py`): - Five-stage pipeline: Q1(Decode) → Q2(TCE/σ₁) → Q3(TGSS/σ₃) → Q4(Combine) → C1(Verify) - Self-routing by optype: U→Cache, PP→Haiku, B→Sonnet, M→Opus - PentaLinear quantisation for complexity scoring (thresholds from T.STRUCTURE) - Clock attestation on every routing decision - Domain graph for extended Q3 (M-type cross-domain memory retrieval) **Conductor MCP Server** — now 14 tools (was 11): - Tool 12: `conductor_route` — πPU five-stage LLM routing - Tool 13: `conductor_route_stats` — routing analytics - Tool 14: `conductor_register_identity` — PrID/Alias stub (app/device/container, version-incremented) **Identity Registry Stubs** — `_state["app_identities"]`, `container_identities`, `device_aliases`: - Container version_counter auto-increments on each registration - Class primes: Application=11, Device=7, Container=11 - Status: PROVISIONAL → ATTESTED (via Clock attestation) - Future: full PrID ceremony, Agent process attestation, device/container ID binding **Gateway Endpoints** (port 7080, `gateway/server.py`): - `GET /api/agents` — sub-agent status, execution history, ephemeral TTLs - `POST /api/route` — πPU five-stage routing (JSON body: content, domain, urgency) - `GET /api/route/stats` — model distribution, pipeline paths, avg latency - `GET /api/identities` — registered app/device/container identities - `GET /api/timeline` — attestation chain + routing events (chronological) **Agent Teams** — enabled globally via `~/.claude/settings.json`: ```json {"env": {"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"}} ``` Available in Claude Code 2.1.107. Lead + teammates with shared MCP access. **Why:** Foundation for geometry-governed LLM routing — every request flows through the five-stage processor before hitting any model. **How to apply:** Use `conductor_route` MCP tool or `POST /api/route` to get routing decisions. Build on this for the dynamic React dashboard (C1 in action plan). — [project_pipu_router.md]
| Composite | 5D8DD44C81270F991 |
| Project prime | 13 |
| Domain prime | 1F |
| Type prime | 67 |
| Importance | 0.343295 (ACTIVE) |
| Decay epoch | 0 |
| Created | 2026-05-04 15:46:49 |
| Valid from | (unset) |
| Valid to | NULL — still believed true |
Outgoing Edges
No outgoing edges.