Identity
Reference tenant
Server-selected role; no client role trust
ENTERPRISE TRUST BOUNDARY
Identity, authorization and durable workflow contracts
This surface reports configuration posture only. It never returns tenant IDs, bearer tokens, API keys or persistence credentials.
Authorization
Server enforced
6 workflow actions mapped to application roles
Persistence
Process memory
Safe non-durable fallback until configured
Concurrency
Expected version
409 conflict on stale writes; no last-write-wins stage transitions
APP ROLE POLICY
Server-side workflow permissions
READEXECUTIVE · BUSINESS_OWNER · AI_ENABLEMENT · RISK_REVIEWER
CREATE_USE_CASEBUSINESS_OWNER · AI_ENABLEMENT
ADD_EVIDENCEBUSINESS_OWNER · AI_ENABLEMENT · RISK_REVIEWER
RECORD_APPROVALRISK_REVIEWER
ADVANCE_GATEAI_ENABLEMENT
RESET_DEMOAI_ENABLEMENT
GOVERNED EVIDENCE VAULT
Attach an integrity-verified object
Demo mode uses the server principal. Enterprise mode requires a validated Entra access token; the browser never selects the authoritative role.
Loading server workflow state…
memory evidence · structured-console telemetry
Evidence references are classified, hashed and server-mediated. Telemetry exports metadata only and fails open. Durable configuration status: evidence fallback; telemetry fallback.
What changes when enterprise services are configured
Set Entra tenant/client configuration to require cryptographically verified access tokens. Set PostgREST persistence to move the aggregate workflow snapshot and append-only audit events into Postgres through a transactional RPC. The domain stage-gate engine stays unchanged.
RS256 + JWKSEntra app rolesOptimistic concurrencyTransactional auditNo secret exposure