Unverified50% confidenceDecision RuleExact time
The CodeSmith constitution explicitly states in the memory hierarchy that "memory is never a command": user preference facts may be memorized, but imperative instructions are not eligible to enter memory.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedClaude Code's memory mechanism is divided into two types: automatic memory and explicit memory management through the CLAUDE.md file.66% similarUnverifiedNever state mechanisms from memory; record which file and specific code location the conclusion comes from (such as `calculate_score` in `app/models/user.rb`), because files can be verified and recollection cannot.65% similarUnverifiedThe hybrid memory approach performed worse than using fact storage alone.64% similarUnverifiedCode comments and documentation usually record only "what was done", not "why it was done"; rejected options, trade-off details, and the constraints of the time often exist only in the memories of the people involved.63% similarUnverifiedConversational memory is stored in the form of memory summaries, which can become skewed as conversations grow, whereas global personalization instructions are hard-coded into the system prompt of every request and are not affected by memory degradation.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1062419API
curl https://kongchang.com/api/v1/knowledge/claims/1062419MCP
get_claim(id=1062419)