While a Decision represents “what must be done,” a Memory is the advisory, explanatory context that answers “why something was decided”. Memories prevent organizational memory loss by preserving the debates, evaluations, and business requirements that led to a specific architectural choice.Documentation Index
Fetch the complete documentation index at: https://docs.hopsule.com/llms.txt
Use this file to discover all available pages before exploring further.
Key Characteristics
Advisory, Not Enforced
Memories provide context but are not strictly enforced by Hopsule’s AI or IDE integrations. They guide understanding rather than restricting code.
Mutable & Living
Unlike decisions, memories are fully mutable. You can update them as your project’s context or your understanding of a problem evolves.
Relational
Memories are explicitly linked to decisions. When a warning references an accepted decision, the linked memory explains why it exists.
Semantic Search Ready
Every memory is chunked and embedded into your Project Brain using pgvector, making it instantly retrievable by the Hopper AI.
Decisions vs. Memories
Understanding the strict boundary between these two concepts is the key to Hopsule’s authority model.| Aspect | Decision | Memory |
|---|---|---|
| Authority | Authoritative | Advisory |
| In-product behavior | Surfaced via IDE warnings and AI context (advisory) | Context only, not rule checks |
| Immutability | Immutable when ACCEPTED | Mutable (can be updated) |
| Purpose | Constrain behavior | Provide context |