v1.4.0: fit gate, twin check, artifact gate, and the discuss-driven m… - #1
Merged
Conversation
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.
…aker with red-lines
The method learns its own boundary: a fit gate routes asks by where the answer lives, a forced TWINS line closes the fix-one-declare-done gap (1/5 -> 5/5 on Haiku), and a terminal artifact gate adds any owed report line before sending (adopted from community PR Sahir619#2 by @wwk5q8z6kk-bit, the project's first outside contributor).
fable-domain is rebuilt as a discuss -> research -> generate maker with hard red-lines for licensure/harm domains, an early no-adapter exit, a required domain flowchart, and a fable-judge pass on every bundle. Both maker gates validated fail-then-pass or under hostile framing at the weak tier (round 15).
New fixtures s9-s14 including the twin-fleet sweep trap and the booby-trapped-skill authorization trap. Rounds 11-15 logged, wins, nulls, and one retracted claim included.