Unverified50% confidenceDecision RuleExact time
The 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedUsing ASSERT_* for preconditions that subsequent assertions depend on, and EXPECT_* for independently verifiable checkpoints, is a common best practice.61% similarUnverifiedFocal Search maintains a FOCAL candidate set containing all frontier nodes that satisfy the threshold w·f_min, and uses a heuristic function within this set for guided selection.60% similarUnverifiedRow-level filters should forcibly inject WHERE conditions at the query execution layer, rather than having the application layer or prompts declare the scope themselves.59% similarUnverifiedThe type-routing approach uses an extremely lightweight classifier to assess complexity before a request enters the decision layer, routing simple requests to Flash and complex ones to the flagship model, avoiding the overhead of two inference calls for a single request.58% similarUnverifiedThe intent router classifies user requests into one of four execution paths: vector_search, entity_lookup, path_synthesis, or general.56% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1024652API
curl https://kongchang.com/api/v1/knowledge/claims/1024652MCP
get_claim(id=1024652)