Uh oh!
There was an error while loading. Please reload this page.
Qualitative consequences, positive framing, and consistent length targets - #477
Closed
neoneye wants to merge 1 commit into
Closed
Qualitative consequences, positive framing, and consistent length targets#477neoneye wants to merge 1 commit into
neoneye wants to merge 1 commit into
Conversation
…gets Replace number-focused constraints with qualitative framing: "Exact numbers will be determined further downstream — here the goal is to articulate the cause-effect relationship clearly." This avoids the permission-floor effect where models derive numbers by arithmetic from real plan figures (4x HKD regression in PR #475). Section 5 prohibition changed from "NO fabricated statistics without evidence" to "NO specific numbers, percentages, or monetary amounts — describe effects qualitatively." All length targets consistent: consequences "2-3 sentences" in both field descriptions and system prompt. review_lever "one sentence (20-40 words)" in both field description and system prompt section 6. Replace negative prohibition ("Do NOT include 'Controls ... vs.'") with positive framing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
neoneye
commented
Mar 31, 2026
MemberAuthor
Self-improve iteration — analysis 72Verdict: CONDITIONAL Wins:
Residual:
Conditions: Confirm timeouts are noise (re-run), and consider removing the "downstream" anchor phrase. |
neoneye
commented
Mar 31, 2026
MemberAuthor
Closing — not convincingly better than baseline. Will refine: keep stricter review_lever and shorter consequences, but allow plan-provided numbers instead of banning all numbers outright. |
This was referenced Mar 31, 2026
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 freeto 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
PR #475's "Never invent" constraint made fabrication 4x worse — models interpreted it as a permission floor and derived numbers by arithmetic from plan figures. This PR removes the number discussion entirely.
Test plan
🤖 Generated with Claude Code