Week 3: The Parts That Do the Work

Two apologies, two different components turn out to be doing the work — an ablation test replaces the hunt for one universal hierarchy

8 March 2027

Slides: pending upload

Week 2 established that an apology has four separable components and that a real one can still be missing one of them. It did not say which component matters most — because there isn’t a single answer. What breaks an apology depends on the apology.

Take two cases.

Case one — after embarrassing someone in front of their family:

I know I embarrassed you in front of your family, and that’s on me. I feel awful about it. I’ll check with you before I bring anything like that up again.

Remove “that’s on me” and the apology collapses into a description of the speaker’s own feelings — no different from confessing you’re upset about something you did, without owning it. Remove the emotional line instead and almost nothing changes; the apology is flatter but still works. Here, acceptance of responsibility is the component the apology can’t do without.

Case two — an automated notice after a delayed order:

We take full responsibility for this delay. Your refund has been processed. We are updating our courier partnerships to prevent this in future.

Every box is technically checked — responsibility named, remedy delivered, even a commitment to change — and it still reads as hollow, because nothing in it acknowledges that a person was inconvenienced. Restore one sentence, “we know this cost you time you didn’t have to spend,” and the same message reads as an apology instead of a transaction log. Here, responsibility and remedy were never the problem; the missing piece was acknowledgment of harm as something that happened to someone.

What the two cases show#

The same four components trade places in importance depending on the case. In case one, responsibility is functional and regret is close to decorative. In case two, responsibility and remedy are already handled, and the whole thing turns on whether harm is acknowledged as directed at a person rather than logged as an event. Neither case licenses a universal ranking — what a component’s removal costs depends on what the wronged party in that specific situation was actually missing.

Function versus performance, without a fixed hierarchy#

Call a component functional in a given case if removing it changes whether the statement still works as an apology there, and performative if removing it only changes tone. The same component can be functional in one apology and merely performative in the next. Responsibility-acceptance turns up as functional more often than the other three across public examples, which is worth noticing — but “more often” is not “always,” and treating it as the fixed answer would mean missing cases exactly like the refund notice, where responsibility was never what was missing.

When two components are both load-bearing#

The two-case method suggests exactly one component fails at a time, which isn’t always true. Take a manager’s apology for publicly overriding a report they hadn’t read: “I overruled your recommendation without reading it first, which was disrespectful of your work, and I’m sorry — I’m reversing the decision and reading the full report today.” Remove the responsibility clause (“which was disrespectful”) and the apology collapses into a bare description of an event. Remove the remedy clause (“I’m reversing the decision”) instead, and it collapses just as completely — a responsibility claim with no action behind it reads as words only, in a case where the harm is a decision still sitting there, uncorrected. Both ablations break it. That doesn’t mean the method failed; it means this case’s four components aren’t independent load paths but two doing one combined job — naming the act, and undoing its effect — and removing either one removes half of a job that only counts as done when both halves are present.

That’s the method the rest of the semester runs on failed apologies: not “which component is missing,” as if the answer were fixed in advance, but “which component was this specific apology actually resting on, and what happened to it.”