Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
145 changes: 145 additions & 0 deletions canon/meta/triangle-of-yaps.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,145 @@
---
uri: klappy://canon/meta/triangle-of-yaps
title: "The Triangle of Yaps — One Thought, One Illustration, One Next Step"
audience: canon
exposure: nav
tier: 2
voice: neutral
stability: experimental
tags: ["canon", "meta", "writing", "communication", "essays", "podcast", "scripts", "triangle-of-yaps", "rhetoric"]
epoch: E0009
date: 2026-06-04
source: "Adapted from the 'Triangle of Yapping' communication framework popularized on social media by @iamjadenly. Borrowed, not invented; mapped onto ODD's creed and axioms."
derives_from: "canon/values/axioms.md, canon/values/orientation.md, canon/meta/writing-canon.md"
complements: "canon/meta/writing-canon.md, canon/constraints/ai-voice-cliches.md, canon/methods/choosing-the-right-narrative-container.md, canon/constraints/dual-context-writing.md"
governs: "The rhetorical shape of any single unit of spoken or written communication produced for klappy.dev — podcast script segments, published essays, and the standalone sections within them. Governs engagement structure; subordinate to writing-canon, which governs document structure."
constraint: "This document cannot override the axioms or the Writing Canon. Where the Triangle and progressive disclosure conflict, progressive disclosure governs structure and the axioms govern truth."
---

# The Triangle of Yaps — One Thought, One Illustration, One Next Step

> Every unit of communication carries one Thought or Topic (T or T), pays it down with a Metaphor, Analogy, Example, or Story (M-A-E-S), and closes with an Application or Next step (A or N). A yap with no single thought is noise; a thought with no illustration is an unpaid claim; an illustration with no next step is a claim that never became an outcome. The three corners map one-to-one onto the creed: name what you have observed, prove it with something concrete, and discharge it into action.

---

## Summary — Three Corners That Turn a Yap into an Outcome

The Triangle of Yaps is a constraint on the shape of a single communication unit: a podcast segment, an essay, or a self-contained section inside either. It is not a document-structure rule — that is the job of the Writing Canon (`canon/meta/writing-canon.md`). It is an engagement rule, governing whether the words earn the listener's attention and leave them able to act.

The three corners are:

- **T or T — Thought or Topic.** One idea, with a stance. Not a list of three things you could have said; the single thing you are saying.
- **M-A-E-S — Metaphor, Analogy, Example, or Story.** The concrete vehicle that lets the audience verify the thought against their own experience instead of taking it on assertion.
- **A or N — Application or Next step.** What the audience does now. This is the outcome the whole unit existed to produce.

The framework is borrowed from a social-media communication format and earns its place in canon because it is the rhetorical expression of ODD's epistemics. The apex is a claim, and a claim is a debt (Axiom 2). The illustration is the proof that pays the debt (Axiom 4, and the creed's "before I confirm, I prove"). The next step is the outcome — and in Outcomes-Driven Development, a unit of communication that produces no outcome is the kind of shortcut that always costs more later (Axiom 3).

Run the triangle on anything before you publish or record it. If you cannot name the one thought, find the illustration that makes it land, and state the one next step, the unit is not ready.

---

## The Three Corners

### T or T — One Thought or Topic, Not a Pile of Points

A unit carries exactly one load-bearing idea. The topic is what it is about; the thought is the stance you take on it. "Caching" is a topic. "A cache that outlives its source is a lie you tell on a schedule" is a thought. The triangle requires the thought, not just the topic.

The discipline here is subtractive. Most weak segments fail because they carry three half-thoughts instead of one whole one. When you find a second load-bearing idea, it does not get crammed into the same corner — it becomes its own triangle, its own segment, its own section. One apex per triangle.

This corner is the rhetorical twin of the Writing Canon's Tier 1 and Tier 2: a title that names the concept and its stance, and a blockquote that states the complete claim. If you can write the apex as one sentence a listener could repeat to a friend, the corner is satisfied.

### M-A-E-S — Metaphor, Analogy, Example, or Story Pays the Claim Down

The apex is an assertion, and an assertion the audience cannot check is something they have to either trust or ignore. The base-right corner removes that bind. A metaphor, analogy, example, or story re-renders the abstract claim as something concrete enough that the listener can observe it against their own experience and confirm it for themselves.

