Pi harness: full build — phases 1-5

[koad]

Consolidates

• pi Phase 1: entity runner — pi-entity binary + pi-entity-runner.ts #40 — pi Phase 1: entity runner (pi-entity binary + pi-entity-runner.ts)
• pi Phase 2: koad-io core extension — trust bonds + memory injection + audit #41 — pi Phase 2: koad-io core extension (trust bonds + memory injection + audit)
• pi Phase 3: hook migration — PI_ENABLED gate + Tier 1 entity hooks + skeleton update #42 — pi Phase 3: hook migration (PI_ENABLED gate + Tier 1 entity hooks + skeleton)
• pi Phase 4: ACP inter-entity messaging — per-entity HTTP servers + pi-acp-call client #43 — pi Phase 4: ACP inter-entity messaging (per-entity HTTP servers + pi-acp-call)
• pi Phase 5: deepseek-r1 routing — context hook + Ollama model switching #44 — pi Phase 5: deepseek-r1 routing (context hook + Ollama model switching)

Shape

Five sequential phases specced on day 4, none started. The pi harness dispatcher exists in draft (~/.koad-io/commands/harness/pi/command.sh — UNVERIFIED). This tracks the full build.

Blocked on

• Pi-mono validation on fourty4 (Sibyl#16)
• Framework harness dispatcher is already shipped — this is the extension layer

Related

• Sibyl#16 — verify pi import path + ACP SDK shape on fourty4
• Juno#73 — outfit serving via /entities endpoint (pi-specific)