Security posture
OSHQ.AI consumes CommandOSHQ workspace authority and applies its own server checks for supported flows. Controls are being verified workflow by workflow.
Canonical workspace authority
CommandOSHQ issues actor and selected-scope context. OSHQ.AI does not create a parallel role or tenant registry.
Server-side checks
Supported intake and capability calls recheck the current session and scope; missing authority blocks the action.
Evidence-linked understanding
Intake understanding links back to captured content. Sources for other responses depend on the connected workflow and must be reviewed.
Workflow records
OSHQ.AI stores scoped intake and conversation records. Trace and audit coverage for each governed workflow is a release validation item.
Server-side model access
Intake understanding uses a server-side provider credential; it is not exposed in the browser. Connected capability calls use the CommandOSHQ boundary.
Validation status
This describes current controls and limits, not a security certification. Broader rollout requires end-to-end verification.