Repair schema
For each incident, capture harm statement, corrective action, owner, customer notification timestamp, and closure verification.
What is a Repair Log?
Repair logs track remediation actions after harm or errors and tie them to receipts and owners.
Glossary anchor
Repair Log
Connect the explainer to the canonical definition for citations and shared language.
A repair log is a chronological record of remediation actions taken after a system causes harm or errors. It links each repair to a receipt, owner, and resolution status so corrections remain visible and auditable.
Teams use repair logs to prove that remedies happened and to detect recurring failure patterns.
After an automated account lock is reversed, the repair log records the reversal, compensation details, and the time-to-remedy clock.
Implementation
Distinct implementation signals
Unique operational detail to help this concept stand on its own in policy, procurement, and review workflows.
Common failure pattern
Postmortems without follow-through decay into archives; require status transitions until remediation is validated in production.
Evidence to ship
Expose open-versus-closed repair counts, repeat-incident rates, and proof that affected users received remedy or compensation.
Standard
STD-02 — Contestability & Recourse
Align repair logs to the notice, receipt, and remedy obligations in STD-02.
Binding
Binding vectors
Reuse repair log language in procurement clauses and incident triggers.
Evidence pack
STD-02 evidence pack
Attach repair logs to receipts, decision logs, and remedy clocks.
Who owns the repair log?
Ownership should sit with the accountable operator or steward responsible for remedy decisions, not just the support queue.
What belongs in each repair entry?
Each entry should include the triggering receipt, action taken, owner, timestamps, and a link to evidence proving the repair.