Trust routes
The trust hub is a routing layer for technical evaluators. It links the pages that explain boundaries, install-surface source, and the category decisions behind memory.
Isolation, no training, deletion posture.
Review shipped tenant-boundary claims and roadmap-labeled compliance work.
Open SourceOpen client edges, managed engine.
Check the MCP server and CLI packages without implying the hosted engine is open.
Why memoryCategory education for agent memory.
Understand why inspectability, supersession, and erasure semantics matter.
Legal surfaces
Privacy, terms, and DPA pages are legal-document surfaces. This trust hub links them without inventing legal language in a marketing issue.
Claims that stay next
Compliance and erasure proof matter, so they stay visible. They also stay explicitly future-only until the implementation and evidence exist.
The right-to-erasure marketing claim stays gated on A.5 product work and verification.
SOC 2 is a roadmap compliance item, not a held certification.
Enterprise identity controls remain shipping-next until built and verified.
If it is not shipped, it stays labeled.
Use the security and open-source pages to evaluate today. Use the roadmap chips to see what is intentionally not being claimed yet.