Product requirements
Useful memory. Explicit boundaries.
A product that carries context should make its sources, permissions and changes easier to inspect.
Product in development
Keep evidence inspectable.
Retain source references and accepted history. Distinguish an original record, an interpretation and a model-generated summary. An unresolved contradiction should stay visible.
Use only the context the task permits.
Purpose, consumer, scope, expiry and revocation are intended access requirements. A network connection or account alone is insufficient. Permission to retrieve does not imply permission to train a model or reuse the data elsewhere.
Review before a durable change.
Suggestions need a distinct review step. Keep corrections traceable and preserve the previous version. No hidden promotion from conversation to accepted memory is part of the intended design.
Plan for retention and exit.
Export, retention and deletion must account for source records, derived indexes, caches and delivered copies. These are product acceptance requirements, not a guarantee that every copy can be recalled today.
Claims follow the evidence.
Local foundations do not establish deployed security, customer integration or production readiness. Read the development status for the current boundary.