Administrative operations
Administration is a trusted server/operator responsibility. Host application JWTs never gain a deployment key, raw maintenance handler or provisioning power through scope metadata.
Setup and executable policy
cortex backend install prepares local additive sources. Development register and provision verify the exact disposable target and target-bound credentials. Trusted internal policy installation, tenant narrowing and guarded Agent publication establish executable configuration.
Transcript lock/approval policy changes require administrator authority and the expected revision. Published Agent version revocation, membership/grant revocation and tombstone operations fence future effects and delivery.
Explicit root SDK and compatibility
Lower-level root SDK APIs serve explicit domain memory operations and server administration. Local provider wrappers require explicit deploymentOperator mode plus separately authenticated administrative transport; the mode is routing, not Convex authentication. A host JWT transport and deployment operator transport are initialized separately.
Ordinary clients receive CAPABILITY_UNAVAILABLE before legacy local model/memory orchestration effects. Use @cortexmemory/sdk/runtime and the provider /remote transport for application requests.
Export, erasure and maintenance
Domain views differ from complete supported-layer user export. Administrative export/erasure use fixed operation allowlists and explicit tenant scope; omitted tenant selects tenantless data, not every tenant. Receipts disclose supported scope, shared/foreign/provenance residuals, verification and partial/unknown outcomes.
Native deployment ZIP tools are separate from domain export. Lifecycle-bearing archives/targets refuse unsupported import before mutation. Installation/status/help do not migrate data. Protected restore sessions and automatic legacy runtime migration are not supplied by this release.
Keep native handlers internal. Use CLI reference, user operations and governance API.