Workspace records are separated by the database; registries are global

Context

The standard establishes the required policy. This examination does not prove every deployed policy or database grant beyond the scoped declarations.

Decision

Apply the approved database isolation standard to workspace-scoped records and explicitly exempt global catalogues and registries. Cross-workspace staff and intake work uses narrowly scoped privileged paths.

Alternatives Considered

Depend only on application workspace filters. A missed filter could expose another organization’s records.

Consequences

Ordinary workspace requests must not retrieve records owned by another workspace.

Global retirement counts and token lookup need bounded privileged functions.

Cross-workspace binding orphaning is confined to the registration transaction.