DD b12: Ladder Pedagogy for Acronyms in Public-Facing Writing#

Decision (TL;DR): On public-facing pages, introduce a Loewe-coined concept in plain English BEFORE naming it. Then introduce the acronym with its expansion. Then reuse confidently within the same page.
Status: ACTIVE
Scope: All public-facing pages on balospe.com (intros, bridges, hooks, FAQs, top-level section pages). Internal-facing pages (LLogs, AA, DD, paper SIs) are exempt — their audience already knows the terms.
Settled: 2026m04d24, after Claude wrote a bridge page that dropped BABL/OSCR/OLT cold and LLoL named the pattern.
VVN: dd-ladder-pedagogy-dv_ClaOp47Max_OOv1_2026m04d24

Why this DD exists#

The whole purpose of balospe.com is to teach readers to recognize the patterns named by BABL, ZION, OSCR, EDEN, and the rest of the framework. A page that drops “the BABL trap” before any plain-English description fails the teaching mission — it asserts authority instead of building understanding.

The default Claude tendency (and the default expert tendency) is to use project jargon early because it is convenient for the writer. This DD exists to refuse that default for public-facing pages, where the reader is being introduced to the framework for the first time.

The eight rules#

#

Rule

Why / how to apply

R1

Concept before name. Describe the underlying mechanism in plain English, in normal sentences, BEFORE introducing the acronym.

A name handed down without context is asserted authority; a name discovered after the description is earned understanding. Example: talk about “blindly assuming and blindly leveraging short-term wins” in normal prose for a paragraph or two before introducing BABL.

R2

Spell out on first use. Every Loewe-coined acronym gets its expansion the first time it appears on a page: **BABL** (*Blindly Assuming Blind Leveraging*).

Otherwise readers cannot connect the letters to the concept they just learned about. Use bold for the acronym, italics for the expansion.

R3

One acronym per paragraph at first introduction. Don’t drop a second new acronym in the same paragraph as the first.

Two-at-a-time triples cognitive load. Give the reader a paragraph to absorb each one. (Reusing already-introduced terms in the same paragraph is fine.)

R4

Reuse confidently within the page after introduction. Once introduced on the page, an acronym can be used freely on the same page without re-glossing.

Avoid OSCR-by-overcautious-repetition. Trust the reader to remember what was just introduced.

R5

Cross-page recall is NOT assumed. Each public-facing page introduces its own acronyms fresh, even if the same term was introduced on a sibling page.

Visitors land deep into the site from search results; they do not browse top-down.

R6

Audience flag. Internal-facing pages (LLogs, AA, DD, paper SIs) may use site jargon from the start.

Don’t apply newcomer-pedagogy where it isn’t needed. The DD audience is contributors and AI agents who already know the terms.

R7

Glossary-link the heaviest terms. Use the existing site substitutions |BABL|, |ZION|, |OSCR|, etc. (defined in source/_templates/include-file/rst-dict-en.rst) on subsequent references — they render with hover tooltips that show the glossary definition.

Reader can dive deeper without dragging the bridge page into a digression. The glossary is the canonical source; pages echo it.

R8

Trifectas count as terms too. life-trifecta, death-trifecta, gentle kind reasonable, stable extensible humane etc. get a one-sentence gloss on first occurrence in a public page.

They look like ordinary phrases but carry the full ZION/BABL framework. Honor them with a brief introduction.

The audience trifecta#

Public-facing writing on balospe.com walks a knife edge between three audiences. This trifecta names the kinds of readers each page must serve without losing any one of them:

beginners producers experts

  • Beginners need easy introductions — the on-ramp from no framework knowledge to enough understanding that they can engage with the material.

  • Producers need to save time and cost in whatever they make — concrete examples and reusable patterns more than first-principles derivations.

  • Experts need clarity across as many cases of use as reasonably possible — the page should not waste their time with content they already know, but should not assume they share LLoL’s particular vocabulary.

The ladder pedagogy of this DD is what serves beginners without shutting out producers or experts. (See the Trifecta Registry for canonical wording of this and other balospe.com trifectas.)

Worked example: introducing OSCR and BABL on a public page#

WRONG (drops jargon cold):

Computer languages collapse the same way civilizations do: through OSCR — Over-Simplifying over-Complicating over-Reaching.

The pattern is familiar…

A newcomer reading top-to-bottom encounters BABL and OSCR before any plain-English description. The acronyms are asserted, not earned.

RIGHT (mechanism first, then name):

Computer languages tend to collapse the same way civilizations do, and the mechanism is so familiar that anyone who has worked with a language for ten years can recite it.

A “simple” feature is added because someone needs it. To make it work with everything else, more rules are added… [plain-English story, no acronyms]

This three-step pattern — over-simplifying a problem at the start, then over-complicating the workarounds, then over-reaching into places the language was never meant to go — is what Balospe.com names the OSCR pattern (Over-Simplifying, over-Complicating, over-Reaching). OSCR is in turn one symptom of a deeper algorithm that runs by default in any system without active resistance: Blindly Assuming Blind Leveraging, abbreviated BABL.

[continues using BABL and OSCR with hover-tooltips on subsequent references]

When to deviate#

Three cases:

  1. Direct quotations of writing that uses different conventions — quote verbatim.

  2. Internal-facing pages (LLogs, AA, DD, paper SIs) — skip the ladder; use jargon from the start.

  3. Pages explicitly addressing readers who already know the framework (e.g. an advanced subsection of a deep paper) — declare the audience at the top of the section and skip the ladder.

When deviating, leave a one-line comment noting why, so future contributors do not “fix” it back to ladder form.

Migration policy#

  • New writing: use the ladder from the start.

  • Edits to existing content: when editing a paragraph for other reasons, apply the ladder to the same paragraph; do not refactor surrounding paragraphs that are not otherwise being touched.

  • Mass migration of pre-existing pages: only with LLoL’s explicit go-ahead, and only after the migration plan is checked against this DD.

Cross-references#

Created by: Claude Opus 4.7 Max in EDEN mode at LLoL’s request (2026m04d24), after LLoL named the cold-acronym-drop pattern in Claude’s writing of the Evolvix bridge page and asked for a DD that future sessions can honor.