Good defaults, tuned when you need them.
MemState balances richness with cost: long histories, wide scans, and stale material are governed so the system stays responsive. Defaults favor safety and explainability; you adjust thresholds when your domain demands it.
How forgetting feels to users
Nothing is silently deleted. Material first becomes less prominent, then can be archived out of default search while remaining recoverable for audits. That protects both user trust and engineering safety.
How retrieval is staged
Search starts from meaning, optionally expands along graph shape, and can add time-aware detail when you ask for how something evolved. You choose how deep each hop goes based on latency and cost budgets.
How operators use these controls
Product teams set coarse policies (how long history should live, how aggressive archival should be). Developers map those policies to environment and runtime settings on the technical pages.
Continue
- Deployment choices (product view)
- Visual maps