PKPEEK Docs
Docs/SI services & Sigma

Sigma Companion and service routing

Screen 4.5 — declare Sigma’s permitted tasks, provider route, fallback candidates and manual path.

PEEK Platform Administrator

/peek/customers/tenant-a/4-5
Live walkthrough · Sigma Companion and service routing
/peek/customers/tenant-a/4-5

Sigma is limited to enabled capabilities and evidence the asking user is authorized to see. Routes declare permitted tasks, the provider route, fallback candidates (which must meet the same data, purpose and environment boundary) and the manual path. Capability checks apply to chat-invoked functions exactly as to UI actions.

Note — Asking Sigma to use an unpurchased module, a revoked source or another tenant’s record is denied without disclosing that the thing exists.

4.5 · Sigma Companion & Service Routing

Define routing and Companion access rules. Open it at /peek/customers/tenant-a/4-5 (any tenant ID you can access works in place of tenant-a). The primary action is Validate route, which requires si_route.publish.

How 4.5 works

  1. 1. Declare permitted tasks, provider route, fallback candidates and manual path

  2. 2. Validate current gates

Screen 4.5 contract

Fields shown
Route, allowed provider, permitted tasks, fallback policy
Primary action
Validate route
Required capability
si_route.publish
Validation
Fallback must meet the same authorized data, purpose and environment boundary. Capability checks apply to chat-invoked functions.
Successful outcome
Only authorized context, tools, citations and retained outputs are returned.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.4.5.action (acceptance test AT-UI-4.5)
Requirements
R02, R06, R09, R27, R28, R42, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-4.5
Boundary — Limit Sigma to enabled capabilities and actor-authorized evidence. Missing source modules or provider permissions cannot be bypassed through conversation.
Rejected even if the browser allows it — Ask Sigma to use an unpurchased module, revoked source or another tenant record; deny without disclosing it.

Related guides

Permitted uses, persona access and evidence

Screens 4.3, 4.4 and 4.9 — recommend SI by persona, constrain processing by data class and purpose, and trace use cases to agency approval evidence.

Portal preview, publish and suspend

Screens 4.6 and 4.8 — preview the agency SI settings with synthetic personas, then publish or suspend SI configuration.