Unverified50% confidenceDecision RuleExact time
Hard 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedDeny rules directly block matching tool calls; ask rules force a confirmation prompt even in Auto Mode; allow rules broad enough to grant arbitrary code execution privileges are still sent to the classifier for re-examination.74% similarUnverifiedRisk approval rules should be written into code rather than prompts, because prompts drift with repeated editing while code goes through review and test coverage.72% similarUnverified应将终态描述当作约束条件（constraints）而非视觉建议，约束条件是可验证的71% similarUnverifiedIn prompt engineering, checkable rules break style down into quantifiable constraints, similar to "constrained decoding" or structured prompting ideas in large model applications, turning subjective judgment into objective conditions that can be checked item by item.70% similarUnverifiedThe article distinguishes advisory instructions from deterministic instructions: prompts or CLAUDE.md content are still part of the model's input and can be ignored, whereas hooks, CI checks, and branch protection rules execute outside the model and are guaranteed to trigger.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1036296API
curl https://kongchang.com/api/v1/knowledge/claims/1036296MCP
get_claim(id=1036296)