chore: file voice pattern #48 and stamp the inbox pass

Work proposed a rule for the corrective form of antithesis, the "X rather than Y" shape, distinct from the additive form #9 already covers. Their evidence held up and I'm a live instance of it, so the task carries my two additions: it belongs in the attestation high-recurrence set immediately, and the frequency cap needs mirroring into the always-loaded chat rules. The voice skill only runs on publish artifacts, and I noticed this in conversation, so the rule as proposed can't reach the surface I complained about. That second half is now approved and folded in.

1 files changed, 57 insertions, 0 deletions

diff --git a/todo.org b/todo.org
index 9d47566..6750eed 100644
--- a/todo.org
+++ b/todo.org
@@ -39,6 +39,63 @@ Tags are assigned and refreshed by =task-audit=; =task-review= keeps them honest
 
 * Rulesets Open Work
 
+** TODO [#B] Voice pattern #48 — corrective antithesis :feature:
+:PROPERTIES:
+:LAST_REVIEWED: 2026-07-31
+:END:
+Work proposed a new voice pattern for the corrective form of antithesis: "X
+rather than Y", "not X but Y", "X, not Y". Distinct from #9, which catches the
+additive form ("not only X but Y"). My ruling, quoted in the handoff: I don't
+mind it occasionally, but it has to be for emphasis and it can't be overused.
+So it's a frequency rule, not a ban. Proposed cap: about one per 150 words,
+never twice in adjacent sentences, mode tags prose + personal.
+
+Evidence is strong. A four-sentence Slack draft fired it four times in a
+hundred words, and I noticed it across messages, which is the tell that it had
+stopped being a device.
+
+Two additions I'd make before applying:
+
+1. Put it straight into the attestation high-recurrence set. That set is for
+   patterns with documented failure history, and this one arrived with its
+   failure history attached.
+
+2. The frequency rule needs a home outside the voice skill. I noticed this in
+   conversation, and the skill only runs on publish artifacts, so as proposed
+   it can't touch the surface where the complaint originated. Mirroring the cap
+   into =interaction.md= (always loaded) is what would make it bite in chat.
+   That second half is the part worth deciding on.
+
+Per the paired-files rule, any change lands in both =voice/SKILL.md= and
+=voice/references/voice-profile.org=. The handoff already names what the profile
+entry wants: problem statement, the verbatim ruling, the four-in-one-draft
+before/after, and a note that #9 is adjacent-but-different so the two don't get
+merged.
+
+Source: inbox/2026-07-31-1312-from-work-new-voice-pattern-proposal-48.org
+
+*** 2026-07-31 Fri @ 13:32:00 -0500 Craig approved the interaction.md mirror
+So the open half of this task is settled and the work is now fully specified.
+Both homes get the rule, with a cross-reference line in each so an edit to one
+prompts a look at the other. Work argued the duplication is right here because
+the two fire on different surfaces and neither subsumes the other, and I agree:
+a single home leaves one surface uncovered.
+
+Placement: a short subsection under =interaction.md='s existing chat-output
+rules, beside "No Reverse-Video Highlighting in Chat Output". Those rules
+constrain how the agent writes to Craig rather than what it decides, which is
+the same shape.
+
+Work sent suggested text for both files. It needs the em-dashes stripped before
+it lands, since it uses them freely while describing a rule that ships into a
+zero-tolerance context.
+
+Remaining work: the =voice/SKILL.md= rule line, the paired
+=voice/references/voice-profile.org= entry, the =interaction.md= subsection, the
+two cross-reference lines, and adding #48 to the attestation high-recurrence set.
+
+Source: inbox/2026-07-31-1328-from-work-craig-approved-mirroring-the-48.org
+
 ** DOING [#B] Hostile subagent review before every agent commit :feature:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-07-28