Features

Incident response

Structured handling for things that go wrong — drift signals, customer complaints, regulator inquiries.

Incident response is the workflow that turns a signal — a drift alert, an inbound complaint, an SLA breach, an external regulator query — into a tracked, accountable piece of work with a beginning, a middle, and an end. Every state change is recorded on the ledger, so the timeline of who did what and when is provable.

Lifecycle

  1. OPENED — by a system signal or a user
  2. TRIAGED — assigned a severity and an owner
  3. INVESTIGATING — owner is gathering evidence
  4. REMEDIATING — taking action: pulling a model, escalating to a senior reviewer, contacting customers
  5. RESOLVED — the action is complete
  6. POST_MORTEM — root cause and lessons captured

Evidence produced

  • Per-incident ledger entries for every state change
  • Linked artefacts: drift reports, affected jobs, related certificates
  • Signed post-mortem document attached as a certificate

FCA mapping

  • PRIN 11 — Relations with regulators
  • SYSC 6.1 — Compliance arrangements
  • DISP 1 — Complaints handling

See also