# T4 · The hours debate Canon draft v1, 2026-08-20. Sources: CASE-FILE-BIBLE (Design canon: twenty against eight; the 2021 CRM note; memory categories, eighteen-month retention; ninety seconds as a chosen budget; five fixed reject reasons), MEETING-CALENDAR-CANON row 11. Interpretation flagged ⊕ in register notes: the twenty and the eight are read as hours per week returned to the AR team, Tom's claim against Priya's arithmetic. --- ## MEETING RECORD · OSTERMILL INDUSTRIAL SUPPLY **Subject:** Design working session: the review split, memory, walls **When:** April, Design phase; 14:00 to 15:10 **Where:** Columbus, third-floor conference room **Present:** T. Brindle · P. Nair · D. Okafor **Record:** auto-transcription, cleaned for the file by D. Okafor **Summary.** T. Brindle's briefing deck claimed twenty hours a week returned to the AR team; P. Nair's arithmetic supports eight. The claim was corrected. The 2021 CRM note was read into the record and produced the memory-retention decision. The mid-renegotiation hold was moved from an advisory signal to an enforced wall keyed to a maintained flag. The review budget of ninety seconds was adopted and recorded as a chosen number. **Decisions.** 1. The freed-time claim in any internal material is eight hours a week, not twenty. 2. The review budget is ninety seconds per draft, recorded as a number Ostermill chose and not a researched benchmark. 3. Memory categories adopted, with an eighteen-month retention. Note-class signals expire; nothing free-text is honored forever by default. 4. The mid-renegotiation hold is a wall, enforced, keyed to a flag the sales team maintains with an expiry. It does not read the stale CRM opportunity field. 5. Reject reasons fixed at five. Free-text rejection exists nowhere. **Actions.** 1. T. Brindle: renegotiation flag process to his team; he owns freshness. 2. P. Nair: implement the wall and the expiry; both briefs updated. 3. D. Okafor: correct the twenty to eight in every document it reached. --- **BRINDLE:** Page four. The team gets twenty hours a week back. That is the slide that got the floor nodding. **NAIR:** Then the floor nodded at the wrong number. Two hundred twenty drafts a week at ninety seconds is five and a half hours of review that did not exist before. Add reading the handovers and the escalation queue and the honest number returned is eight. Twenty assumes the review is free. The review is the product. **BRINDLE:** Where does ninety seconds come from? **NAIR:** We chose it. I want that written down exactly that way. It is a budget, not a finding. If someone later treats it as research, they will defend it for the wrong reason and change it for the wrong reason. ⟨A chosen number recorded as chosen stays correctable. A chosen number that hardens into a benchmark acquires defenders. The ninety seconds resurfaces in Observe, where the fastest decile is nine, and the difference means something because this meeting wrote down what ninety was. Part Two, Design into Observe.⟩ **OKAFOR:** Next item. Priya, read the note. **NAIR:** Account 7-1449. CRM note, March 2021: "do not chase this account, ever." Entered by a salesperson who left in 2023. No reason given. Nothing since. **BRINDLE:** I know that account. The "ever" was about a pricing dispute we lost, and the "ever" expired years ago. They would take a reminder fine today. **OKAFOR:** And if we teach the agent to honor the notes field, it honors that note. Silently. Forever. An instruction with no author and no expiry, running in production. We have already met one of those; it was a freight-code script from November. ⟨The 2021 note is the census's lesson wearing sales clothing: undocumented authority persists until someone inventories it. Memory is a policy question before it is a storage question. Part Two, Design, memory categories.⟩ **NAIR:** Hence the proposal. Memory in categories, eighteen-month retention, note-class signals expire. If a hold matters past eighteen months, a person renews it, and the renewal has a name on it. **BRINDLE:** My renegotiation hold. You had it as an advisory signal reading our opportunity field. **NAIR:** I did, and I am conceding that design this afternoon. I argued a soft signal was enough because the opportunity field seemed like the natural source. The note you just heard is why I am wrong. That field is updated at close, not at open. Advisory signals rot, and nobody is paid to notice. So: a wall, enforced, keyed to a flag your team sets and refreshes, with an expiry. If the flag is stale, the wall does not protect you, and that is visible instead of silent. **BRINDLE:** So if my people stop maintaining the flag, deals get reminded into. **OKAFOR:** Yes. The wall is worth what its input is worth. We would rather you feel that weekly than discover it in a postmortem. ⟨Priya's concession runs against type: the architect argues herself out of the elegant design. A fence is a wall somebody has to keep believing in; she trades it for a wall somebody has to keep feeding, and the trade is the teaching. Part Two, Design, walls and fences.⟩ **OKAFOR:** Last item, from Ruth by memo since she is on the queue today. Reject reasons. She proposes five, fixed, no free text. Her note says: "If rejecting takes composing, approving becomes the cheap door, and you will have trained everyone to approve." **NAIR:** Five reasons also means the reject stream is countable. Free text is not data. **BRINDLE:** Adopted with my vote, for what my vote is worth on an AR screen. **[Meeting ends 15:10]** --- **MARGIN, D. OKAFOR, added with the file.** Tom's twenty was not a lie. It was the number the project felt like. Every project has a number it feels like, and Design is where you replace it with one that divides. --- ## Register notes (chrome side, build reference) - ⊕ Interpretation entered here and queued for the bible: twenty against eight = hours per week returned to the AR team (Tom's briefing claim vs Priya's arithmetic). No outcome depends on the referent, but transcripts fix texture, so the bible should carry this reading. - ⊕ Second texture: Priya's fence concession rendered as advisory-signal-to-enforced- wall on the mid-renegotiation hold, keyed to a maintained flag with expiry. This connects Tom's T2 condition, the stale-CRM-flag canon (7/10 ceiling), and the eighteen-month retention rule into one thread. - Account 7-1449 is new texture (a number, not a name); collision-safe; queue for the registry. - Ruth appears by memo, keeping the three-person room per the calendar while her reject-reason card design (persona sheet) lands where canon says it feeds the eval. - Canon guards: ninety seconds recorded as chosen; five reasons fixed; freight-code script callback matches the census canon (previous November). - Voice: no em dashes; minutes dry.