docs/PHASE2: formulate — MCP client + tool-calling bridge
Phase 2 formulate manifest. Three pillars per PHASE0.md §11 row 2:
mcp.lua (JSON-RPC 2.0 over HTTP+SSE, target: lmcp), tool-calling bridge
(OpenAI tools field <-> MCP tools/call), and the safety.lua
authorization gate (per-call confirm + auto_approve policy).
Resolves PHASE0.md §13 Q6–Q10:
Q6 CMD: + tool-calls coexist; substrate §3 unchanged
Q7 config-declared servers + runtime :mcp connect
Q8 per-call confirm default, auto_approve policy in config
Q9 hybrid system prompt: static frame + dynamic tools body field
Q10 streaming-from-day-one on Phase 1 SSE; on_delta widens to (kind, payload)
New questions tracked in §11 (Q17–Q22): transport abstraction, role:tool
vs prefix injection (mistral-nemo template verification needed), large
tool-result handling, parallel dispatch, error mapping, aish-as-MCP-server
(parked).
§4 module layout amended: mcp.lua slots between broker.lua and router.lua.
The amendment is documented in this manifest; the actual §4 table edit
lands when implementation starts (Phase 2 implement phase).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
marfrit
ec6793c93c