Unverified50% confidenceDecision RuleExact time
The project engineering standard explicitly prohibits using the standard library json on performance-critical paths and requires unconditionally enforcing orjson, so a soft fallback (try import orjson / except ImportError: import json as orjson) would violate the architecture policy.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedJSON Schema成为工具参数描述的通用格式，标准化进程降低了跨平台Harness的开发成本65% similarUnverifiedJSON Schema constrains the shape of JSON data through keywords such as type, properties, required, enum, and minimum, but in tool-calling scenarios it cannot express policy constraints such as "whether a path is allowed to be written to", which must be left to the permission and approval layer.64% similarUnverifiedThe Go standard library encoding/json's DisallowUnknownFields() is a strict-mode option that causes decoding to return an error rather than silently ignoring fields when the JSON input contains fields not defined in the target struct.63% similarUnverifiedJSON mode and structured output only solve the problem of format validity; they do not guarantee semantic correctness and do not provide calibrated confidence, so they cannot support threshold policies.62% similarVerifiedConstrained decoding restricts the model, via a predefined JSON Schema, so that each generated token can only be selected from the set of valid tokens.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1064221API
curl https://kongchang.com/api/v1/knowledge/claims/1064221MCP
get_claim(id=1064221)