will/flynn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(plan): add pi canary evaluation gate and tracking (diagram review no topology change)

Browse Source
This commit is contained in:
William Valentin
2026-02-23 22:26:35 -08:00
parent afddd1ba7a
commit 4f88e047fd
7 changed files with 153 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api/PROTOCOL.md
+1
View File
@@ -37,6 +37,7 @@ The gateway serialises agent work **per session**, not per WebSocket connection:
- Lane policy is configurable (`collect`, `followup`, `steer`, `steer_backlog`, `interrupt`) with per-channel and per-session overrides.
- Session-local overrides can be managed at runtime via `agent.send` commands: `/queue`, `/queue set ...`, `/queue reset`.
- Backend selection for a turn is server-side (`native` by default, optional external backends per config: `claude_code`, `opencode`, `codex`, `gemini`, `pi_embedded`) and does not change JSON-RPC method signatures.
- Backend routing and fallback outcomes are emitted to audit logs (`backend.route`, `backend.success`, `backend.fallback`) for rollout evaluation; this telemetry is outside JSON-RPC response payloads.
This is implemented via a per-lane queue (`LaneQueue`) in the gateway server, and used by `agent.send` and `agent.cancel`.