SI services overview and continuity
Screens 4.1 and 4.7 — agency SI mode, service inventory, use cases, usage, quotas and degradation.
PEEK Platform Administrator · PEEK Technical Reviewer · PEEK Incident Operator
/peek/customers/tenant-a/4-1SI (Supervised Intelligence) is the product term for model-assisted features: Sigma Companion, background SI tasks and SI-dependent agents. 4.1 shows each tenant’s agency SI mode (the demo tenant tenant-a runs *limited*; tenant-b is *off*), service inventory, allowed use cases and provider readiness — without exposing prompts or secrets.
| Situation | How it is shown | What still works |
|---|---|---|
| Not purchased | Commercial absence | Core manual work |
| Agency turned SI Off | Agency restriction — Companion, background SI and SI-dependent agents blocked | Manual work and deterministic automation (unless All Automation Off) |
| Provider outage or quota exhausted (4.7) | Runtime failure with fallback eligibility | Permitted manual work; no substitution to an unapproved provider |
4.1 · SI Services Overview
Show agency SI status and permitted service capabilities. Open it at /peek/customers/tenant-a/4-1 (any tenant ID you can access works in place of tenant-a). The primary action is Open service governance, which requires si_governance.read.
How 4.1 works
1. Read allowed use cases, agency SI mode, provider readiness and affected capabilities
Screen 4.1 contract
- Fields shown
- Agency SI mode, service inventory, use cases, dependency status
- Primary action
- Open service governance
- Required capability
si_governance.read- Validation
- Show commercial absence, agency restriction and runtime failure separately; metadata must be tenant scoped.
- Successful outcome
- Overview links to governance and synthetic preview without exposing prompts or secrets.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.4.1.action(acceptance testAT-UI-4.1)- Requirements
- R02, R06, R10, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-4.1
4.7 · Usage & Service Continuity
Review sanitized usage and service degradation. Open it at /peek/customers/tenant-a/4-7 (any tenant ID you can access works in place of tenant-a). The primary action is Review continuity options, which requires si_governance.read or si.restrict.
How 4.7 works
1. Review usage/quotas and service health
2. Show bounded continuity options and immediate restriction status
Screen 4.7 contract
- Fields shown
- Usage period, quota, provider status, fallback eligibility
- Primary action
- Review continuity options
- Required capability
si_governance.readorsi.restrict- Validation
- No unapproved provider substitution. Usage counters identify period and freshness; pending work must retain accurate state.
- Successful outcome
- Permitted manual work continues; restrictive action records stop progress and unresolved dispatched calls.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.4.7.action(acceptance testAT-UI-4.7)- Requirements
- R02, R06, R27, R28, R33, R36, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-4.7
Related guides
Provider approval and credential custody
Screens 4.2 and 4.10 — approve provider service profiles (environment, region, processing terms) and define credential custody and rotation.
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.
Incidents, containment and recovery
Screens 8.5 and 8.6 — apply preauthorized containment immediately, then restore service only after current authority and technical checks.