<aside> 🔐

Document purpose: Keep ISAC memory simple, secure, fast, portable and tightly integrated with GCF.

Document status: Architecture/design specification. Current implementation status is controlled by the roadmap and stage evidence.

</aside>

Unified Memory Service

Use one encrypted Memory Service with logical namespaces rather than many unrelated databases.

user
isac
gcf
projects
skills
episodes
devices

Memory Types

Working, episodic, semantic, procedural, user, relationship, project/domain and ISAC self-memory.

Memory Tiers

Tier	Purpose
Hot Cache	Tiny, fast, current conversation/task context.
Warm Store	Recent projects and frequently reused memories.
Compressed Cold Memory	Long-term history stored compactly and retrieved on demand.
Archive	Old raw history retained only when policy allows.

Smart Retrieval

GCF should rank memories by relevance, confidence, importance, project/context fit and recency, then load only a small result set into active context.

Consolidation & Forgetting

Repeated observations can consolidate into stronger structured knowledge. Weak inferred memories may decay. User corrections supersede incorrect memories with provenance preserved. Old raw history may be archived or deleted according to policy.

Storage Limits

The user should be able to set a hard memory budget. ISAC can recommend a value based on available storage. When the limit is approached, GCF may consolidate, compress, archive or ask the user according to policy.