Glass-Box Personalization Architecture
How ARMES builds an inspectable, user-controlled memory layer without opaque profiling or third-party data leaks.
The Black-Box Memory Problem
In legacy AI products, "memory" is an opaque, uncontrollable database. The AI silently records snippets about your habits, beliefs, and queries without showing you what was saved, why it was saved, or how it affects future answers. If an AI misinterprets a casual comment, that error persists invisibly and degrades every subsequent response.
ARMES introduces Glass-Box Personalization: an architecture where memory is explicit, structured, completely transparent, and 100% under your control.
The Four Layers of Personal Context
1. Identity Profile -> Name, Role, Communication Style, Hard Constraints
2. Memory Ledger -> Atomic verified facts with source provenance
3. Episode Summaries -> High-level distillations of completed conversations
4. Active Notes & Files -> Explicit project documentation and data1. Identity Profile
High-level directives established during onboarding or in Settings → Personalization:
- Preferred Name & Role: How agents address you and your primary professional lens.
- Goals & Work Style: Your 30–90 day objectives and preferred formatting (e.g., bulleted vs. narrative).
- Hard Constraints: Strict boundaries (e.g., "Never suggest JavaScript when TypeScript is possible").
2. Memory Ledger (Atomic Facts)
Discrete units of knowledge extracted during chats:
- Example: "Prefers Supabase for database schemas over Prisma or Raw SQL."
- Every fact has a provenance link back to the exact conversation where it originated.
3. Episode Summaries
When a conversation concludes, an automated background summarizer distills the key decisions, open questions, and deliverables into an "episode." Agents can reference past episodes without needing the entire multi-thousand-token raw transcript.
4. Active Workspace
Your shared Notes, persistent Files, and active Project lens.
The Injection Envelope
When an agent responds to your prompt, ARMES compiles an Identity Envelope injected as a system preamble:
[object Object],
,[object Object],[object Object], ,[object Object],
,[object Object],[object Object], ,[object Object],[object Object],
,[object Object],[object Object], ,[object Object],[object Object],
,[object Object],[object Object], ,[object Object],[object Object],
,[object Object],[object Object], ,[object Object],[object Object],[object Object], ,[object Object],[object Object],
,[object Object],[object Object],
,[object Object],[object Object], ,[object Object],
,[object Object],[object Object],
,[object Object],
,[object Object],
,[object Object],You can inspect the exact live envelope injected into your agents at any time in Settings → Personalization under the "What agents see" preview card.
Master Personalization Toggle
Personalization is enabled by default so your installed agents can maintain continuity across sessions. You can toggle personalization off entirely in Settings → Personalization at any time. When disabled, no memory envelope is injected and background extraction stops immediately; existing facts remain stored in your vault until you explicitly delete them.