Commit bcd5dcf
committed
fix(loki): spec-contradiction is non-fatal by default (never-fail-a-stage)
The final and most robust layer: a detected spec-contradiction no longer
terminal-fails the run before iteration 1. It is recorded as a high-severity
finding and the build PROCEEDS. This is safe: the completion gate still refuses a
"green" done while an unresolved contradiction stands and it is surfaced in
proof-of-done, so nothing fakes success -- this only stops a false-positive from
KILLING a valid build at 0 iterations. Observed: the LLM grill classifier
over-fires "contradiction" on ordinary ambiguities in real PRDs
(saas-dashboard, markdown-notes killed at 0 iters while landing-page and
url-shortener built cleanly from equivalent specs). Combined with the no-retry
exit-20 terminal, a flaky/mislabeled verdict was a hard build failure.
Default flipped: LOKI_SPEC_CONTRADICTION_FASTFAIL now defaults 0 (proceed);
set =1 to restore the old hard terminal. Companion to the classifier layering
(b5fa4ed/e4d9f4e8/80b02d6c/a3be6479). Feature-branch only.
Claude-Session: https://claude.ai/code/session_01VyBdR1hf2uUTwd84f9amTa1 parent a3be647 commit bcd5dcf
1 file changed
Lines changed: 10 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
16948 | 16948 | | |
16949 | 16949 | | |
16950 | 16950 | | |
16951 | | - | |
| 16951 | + | |
| 16952 | + | |
| 16953 | + | |
| 16954 | + | |
| 16955 | + | |
| 16956 | + | |
| 16957 | + | |
| 16958 | + | |
| 16959 | + | |
| 16960 | + | |
16952 | 16961 | | |
16953 | 16962 | | |
16954 | 16963 | | |
| |||
0 commit comments