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

docs(eval): record applied runtime rollback in decision log

Browse Source
This commit is contained in:
William Valentin
2026-02-23 22:48:32 -08:00
parent 8b1f2d9a67
commit 3e5e82c76e
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plans/pi_embedded_evaluation.md
+2 -1
View File
@@ -208,7 +208,8 @@ Track all tool-adjacent/risky prompts that were force-routed to native (`no_tool
- `empty_assistant_text`
Window B shows fallback recovery (0%) but fails minimum sample/baseline gates, so it does not overturn Window A.
Window D confirms guardrail compatibility behavior in controlled probes, but guard compatibility alone is insufficient to justify expansion.
- Next cohort/config delta: route canary users back to native path (remove/disable `pi_embedded` canary routing) until latency/fallback defects are remediated and a fresh canary is re-approved.
- Next cohort/config delta: route canary users back to native path until latency/fallback defects are remediated and a fresh canary is re-approved.
Applied operational rollback in runtime config: `~/.config/flynn/config.yaml` now has `agent_configs.pi_canary.backend: native` (backup created as `~/.config/flynn/config.yaml.bak-rollback-20260223-224801`).
## Diagram/Protocol Impact Review