Organisation isolation
Users, credentials, settings, memories and operational records are associated with an organisation boundary.
Security and control
Autonomy needs a boundary.
Commerce OS is designed around organisation scope, explicit credentials, traceable work and human approval for consequential actions.
Owned credentials
API keys and OAuth connections belong to the organisation that configured them; new organisations do not inherit another workspace's provider access.
Human approval
External and sensitive actions can be held for a named approver before execution.
Observable actions
Work timelines retain the request, agent, tool activity, state transitions and resulting artifacts.
Evidence-backed completion
Provider receipts and artifact references are retained where an external action needs proof.
Fail closed
If required credentials, media, permissions or evidence are missing, the operation remains blocked.
Deployment note
Configuration determines the real boundary.
Security also depends on correct database migrations, secret storage, network exposure, OAuth configuration and provider permissions in the deployed environment. The product should report missing configuration rather than silently falling back to shared access.