feat(frame): add premise-validity gate (success/failure/simplest_alternative)#172
Merged
Conversation
…rnative) Adds Step 1b to /frame: three required fields that must be answered before tier classification can proceed. Non-falsifiable failure modes surface an abort prompt. Frame artifact gains a required Premise Validity section. Motivated by Roxabi/lyra#1162 (quality-debt infra that measured bookkeeping compliance, not code quality — 1100 LOC that a falsification check would have caught). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
13 tasks
…erion - Insert positive falsifiability rule (measurable outcome + time horizon) before counter-examples in Step 1b evaluation rules - Add 5 canonical proxy-metric LLM anchors after the abort signal sentence Co-Authored-By: Claude Sonnet 4.6 <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
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.
Summary
Originating case: Roxabi/lyra#1162 — quality-debt annotation infrastructure (~1100 LOC + 6 registry files) where `failure_in_6mo` would have been "DEBT count stays flat despite 3 sprint cycles" and `simplest_alternative` would have pointed directly to a regression-cap ratchet (~130 LOC, ~95% of the value).
Closes #169
Acceptance checklist
Coupling note
Issue #168 (`/plan` budget heuristic) is in-flight in parallel. Neither branch touches the same files — no conflict expected.
🤖 Generated with Claude Code