Unverified50% confidenceFactExact time
SchemagateRetriever uses the Principal parameter to carry the caller's identity and role, together with top_k to control the upper limit of candidate tables.
1
Sources
50%
Confidence
Long-term
Relevance
10/29/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe correct access control order is: first resolve the caller's identity from the request (not from the model's output), map the identity to a tool allowlist, expose only the tools on the allowlist to the model, and reject tool names not on the list before the parameters are evaluated.64% similarUnverifiedThe criterion for deciding whether to use @-Mentions for manual specification is: whether you can say roughly which file or module the problem is in; if you can, use @ to narrow the scope, and if you cannot, let the Agent search freely.57% similarUnverifiedCascade Layers explicitly declare the order of style priority levels via the @layer rule, solving the problem of relying on selector specificity and source order.57% similarUnverifiedEdit attribution in line-level provenance can be implemented through schemes such as dominant-contribution determination, mixed-label mechanisms, and sub-line-level tracking.55% similarUnverifiedPre-storing or quickly computing Top-K results at each prefix node enables constant query cost — returning a fixed Top-K regardless of how many entries the prefix matches — and is the key to flattening P99 latency.55% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1112309API
curl https://kongchang.com/api/v1/knowledge/claims/1112309MCP
get_claim(id=1112309)