The four are a menu, not a checklist — pick the one that fits the thought:

- **Metaphor** — name the thing as another thing ("a stale cache is a photograph of a room you've already left").
- **Analogy** — map the structure of a familiar thing onto the unfamiliar one ("frontmatter is to a document what a passport is to a traveler").
- **Example** — a real, specific instance ("the three canon docs we shipped in February that failed every disclosure tier").
- **Story** — a sequence with a turn ("I planned the write path for months, then deleted the branch — here's what changed").

This corner is where the creed's fifth line bites: *what I have not verified, I will not imply.* A vivid illustration can smuggle in more certainty than the thought has earned. The story must be honest to the strength of the claim — a metaphor that overstates is a debt taken out in the audience's name.

### A or N — Application or Next Step Is the Outcome the Yap Was For

The base-left corner is the one most writers drop, and dropping it is why so much fluent content changes nothing. **A** is application: how the idea is used in the audience's own situation. **N** is the next step: the specific thing to do next. One of the two must be present and explicit.

In Outcomes-Driven Development this corner is not a nicety — it is the point. The thought was the claim; the illustration was the proof; the next step is the outcome that discharges the whole transaction. A unit that informs without enabling action has performed communication without producing it. It feels efficient because something was said, but it leaves the real work undone, which is the exact failure mode Axiom 3 names: shortcuts on the substance always cost more than doing it properly the first time.

---

## How the Triangle Maps to the Creed and the Four Axioms

The Triangle is not a separate value system bolted onto canon. It is the creed (`canon/values/orientation.md`) applied to the act of explaining something to another person:

| Corner | Creed line | Axiom |
|--------|-----------|-------|
| T or T — Thought or Topic | "Before I speak, I observe." | Axiom 2 — A Claim Is a Debt |
| M-A-E-S — illustration | "Before I confirm, I prove." | Axiom 4 — You Cannot Verify What You Did Not Observe |
| A or N — next step | (the outcome the claim was for) | Axiom 3 — Integrity Is Non-Negotiable Efficiency |
| Honest illustration | "What I have not verified, I will not imply." | Axiom 1 — Reality Is Sovereign |

Read top to bottom, the triangle is the creed in motion: observe a real thought, prove it with something concrete, discharge it into an outcome, and never let the illustration imply more than you have earned.

---

## Applying the Triangle to a Podcast Script

A script is a sequence of triangles, one per segment, not one triangle stretched over an episode. Outline the episode as a list of apexes first — the thoughts, in order. Each apex then gets its own illustration and its own next step before the next segment begins.

A worked segment:

- **T or T:** "Your videos flop when they end on the explanation instead of the instruction."
- **M-A-E-S:** "It's like handing someone a map and walking off before you've told them where they're going."
- **A or N:** "Before you publish your next one, write the last line first — make it the single thing you want them to do."

The transition into the next segment is the previous segment's next step landing, then a new apex. If a segment has no next step, it is either filler to cut or two segments wearing one coat.

## Applying the Triangle to an Essay

In an essay, the triangle operates at two scales. The essay as a whole has one apex (its thesis), one governing illustration (its central example or story), and one application (what the reader does differently). Each section then runs its own smaller triangle inside that frame.

Because klappy.dev essays are dual-context — the same file renders as a book chapter and a standalone web essay (`canon/constraints/dual-context-writing.md`) — the next-step corner stays grounded in the reader's own work rather than in "the next chapter." The application a reader can act on travels with them regardless of where they found the piece; a pointer to surrounding navigation does not.

## Where the Triangle and Progressive Disclosure Meet

The two frameworks govern different axes of the same artifact and reinforce each other. The Writing Canon governs **structure** — can each extraction tier be acted on alone. The Triangle governs **engagement** — does the prose earn attention and produce an outcome. They line up cleanly: the apex is the title-and-blockquote claim, the illustration is the body that proves it, and the next step is what the summary leaves the reader able to do. A unit that passes the Triangle but fails progressive disclosure reads well and extracts badly. A unit that passes disclosure but fails the Triangle extracts cleanly and persuades no one. Publishable work passes both.

---

## The Tension — Engagement Compresses, Proof Demands Room

