“Composite rewards cleverness; pairwise reveals concreteness. Multi-feature accumulation scores high on absolute heuristics but loses head-to-head against single-feature lines with concrete bodily, spatial, or ritualistic anchors. The composite scorer is the feature-presence scan; pairwise is the discriminator scan. When they disagree, pairwise wins — composite is the approximation, pairwise is the operator's taste in execution.”
Surfaced:Build 3331 (One Line pairwise battle calibration — 200-battle ratification). The B3325 substrate (one_line_battles + one_line_elo tables + Haiku judge + Elo K=32 update) ran two 100-battle rounds against the operator-owned 296-anchor corpus. The top Elo winners after 200 battles were moderate-composite (67-78) lines anchored in concrete imagery: "Tea ring where I've been setting down the same cold cup" / "Earned every breath like rent was due" / "My throat knows the weight / Of words I'll never say" / "Throat full of years I couldn't speak" / "Now the vein knows the needle better than it ever knew her prayers." The high-composite Elo losers were abstract-paradox / meta-aware / religious-poetic / smart-aphorism lines: "Every morning I construct me / Every night I come apart" (composite 86, Elo delta -32) / "I've optimized myself out of existence" (composite 77, Elo delta -30) / "Your hands become communion / And I taste salvation whole" (composite 75, Elo delta -46 across 3 battles). The Haiku judge's per-battle rationale named the discriminator each time: "uses concrete self-destruction to anchor abstract loss" / "uses fluorescent hum, engine idle to SHOW emotion not tell it" / "achieves concrete-abstract anchoring via hands as the specific anchor in a named room."
The anti-pattern this names
Composite scorer ships as the only quality signal for a craft detector. Composite (mean-of-top-N over a feature taxonomy) cannot distinguish "smart, abstract, well-assembled" from "concrete, embodied, located" — both trip many of the features. Without pairwise, the high-composite/low-concrete lines get treated as canonical when they are actually the cleverness-tax: lines that LOOK like the move but are not. The pattern shape is consistent (abstract paradox / meta-aware self-commentary / religious-poetic without anchor / smart-aphorism without specific room) and it is invisible to composite alone. Every future quality-of-craft detector built per SA#30 that ships without a pairwise counterpart will recapitulate this bias. The bias is not noise — it is a class — and the class is measurable: across 200 battles in the B3331 ratification round, 13 lines with composite >=75 lost head-to-head by Elo deltas of -100 or more.
The check
Every future quality-of-craft detector that ships per SA#30 must also ship: (1) A pairwise substrate — two tables: comparison records + Elo per item. Schema like one_line_battles + one_line_elo. K=32 standard Elo update. Initial rating 1500. (2) A judge — LLM-based per-battle adjudicator that returns winner + confidence + rationale. The rationale field is load-bearing — it is where the discriminator becomes legible to operator review. (3) A pair-pick strategy — similar-composite windows (+/-5 points works; +/-10 for cold-start) so the judge isn't asked predictable questions. Bias toward pairs with low Elo confidence. (4) A disagreement view — admin query that surfaces lines where composite says "great" and Elo says "average" (or vice-versa). This is the calibration-signal-as-dashboard. (5) A coexistence policy — when composite + Elo disagree by >100 Elo points (~12 composite points), pairwise wins for downstream surfaces (forge anchors, public ranking, public claims). Composite remains the cheap pre-filter; pairwise is the expensive corrective. Relationship to SA#30: SA#30 builds the corpus before the detector. SA#31 names the second axis the corpus makes visible — companion pair. Relationship to SA#25 ("The personal detail is the universal door"): SA#25 is the indie-specific genre instance; SA#31 generalizes it across all genres via pairwise calibration. Canonical phrasing: BRAND.sacredAccident31. Operator-facing arc: docs/ONE-LINE.md + docs/SACRED-ACCIDENTS.md (SA#31 section).
Share this discipline
“Composite rewards cleverness; pairwise reveals concreteness. Multi-feature accumulation scores high but loses head-to-head against single-feature lines with concrete bodily, spatial, or ritualistic anchors. Every detector built per SA#30 needs a pairwise counterpart. — Sacred Accident #31”
Why this gets its own permalink
Each Sacred Accident is a discipline this codebase operates under — a rule named on the public record, enforced in the build pipeline, and cited in every commit that advances the moat it protects. Permalinking each one turns the discipline into a teaching artifact: a buyer or partner who reads this page can cite the exact principle we operate under without grepping our docs.
Canonical phrasing: BRAND.sacredAccident31 · Doc: docs/SACRED-ACCIDENTS.md