docs(domain): override-loop verdict — split keep/retire for behaviors v3#5
Merged
Conversation
…haviors v3 Step #1 of the native-first plan completed. Portfolio scan: 0 overrides across all 12 projects over ~7 weeks (behaviors live since v3.0), including production. Only 4/12 adopted behaviors. Verdict in native-vs-dotforge-boundary.md is now SPLIT: - KEEP the graduated escalation engine (soft_block) — exercised and works; the happy path is "verify" not "override" (observed live this session). - RETIRE/SIMPLIFY the auditable override trail + v4 capture loop — the v3-vs-hookify differential is empirically refuted (0 uses); the loop processes an always-empty log. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Paso #1 del plan native-first completado.
Hallazgo (scan de los 12 proyectos)
.forge/audit/overrides.logen los 12, en ~7 semanas (behaviors v3 viven desde v3.0, 2026-04-13), incluidos production (TRADINGBOT, cotiza — logs vacíos).Veredicto SPLIT (en
native-vs-dotforge-boundary.md)verify-before-donebloqueó un push, resuelto corriendo tests). hookify solo hace block binario; la escalación graduada es un delta real y usado.process-override-log.sh, audit item B3, SessionStart wiring). El diferencial v3-vs-hookify está empíricamente refutado (0 usos); el loop procesa un log siempre vacío.Nota
test_lock.sh(runtime) resultó flaky durante la verificación — falló una vez, pasó en re-run (8/8). No relacionado con este cambio; candidato a estabilizar aparte.🤖 Generated with Claude Code