Marketing memory surface
The public marketing site includes a shipped Memory product surface. It explains the product to evaluators; it is not a second memory runtime, storage layer, or configuration surface.
Availability
The surface is shipped as marketing content. Its factual statements are derived from reviewed shared facts and must remain consistent with the implemented Memory capability and public documentation.
It does not establish package availability, cloud availability, retention guarantees, or support for a host that the product documentation does not independently verify.
Concepts
The surface is a presentation layer over reviewed product facts. It does not own memory capture, retrieval, storage, or lifecycle behavior.
Content flow
- Repository-reviewed facts define the claims that the marketing surface may make.
- The marketing application renders those facts for an evaluator-facing Memory page.
- Product documentation remains the canonical source for setup, interfaces, data flow, security, limits, recovery, and troubleshooting.
Interfaces
This capability has no CLI, MCP, OpenAPI, client, or workspace interface of its own.
Configuration
There is no operator configuration: changes are made through reviewed repository content and application code.
Persistence
The surface does not persist memories, credentials, or customer content.
Security and egress
The surface does not persist memories, credentials, or customer content. It introduces no capability-specific external egress. Runtime persistence and trust boundaries belong to the Memory product capability documented in Memory.
Failure modes
| Failure | Recovery |
|---|---|
| Marketing claim diverges from shipped behavior | Correct the shared fact or page copy in the same reviewed change as the product truth. |
| The surface implies unsupported availability | Remove the claim until implementation and verification evidence exist. |
| The marketing route is unavailable | Restore the marketing application; Memory runtime data is unaffected. |
Recovery
Correct or remove an unsupported claim before republishing. A route outage is recovered in the marketing application and does not require Memory data repair.
Troubleshooting
Compare the rendered claim with the shared facts, the Memory product documentation, and current implementation evidence. Treat any mismatch as a content defect.