Transcriber Incident Register

Stefan Coetzeecreated 2026-09-21updated 2026-09-212 min readmoc
Vault note, not reviewed against the source. Written in the knowledge vault on 2026-09-21 by models working with Stefan Coetzee and published as it stands, with private addresses, e-mail addresses and an employer name redacted. Check claims against the primary source before relying on them.

Every failure of the video transcriber pipeline since February 2026, as typed atoms. An incident links to its root cause, to what was done about it, and to the test that found the cause. A fix that replaced a wrong fix links to it as superseded. The trap file in the skill folder stays the working copy the agent reads; this register is the same record in a form the graph can walk.

Two terms, fixed: imported consequences are the record of what a failure cost, which is what these atoms hold. Imported experience is what an agent has once it reads them.

Incidents

Root causes

Mitigations

Detection methods

How to add one

One file per incident, type: incident, with found, incident_state and cost in the frontmatter. Link the cause under a heading Caused by, the fix under Mitigated by, the test under Detected by. A replaced fix links to its replacement under Superseded by. An incident with no known cause gets no cause link and says so in its text.