Unverified50% confidenceFactExact time
"No-crash property" is a safety property that only constrains that "bad things do not happen" and does not require that "good things must happen"; by contrast, functional correctness requires complete input-output specifications, and its proof difficulty is an order of magnitude higher.
1
Sources
50%
Confidence
Long-term
Relevance
10/23/2026
First Seen
Sources
Related Entities
Related Claims
Unverified纵深防御原则要求系统安全性不应依赖于用户的完美操作，每一层工具都应假设上一层可能已被突破并提供独立的安全校验68% similarUnverifiedmustNotFail cases are hard constraints: any single failure vetoes the release no matter how high the average score, which corresponds to the "safety invariant" idea in engineering.68% similarUnverified系统的整体可靠性由最薄弱的那个环节决定，消除单点故障是保障关键系统持续可用的首要原则68% similarUnverifiedSetting the security boundary outside the prompt is not a distrust of model capabilities, but a respect for the basic laws of systems engineering.68% similarUnverifiedThe reliable defense against prompt injection is architectural least-privilege isolation: physically separating the steps that process untrusted content from the steps that have tool permissions, and adding a final human confirmation.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1088808API
curl https://kongchang.com/api/v1/knowledge/claims/1088808MCP
get_claim(id=1088808)