Unverified50% confidenceDecision RuleExact time
Additive changes include adding optional fields, new paths and new operations, which are usually backward compatible, but edge cases such as naming conflicts should be noted.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/18/2026
First Seen
Valid until: 1/16/2027
Sources
Related Entities
Related Claims
UnverifiedPossibly breaking changes include renaming enum values, tightening validation schemas, and removing response properties.69% similarUnverifiedA one-shot full rename of a field is risky in any case; the safer path is to add a new field first, migrate consumers one by one, and then remove the old field, and this order matters more than the repository layout.69% similarUnverifiedAn effective prompt should contain only new facts that have changed since the last call, relevant paths, and the recent diff — not the entire repository.67% similarUnverifiedDuring retrieval, a freshness weight can be layered on top, so that when conflicting memories on the same topic exist, the one with the higher version number is prioritized and the older version is retired.66% similarUnverifiedWhen tracking prompts, the wording should be locked: once a prompt is modified, the trend data is broken; new wording should be added as a new row rather than replacing the original entry.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1058035API
curl https://kongchang.com/api/v1/knowledge/claims/1058035MCP
get_claim(id=1058035)