Epistemic rigor and engagement pull against each other, and the Triangle sits on the fault line. A claim is a debt (Axiom 2), and paying it down takes evidence, qualification, and detail — the very things that make a reader's attention drift. The Triangle's compression is what holds that attention, and the same compression leaves almost no room for the proof a rigorous claim requires. Push the full detail in and you lose the reader; strip it out to keep them and you have engagement resting on nothing. Both failures are real, and pretending the Triangle resolves them on its own would be its own kind of dishonesty.

The resolution is to stop treating one triangle as the whole act of communication. The Triangle is the entry point, not the destination. Its job is to earn enough attention and trust that the reader chooses to go deeper, and the corner that performs the handoff is A or N. The next step of the last triangle is not "now you are done" — it is "here is where the proof lives." The engagement layer draws them in; the deeper tiers carry the evidence. This is the same descent the Writing Canon (`canon/meta/writing-canon.md`) already defines: title and blockquote are the hook, the body and its citations are the proof, and progressive disclosure is the staircase between them. The Triangle governs the top of that staircase. It is not responsible for what gets proven three flights down — only for making the first step worth taking.

This is why the Triangle recurses. A whole essay is one triangle whose next step points into its sections; each section is a triangle whose next step points into its evidence; the homepage overview is a triangle whose call to action points into the essay. At every level the shape is the same — hook, illustration, handoff — and the proof is never inside the triangle. It is always one level down. The triangle's only obligation is to make the descent worth taking.

So the scope is deliberately provisional: we apply the Triangle universally without claiming it is universal. It is the default lens for the entry layer of anything we present, used everywhere until a specific case disconfirms it or a better framework earns the slot. Universal application is a working practice; universal truth is not a claim being made here. The retraction condition below is what keeps the practice honest.

---

## Constraints — One Triangle per Unit, Honest Illustrations, Subordinate to the Axioms

The Triangle is illustrative guidance for the shape of communication, not a higher authority than the values it expresses.

- **One apex per unit.** A second load-bearing thought is a second triangle. Do not overload a corner.
- **The illustration must be honest to the claim's strength.** A metaphor that implies certainty the thought has not earned violates the creed's fifth line and must be weakened or replaced.
- **The next step must be real.** A vague "go think about this" is a dropped corner dressed as a present one. If there is genuinely no application yet, that is a signal the thought is not ready to publish, not a license to skip the corner.
- **Subordinate to the Writing Canon and the axioms.** Where the Triangle and progressive disclosure pull in different directions, progressive disclosure governs structure. Where either pulls against the axioms, the axioms govern. This document cannot override them.
- **Not every unit is a triangle.** Some communication is not trying to move anyone — a lament, a raw field note, a reference entry you consult rather than read. Forcing the next-step corner onto those deforms them. The Triangle governs communication meant to persuade or enable action; outside that scope it does not apply, and saying so is not a loophole.
- **Experimental, with a named retraction condition.** This mapping rests on two worked contexts so far — the weekly audio overview and essay structure — so it is a working hypothesis, not a settled law. Retire or revise it if applying the three corners in practice produces flatter or less honest communication than unstructured drafting, or if the creed mapping starts to read as retrofitted rather than load-bearing. Drift is a signal that it is being used, not that it has failed.

---

## Checklist — Before Publishing an Essay or Recording a Script

1. **Apex test:** Can you state the one thought as a single sentence a listener could repeat? If there are two, split into two units.
2. **Illustration test:** Does a metaphor, analogy, example, or story let the audience verify the thought against their own experience, rather than take it on assertion?
3. **Honesty test:** Does the illustration imply only as much certainty as the thought has earned? (Creed line five.)
4. **Next-step test:** Is there an explicit application or next step the audience can act on? Is it real, not "go reflect"?
5. **Outcome test:** If the audience did nothing differently after this unit, did the unit have a point? If not, the A-or-N corner is missing.
6. **Disclosure alignment:** Does the apex match the title/blockquote, the illustration sit in the body, and the next step survive in the summary? (See `canon/meta/writing-canon.md`.)
7. **Ghost-writer test:** Does the illustration sound like the author or like a model? Watch for clustered AI-voice patterns. (See `canon/constraints/ai-voice-cliches.md`.)
8. **Scale test (essays):** Does the whole essay run one triangle, and does each section run its own inside it?
Loading
Loading