Unverified50% confidenceDecision RuleExact time
Only the stale state touches the report. On rebuild, each assumption is rebased to its live value and the version number increments, so anyone can see that the answer has changed.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
Unverified"Rebasing" means that when a report is rebuilt due to staleness, each assumption's baseline value is updated to the current live value, and the next comparison starts from there. This avoids error accumulation, at the cost of losing a global view of long-term drift.80% similarUnverifiedWhen a comment is expanded or collapsed, the offsets of all subsequent items need to be recalculated, and improper handling will result in content jumping or positioning misalignment.70% similarUnverifiedNew observations should be collected for mandatory cases after every configuration change, and old passing records should not be reused.69% similarUnverifiedWhen an expected state transition does not occur, the system records the failure as evidence and converts it into an explicit constraint in the symbolic layer.68% similarUnverifiedWhen context becomes too long, history should be organized in segments while retaining recent results, and if necessary a new web conversation with progress should be continued; when the response format is wrong, return it to the model for correction, and if it is still wrong, stop—never execute by guessing.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1013884API
curl https://kongchang.com/api/v1/knowledge/claims/1013884MCP
get_claim(id=1013884)