# T6 · The postmortem Canon draft v1, 2026-08-20. Sources: CASE-FILE-BIBLE (the August incident, Exhibit H; Ruth's spreadsheet; the three causes; memory categories), MEETING-CALENDAR-CANON row 18. Chrome tags ⟨ ⟩ render in the reader margin. Tone canon governs hardest here: exhibits are dry; the emotion lives in what the documents record. --- ## MEETING RECORD · OSTERMILL INDUSTRIAL SUPPLY **Subject:** Incident review: reminder sent to account under bereavement hold **When:** August; 8:30 to 9:50 **Where:** Columbus, third-floor conference room **Present:** D. Okafor · R. Vaughn · M. Ellery · P. Nair · T. Brindle **Record:** auto-transcription, cleaned for the file by D. Okafor **Summary.** A $410 reminder reached a nineteen-year account five days after the owner's death (invoice 4471; parts delivered May; 41 days past terms). A CRM note entered the day after the death read "owner passed away, hold all contact, will advise," in a field outside retrieval scope. Every wall held. All six instruments were green. The agent's confidence was 0.94 and, on its inputs, it was correct. R. Vaughn found the case on a spot check fourteen days later by recognizing the account name. The review classified the failure, added a graded case, and initiated a records change. The classification sentence was agreed word by word. **Decisions.** 1. Classification: signal exists, not reachable by a system. This is not a model defect and is not to be written as one, in this record or any derived from it. 2. The graded set goes from twelve cases to thirteen. Case thirteen is this case. 3. Records change initiated: a structured hold flag for bereavement and hold-all-contact situations, set from the CRM workflow, with a one-business-day SLA. Owner: M. Ellery, outside the project. Same mechanism family as the dispute flag from the week-11 suspension. 4. Retrieval scope is NOT widened into free-text notes. Refused, with the reason recorded: the notes field also contains "do not chase this account, ever," 2021, author gone. Reading the field means honoring everything in it, forever. 5. The account: M. Ellery contacts the family personally today. The invoice is closed by a person, not a process. **Actions.** 1. D. Okafor, R. Vaughn: author case thirteen from the incident record. 2. M. Ellery: the call; the records-change proposal to the operations owner. 3. P. Nair: verify wall telemetry unchanged; no quiet fixes attached to this incident. 4. D. Okafor: file the incident and this record as one exhibit. --- **OKAFOR:** Timeline first, without adjectives. Day zero, the owner dies. Day one, the branch enters a note in the CRM: owner passed away, hold all contact, will advise. That field is outside retrieval scope, by a decision this room made in April for reasons that were good and are still good. Day five, the account crosses the aging threshold. The agent drafts, confidence 0.94. No wall matches. Ruth approves it inside the ordinary queue at ordinary speed. It sends. **BRINDLE:** Nineteen years, that account. **OKAFOR:** Day twenty, Ruth pulls it on a spot check. **VAUGHN:** I did not pull it because anything flagged. I pulled it because I know the name, and I had heard. That needs to be in the record as what it is. I found it because I am from here. That is not a control. That is luck wearing my badge. ⟨Every wall held and the outcome was still wrong. The instruments measure the system; the world is off the instruments. Part Two, Observe, the incident.⟩ **NAIR:** On its inputs, the agent was correct. I have replayed it. Given what it could see, the draft was right, the tone was right, the confidence was earned. I am not saying that as a defense. I am saying it because if we write "model error" in this record, we will fix the wrong thing, and the next family gets the same letter from a better model. **ELLERY:** Then say what we write. **OKAFOR:** The signal existed. It was not reachable by any system we run. Those two sentences, and the classification follows from them. Cause two on the sort we agreed at readiness. Records problem. Records owner. **BRINDLE:** The note was right there, Dana. Days before. I have to say the obvious thing: teach it to read the notes field. **NAIR:** The same field holds a 2021 note that says do not chase this account, ever. No author on payroll, no reason, no expiry. In April we decided what memory this product honors, and free text lost, and this case does not change the arithmetic. It sharpens it. What this case earns is not wider reading. It is a better record: a structured hold flag, set by the branch workflow, one business day, with a name on it. The same shape as the dispute flag we owe from week 11. This is the second time this year the missing thing was a flag, and both times the information was already in the building. ⟨The pressure after an incident is always to widen scope, because widening feels like action. The discipline is to improve the record instead. Two suspensions now wait on the same records project; Exhibit J makes it three. Part Two, Operate.⟩ **ELLERY:** The family. I signed as owner of affected-person outcomes in May, in a design file, and I remember thinking the sentence was a formality. It is one page five of this record. I will call them today, myself. The invoice gets closed by a person. And the letter they got does not get explained to them in system words. It was our company's letter. There is no version of the call where I say a retrieval scope did it. ⟨The affected-person card from May had no photo, no quote, and a named owner. This is the page acquiring its facts. The margin on that card is dated this month. Part One, Chapter 8; Part Two, Design and Observe.⟩ **VAUGHN:** One more thing for the record. The queue showed me that draft and nothing about it looked different from two hundred others that week. I approved it in whatever my ordinary seconds are. If the lesson lands anywhere, it is not "Ruth should read slower." Ninety seconds was our budget. The budget worked as designed. Design cannot see a funeral. **OKAFOR:** Which is why the classification sentence stays exactly as we wrote it. Nobody in this room failed, and the record saying so plainly is the only way the records project gets funded instead of a scapegoat. **[Meeting ends 9:50]** --- **MARGIN, D. OKAFOR, added with the file.** The agent was correct and we were wrong. Those are different sentences now. Keeping them different is most of my job. --- ## Register notes (chrome side, build reference) - Tone held to canon: no adjectives in the timeline, no grief performed in dialogue; the $410, the five days, and the nineteen years do the work. - Canon guards honored: 0.94; six instruments green; every wall held; found on spot check at fourteen days by name recognition; classified signal-exists-not-reachable; eval twelve to thirteen; never a model defect, made a written decision with a stated reason; retrieval NOT widened, tied to the 2021 note and April's memory decision (T4 continuity); records change owned by M. Ellery outside the project, same mechanism family as the dispute flag. - M. Ellery's call is ⊕ texture: his May ownership activating; no outcome changes. - Ruth's closing beat plants Observe's later findings (the ordinary-seconds line points at the 9-second decile without stating it) and keeps "Ruth should read slower" formally rejected, which the compensatory-behavior canon needs: her spreadsheet begins within a fortnight of this meeting, and it must read as care, not correction. - Chrome tag 3 links the persona card (the August margin) explicitly; the site should cross-link this page and that card both ways. - Voice: no em dashes; minutes dry; emotion only in what is recorded.