Platform · Memory settings
Memory settings. Your data, on your terms.
Each control below answers a specific fear, and each comes with its receipt. Chips say what is live today; design stage means not shipped.
Retention & TTL
Design stage- The fear
- Data outliving its purpose.
- The control
- Designed: per-privacy-class retention windows, swept on schedule. Configurable retention controls are not yet exposed; to request deletion or export, contact us.
- The receipt
- Designed: the sweep is scheduled and its results are visible.
Privacy classes
Design stage- The fear
- One rule for data that deserves several.
- The control
- Designed: every record carries a privacy class, and retention and handling follow the class.
- The receipt
- Designed: the class is on the record, inspectable per contact.
Locked facts
Design stage- The fear
- A fact an agent quietly overwrites.
- The control
- Design stage; enforcement would come with the Reflector contract.
- The receipt
- In the repository substrate a change makes a new version instead of silently replacing the old one. Not yet served to customers.
Bi-temporal record
Design stage- The fear
- History that rewrites itself.
- The control
- Designed: what was true, and when we knew it — two timelines on the record.
- The receipt
- Superseded versions would stay queryable; the chain is the receipt.
Tenant isolation
Live- The fear
- Your callers pooled with someone else’s.
- The control
- Row-level security backstops the tenant filter on the tables that hold customer memory; keys are tenant-scoped.
- The receipt
- Covered in full on the security page.
Durable acknowledgment
Live- The fear
- An acknowledgment that means “eventually.”
- The control
- A 204 means the interaction is durably committed in the database; the commit happens before the response returns.
- The receipt
- A later GET /v1/caller/{phone_number} is the receipt.
Every agent proposes. Northsun governs.