← Case Studies/Case #008/C8-023
C8-023Decided — CorrectionPostureDerived2026-04-25

Post-Event Notification and the Commitment Not to Relitigate

Operator-corrected ADR. The AI's version stated 'no retroactive complaint to organizers' and argued against raising the concern informally — both wrong. Corrected record: same-day evening after the prior tournament, the operator sent an informational email to the organizers explaining how premium square scoring works and describing what likely happened with the anomalous result. The email did not request any change to the prior year's result. Organizers acknowledged it. The subsequent year's governance improvements (detailed scoring guide, removal of format ambiguities) are the inferred — not confirmed — response. 'Not relitigating' means: one clean notification to the responsible party, no social discussion, no ongoing pursuit after acknowledgment. It does not mean silence toward the people who can act on the information.

Freshness
Permanent

Permanent. The distinction between clean notification and adversarial relitigating does not expire.

#post-event-email#notification-not-challenge#no-relitigate#informational#organizers-acknowledged#ai-correction#responsibility-channel

Correction Notice

The first version of this ADR stated: "The result is not being raised with the organizers." This was wrong. The operator did raise it with the organizers — via email, same-day evening, after taking time to reflect objectively. The AI's version also argued in the Why-Not section against raising it informally, which was doubly incorrect: not only did the raising happen, it was the appropriate action.

The corrected ADR preserves the correct reasoning about what "not relitigating" means while accurately capturing what the operator actually did.


Capture

The same evening of the prior year's event, after stepping back and considering objectively what might have happened, the operator sent an email to the organizers.

The email:

The organizers acknowledged the email.

In the following year, the organizers introduced a PowerPoint presentation explaining how to score the game correctly, and the ambiguities in the format's rules were substantially reduced. Whether the email was the direct cause of these changes has not been confirmed — the operator assumes the connection but has not asked directly. The alignment between what the email raised and what was subsequently addressed is striking enough to treat as the likely explanation.


Why the Email Was the Correct Action

The email went to the people responsible for the event — the organizers who design the format, set the rules, and run the competition. These are exactly the people who can do something about a scoring integrity problem. Informing them is not adversarial; it is informing the responsible parties of a problem they are positioned to address.

The email was:

This is the correct form of raising a concern. It informs the responsible party, it is not adversarial, and it does not seek to overturn a result that cannot be retroactively adjudicated.


What "Not Relitigating" Actually Means

Not relitigating means:

Not relitigating does not mean:

The email was the single correct action. Acknowledgment was the closure. The matter is addressed, not suppressed.


Why-Not

Why not send a more formal or demanding email? The email's value came from its informational character. An email that demands a specific outcome (rescoring, disqualification) would be adversarial and would be correctly perceived as a challenge to the result. The operator's goal was not to obtain a different result — it was to ensure the organizers understood the scoring rule. An informational email achieves that goal without the adversarial cost.

Why not raise it with the participants directly? Raising it with other participants is relitigating in exactly the sense this ADR rejects. Other participants did not cause the problem and cannot fix it. Direct engagement with them about a scoring concern is social accusation territory. The email to organizers was the correct path precisely because organizers are responsible and positioned to act.

Why not follow up after the email was acknowledged? The acknowledgment was the response. A single well-formed communication was sent; it was received; the organizers had the information. Repeated follow-up converts an informational exchange into a sustained complaint. The email was one action; acknowledgment was the closure. That is the end of the chain.

Why assume the rule changes were a response to the email rather than an independent decision? The assumption is noted explicitly as an assumption. The operator has not confirmed the connection directly. The circumstantial evidence is strong — the changes specifically addressed what the email raised — but the organizers have not stated the cause. The assumption produces no behavioral consequence, and the inferred connection does not affect what the operator did or will do. It is recorded as context, not as confirmed fact.


Commit

Decision: The operator raised the concern with the organizers via a single informational email sent same-day, describing the scoring rule and the likely cause of the anomalous result, without requesting any change to the prior year's result. The organizers acknowledged the email. The operator assumes (without direct confirmation) that the subsequent rule improvements — detailed scoring guidance and removal of prior ambiguities — were a response to the concern. No further pursuit was made. No social discussion of the prior result is undertaken. This is what "not relitigating" means: one clean notification to the responsible party, then closure.

Confidence: High. The distinction between notification and adversarial challenge is clear and the corrected record reflects what actually happened.


Timestamp

2026-04-25

C8-022C8-024