Known limitations
The important promises that are not complete yet.
These are current product boundaries, not footnotes.
Context conflicts are incomplete
include: ["memories"] materializes cited, temporally eligible Memories whose complete lineage is contained in the selected evidence window. include: ["conflicts"] still returns an empty array. The current Memory atom allows one active value per single-valued slot and has no unresolved-dispute state, so Brain will not mislabel ordinary historical changes as conflicts. Use listMemories for browsing and do not present Context conflicts as complete.
Objects do not arbitrate Context
Accepted Objects are stored and readable, but they do not yet resolve competing Memory claims inside createContext.
Ownership arbitration is partial
Ownership claims are returned, but ownership is not enforced inside every retrieval window. The private spine does enforce operation scopes and forced row-level tenant isolation; those controls do not make an unresolved ownership claim safe to promote to self.
Trace durability depends on the engine
The public InMemoryStore sandbox keeps bounded process-local traces. Private SpineStore deployments persist bounded trace receipts in Postgres and tombstone deleted Record pointers.
Record deletion follows source custody
forgetRecord permanently erases API-origin Records and quarantines partially supported derived rows. Externally reconciled Records return 403 record_not_erasable: delete at their origin and let Brain reconcile, or forget the whole Brain. forgetBrain performs the terminal tenant cascade and leaves one content-free durable receipt.
Sandbox and spine are different
The public Cloud Run sandbox uses InMemoryStore. It proves request/response behavior and the developer experience, never durable or real-corpus memory.
Latency is a live trade
Warm and cold latency depend on the selected retrieval/rewrite path and the backing corpus. Treat all published numbers as dated, dataset-tagged measurements rather than an SLA.
Brain Mac is a bounded customer slice
Brain Mac's read-only four-operation migration is ready. The visible Ask/Search experience and write paths have not moved onto the Memory API yet.
# Known limitations These are current product boundaries, not footnotes. ## Context conflicts are incomplete `include: ["memories"]` materializes cited, temporally eligible Memories whose complete lineage is contained in the selected evidence window. `include: ["conflicts"]` still returns an empty array. The current Memory atom allows one active value per single-valued slot and has no unresolved-dispute state, so Brain will not mislabel ordinary historical changes as conflicts. Use `listMemories` for browsing and do not present Context conflicts as complete. ## Objects do not arbitrate Context Accepted Objects are stored and readable, but they do not yet resolve competing Memory claims inside `createContext`. ## Ownership arbitration is partial Ownership claims are returned, but ownership is not enforced inside every retrieval window. The private spine does enforce operation scopes and forced row-level tenant isolation; those controls do not make an unresolved ownership claim safe to promote to self. ## Trace durability depends on the engine The public `InMemoryStore` sandbox keeps bounded process-local traces. Private `SpineStore` deployments persist bounded trace receipts in Postgres and tombstone deleted Record pointers. ## Record deletion follows source custody `forgetRecord` permanently erases API-origin Records and quarantines partially supported derived rows. Externally reconciled Records return `403 record_not_erasable`: delete at their origin and let Brain reconcile, or forget the whole Brain. `forgetBrain` performs the terminal tenant cascade and leaves one content-free durable receipt. ## Sandbox and spine are different The public Cloud Run sandbox uses `InMemoryStore`. It proves request/response behavior and the developer experience, never durable or real-corpus memory. ## Latency is a live trade Warm and cold latency depend on the selected retrieval/rewrite path and the backing corpus. Treat all published numbers as dated, dataset-tagged measurements rather than an SLA. ## Brain Mac is a bounded customer slice Brain Mac's read-only four-operation migration is ready. The visible Ask/Search experience and write paths have not moved onto the Memory API yet.