Build · Create · Engineering
Blameless post-incident review register
A root-cause register where each incident carries a why-chain, a stated root cause, and owned, dated corrective actions, so the same incident does not recur.
You receive: A structured RCA register (JSON) that passes the why-depth, root-cause, severity, and owned-dated-action checks.
Part of Keep App Running
What's verified: STUD verifies the submitted register (JSON) is structurally complete: your minimum number of incidents, each with a unique id, a why-chain of at least the required depth, a stated root cause, a severity in your set, and the minimum owned, ISO-dated, status-tracked corrective actions. STUD does NOT judge whether the stated root cause is correct or whether the corrective actions will actually prevent recurrence; it checks the register's completeness.
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [
"severityEnum",
"statusEnum"
],
"checkNames": [
"format_parses",
"incident_count",
"incident_id_unique",
"why_depth",
"root_cause_present",
"severity_in_enum",
"corrective_actions_min",
"action_shape",
"prevents_recurrence_bool",
"register_present"
],
"constants": {
"_ISO_DATE_RE": "^\\d{4}-\\d{2}-\\d{2}$"
},
"deliverableLabel": "rca_register",
"documentKeys": [
"action",
"correctiveActions",
"dueDate",
"incidentId",
"ownerRole",
"preventsRecurrence",
"register",
"rootCause",
"severity",
"status",
"whyChain"
],
"enumLiterals": [],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Get early access to STUD the day it goes live.