PKPEEK Docs
Docs/Oversight, support & audit

Incidents, containment and recovery

Screens 8.5 and 8.6 — apply preauthorized containment immediately, then restore service only after current authority and technical checks.

PEEK Incident Operator · PEEK Technical Reviewer

/peek/customers/tenant-a/8-5
Live walkthrough · Incidents, containment and recovery
/peek/customers/tenant-a/8-5
/peek/customers/tenant-a/8-6

Incident to restoration

  1. 1. Select incident scope

    Choose the affected tenant(s) and capability. You need incident.contain for that scope — the demo Incident Operator covers only tenant-a.

  2. 2. Inspect impact

    Dependency impact is shown with sanitized metadata.

  3. 3. Apply containment

    Preauthorized containment takes effect immediately; a queued review cannot delay it.

  4. 4. Record follow-up

    Stop progress and unresolved external effects are recorded for independent review afterward.

  5. 5. Recovery review (8.6)

    Reviewer checks root cause, credentials, current entitlements, agency authority, test evidence and reconciled outcomes.

  6. 6. Staged reactivation

    Only the approved scope is restored; each resumption is decided and reevaluated explicitly.

Heads up — Recovery never resumes queued handoffs, agent actions or uncertain external effects automatically and never reuses stale approvals. Reactivating after an entitlement or grant was revoked leaves the affected work blocked.

8.5 · Incident & Intervention Review

Contain service risks and record outcomes. Open it at /peek/customers/tenant-a/8-5 (any tenant ID you can access works in place of tenant-a). The primary action is Apply authorized containment, which requires incident.contain.

How 8.5 works

  1. 1. Select incident scope and preauthorized action, inspect impact, apply containment and record review follow-up

Screen 8.5 contract

Fields shown
Incident, scope, operator authority, dependency impact, actions
Primary action
Apply authorized containment
Required capability
incident.contain
Validation
Operator must have incident authority for affected scope. A queued review cannot delay a permitted restrictive stop.
Successful outcome
Containment records immediate decision, stop progress and unresolved external effects.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.8.5.action (acceptance test AT-UI-8.5)
Requirements
R02, R06, R17, R22, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-8.5
Boundary — Preauthorized containment may be immediate with independent review afterward.
Rejected even if the browser allows it — An unassigned operator tries a global stop or recovery; deny the out-of-scope action.

8.6 · Recovery & Reactivation Review

Restore service only after current authority and technical checks. Open it at /peek/customers/tenant-a/8-6 (any tenant ID you can access works in place of tenant-a). The primary action is Authorize staged reactivation, which requires recovery.review.

How 8.6 works

  1. 1. Review repaired service, credential state, current entitlements, agency authority and reconciled outcomes

  2. 2. Approve staged restoration

Screen 8.6 contract

Fields shown
Root cause, credentials, approvals, test evidence, unresolved effects
Primary action
Authorize staged reactivation
Required capability
recovery.review
Validation
Critical unresolved effects or missing authority block restoration of the affected action; never reuse stale approvals.
Successful outcome
Restore only approved scope; each resumption is explicitly decided and reevaluated.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.8.6.action (acceptance test AT-UI-8.6)
Requirements
R02, R06, R17, R22, R28, R36, R38, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-8.6
Boundary — Recheck current entitlements, agency decisions and permissions. Never resume queued handoffs, agent actions or uncertain external effects automatically.
Rejected even if the browser allows it — Reactivate after entitlement or grant revocation; affected work remains blocked.

Related guides

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.

Suspend, recover and execution history

Screen 5.7 — stop agents, track cancellation, reconcile external receipts and decide resumption explicitly.

Connector changes and connection oversight

Screens 6.7 and 6.8 — review custom API requests and connector revisions; monitor health and contain affected capabilities.