Unverified50% confidenceDecision RuleExact time
The key constraint of the attempt ledger is to write immediately after each attempt, not to batch-record at the end of the day; a reject must also carry a gate name (one of build, scope, or proof).
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedDiff review should use three gates checked in order, rejecting on the first failure: build (whether the test suite passes), scope (whether the diff only touches allowed paths), and proof (whether new tests failed before the change and pass after it).72% similarUnverifiedThe retry cap should be derived through token budget arithmetic rather than chosen by feel; the function attempt_cap(context_tokens, error_tokens, ceiling_tokens) can compute the number of attempts that fit within the token ceiling.68% similarUnverifiedTo verify whether a rule is in effect, switch to manual mode in a practice copy, temporarily add a prompt rule for the same command, then have it check the repository status; a confirmation dialog is expected to appear (because prompt takes priority over allow)67% similarUnverifiedThe reasoning tier should be treated as a parameter to be tested rather than a default value; reasoning is a switch for handling difficult tasks, not a setting to be left permanently on.66% similarUnverifiedHard limits should be placed in the code rather than in the system prompt; for example, the check in create_refund is the actual rule, while a limit in the prompt is merely a suggestion.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1051253API
curl https://kongchang.com/api/v1/knowledge/claims/1051253MCP
get_claim(id=1051253)