Tenant and client isolation

DenialOS uses organization + client scoping across the major customer-bound domains.

Examples:

• voice delegations query by organizationId and clientId;
• hospital voice provider/campaign/audience objects are scoped to both;
• AI context manifests are stored with organization/client authorization context;
• EHR canonical records carry organization/client/connection lineage;
• denial cases are read through scoped authorization helpers.

The design goal is:

organization A + client A
          ≠
organization B + client B

and likewise:

connection A
cannot substitute for
connection B

The strongest runtime claim still depends on executing the full adversarial suite against the target database/runtime.