DD b13: Trifecta Registry#

Decision (TL;DR): This file is the canonical registry of every trifecta used on balospe.com. Never invent new trifectas inline; never substitute “almost-equivalent” wording. Add new trifectas here, then use them.
Status: ACTIVE
Scope: Site-wide. Authoritative for which word-triples are trifectas, their canonical wording, and the contexts where each is most useful.
Settled: 2026m04d24, after Claude attempted to substitute “kinder, clearer, and more useful” for “gentle kind reasonable” and LLoL named the BABL-erosion risk.
VVN: dd-trifecta-registry-dv_ClaOp47Max_OOv1_2026m04d24

Why this registry exists#

Trifectas are not interchangeable adjective-triples. Each one is a 3-element fused quality with three irreducible aspects (see DD b11: Trifectas in Single-Italic-Span, No Commas for why the punctuation matters). Substituting “almost the same” wording silently erodes the framework: readers stop seeing the same trifecta recurring across contexts, and the generality of the underlying pattern becomes invisible.

This registry covers only trifectas (3x). For 4-element fused cycles (tetrads such as seed feed grow reap), see DD b14: Tetrad Registry (4-element fused patterns). For higher-arity fused patterns and the full taxonomy across DDs b13–b24, see the overview index DD b25: Fused-Pattern Taxonomy Overview.

The risk is the same kind of BABL drift the trifectas themselves protect against: many small papercuts, each individually defensible, that collectively destroy the convention.

This DD locks down the canonical wording and explicitly forbids inline invention. New trifectas are added here by LLoL, with discussion. Claude may propose candidate new trifectas (see Proposing new trifectas below), but never use a non-registered trifecta in writing.

How to use this registry#

  • Writing a trifecta? Look it up here first. Use the canonical wording verbatim.

  • Tempted to coin a new one? Stop. Read Proposing new trifectas below.

  • Trifectas are equivalent? Some pairs are equivalent in principle but better suited to different contexts (like lambda-calculus and Turing-machines: same expressive power, very different ergonomics for specific tasks). The Equivalences and context column notes when this applies.

  • Formatting: All trifectas follow b11-trifecta-italics-no-commas (single italic span, no commas). All introductions on public-facing pages follow b12-ladder-pedagogy-for-acronyms.

The registry#

The registry is split into three tables — death-trifectas first, then life-trifectas, then other trifectas (audience etc.) — per the BABL-before-ZION ordering rule (CLAUDE.md Language Rule 7).

Death-trifectas#

Canonical wording

Frame

Scope, equivalences, and context

Over-Simplifying over-Complicating over-Reaching

BABL operational pattern (OSCR)

The OSCR pattern — the operational mechanism by which BABL destroys systems. Capitalized for the acronym (O-S-C-R); italics optional in display because the capital letters already mark the structure. Maps to the three idols (BAAL drives over-Simplification, ASHERAH drives over-Complication, MOLOCH drives over-Reach). See OSCR for the full glossary entry.

Blindly Assuming Blind Leveraging

BABL algorithm

The deeper algorithm BABL names: assume blindly that what worked yesterday will work today, then leverage that assumption blindly. The mechanism that produces OSCR. Used in the running text of every public-facing description; abbreviated to BABL once the spelled-out form has been introduced (per DD b12: Ladder Pedagogy for Acronyms in Public-Facing Writing R2).

incurious ignorant indifference

individual-level death-trifecta

The personal-scale death-trifecta: not asking, therefore not knowing, therefore not caring. The three aspects compound on each other — incurious (refusing to investigate) leads to ignorant (lacking the knowledge that investigation would have produced) leads to indifference (lacking the engagement that knowledge would have prompted). The individual-level pattern that aggregates upward into civilizational BABL. Most useful in contexts about personal responsibility, why “I didn’t know” does not excuse, and why each person’s choice to engage matters for the whole. NN status — LLoL added this entry on 2026m04d25; Claude wrote this scope/context on first interpretation; LLoL to refine if the framing drifts from his intent.

Life-trifectas#

Canonical wording

Frame

Scope, equivalences, and context

gentle kind reasonable

ZION life-trifecta (general)

The general-purpose social/civilizational life-trifecta. Order is intentional: reasonable first (long-term sustainability), kind second (equally balanced for all sides), gentle third (smooth dynamic transition). See CLAUDE.md Language Rule 7 for the BABL-before-ZION ordering rule and why reasonable leads within ZION. Most useful in: ethical, social, organizational, and governance contexts. Equivalent to stable extensible life-friendly via the mapping reasonable=stable, kind=life-friendly, gentle=extensible-without-breaking.

stable extensible humane

life-trifecta (computer-language form)

The Evolvix language trifecta. Most useful when describing technical artifacts that must last (computer languages, data formats, protocols, infrastructure). Equivalent to gentle kind reasonable and to stable extensible life-friendly. For computer languages specifically, humane sharpens the third hallmark (intuitive for non-programmers).

stable extensible life-friendly

life-trifecta (general-systems form)

Equivalent to stable extensible humane but with life-friendly in place of humane; the general-systems version. Most useful when the system in question is not narrowly a computer language (e.g. social rules, data, machines for sustainability). Used in A beautiful blue marble and in the b18 papers.

Other trifectas#

Canonical wording

Frame

Scope, equivalences, and context

beginners producers experts

audience trifecta (writing)

The three audiences every public-facing balospe.com page must serve at once: beginners need easy introductions, producers need to save time and cost in what they make, experts need clarity across as many cases of use as reasonably possible. Use this trifecta when reasoning about who a page must serve. See DD b12: Ladder Pedagogy for Acronyms in Public-Facing Writing for the implementation.

Proposing new trifectas#

Claude (and any contributor) may propose candidate new trifectas, but never use one in published writing without LLoL’s go-ahead. The proposal pathway:

  1. Notice the candidate. A genuinely new trifecta tends to surface when the same three-aspect-fusion-quality keeps showing up in different contexts and resists being collapsed into an existing trifecta.

  2. Check existing trifectas first. Most “new” candidates turn out to be context-shifted versions of one of the canonical trifectas above. If so, use the canonical one — do not add a duplicate.

  3. Propose explicitly. In the conversation or AA file, write: “I notice a possible new trifecta: <word1 word2 word3> — it names the fused quality of [explanation]. Worth discussing or adding to the trifecta registry?”

  4. Wait for LLoL’s go-ahead. Either pause for a discussion or accept an AA task to draft the addition for review.

  5. If accepted, add here. With canonical wording, frame, and the Scope, equivalences, and context column populated.

The opposite of proposing is forbidden. Do not silently use a non-registered trifecta in writing. Do not substitute “almost the same” words for an existing trifecta to avoid repetition. Repetition of canonical trifectas is a feature — it lets readers see the same pattern recurring across contexts and start noticing the generality.

When to deviate#

  • Direct quotations of writing that uses different wording: quote verbatim.

  • Pre-existing site content with non-canonical trifecta wording: migrate opportunistically when editing the same paragraph for other reasons; do not run a mass re-format pass.

  • LLoL’s verbatim historical writing (especially archived Zenodo descriptions): exempt unless LLoL explicitly migrates it.

Cross-references#


Created by: Claude Opus 4.7 Max in EDEN mode at LLoL’s request (2026m04d24), after LLoL named the trifecta-erosion risk during a review of Claude’s bridge-page draft.
How to add to this registry: LLoL edits this file directly to add new trifectas, or accepts a Claude-drafted addition via an AA task.