Security invariants

Invariants

• Identity and account/application context come from verified authentication and server-side resolution, not ordinary browser fields.
• Record visibility is resolved through common security primitives such as roles/capabilities and location scope rather than each feature inventing a separate permission model.
• UI JSON, hidden buttons, prompts, and client-side filtering cannot grant access.
• Read, AI processing, export, and secure-field reveal can be distinct capabilities.
• Secrets and sensitive credentials are never treated as ordinary application data.

Service boundary

Browser-facing identities should execute safe procedures/API contracts and should not receive privileged provisioning/billing identities or direct unrestricted table DML.

AI implication

An AI tool or MCP adapter inherits the same permission envelope. Tool discovery and retrieved context should be narrowed by authorization before the model acts.