Memory 1: AuthZ

Oracle Agent Memory requires exact user scoping and assigns authorization responsibility to the integrating application. See the Oracle Agent Memory security considerations.

Define this contract first:

• user_id: authenticated principal or deployment-scoped pseudonym.
• agent_id: stable AI Optimizer agent or application identity.
• thread_id: individual conversation identity.
• client: remains an ephemeral settings and session selector.

For the initial trusted-demo mode, client could be mapped to user_id, but memory must be disabled by default and the limitation documented. A later authenticated mode should derive user_id from a verified gateway or identity claim, never a caller-controlled header.