The Map

The Wisdom Reboot Demo: A Map For Finding Signal in Noise

This page demonstrates every tool I'm building into Wisdom Reboot - from Nutshell popovers to pull quotes, from tables to footnotes. But first, let me be honest about what this is.

I'm not a guru. I'm not an expert. I walk to work each day, listening to podcasts, YouTube videos, audiobooks. For decades I've consumed vast amounts of content. And I feel... empty. Without clarity.

Wisdom Reboot is my attempt to turn all that noise into signal. To scratch my curiosity. To unlearn, relearn, and maybe - just maybe - extract something of value from what I'm hearing.

This page is the map I'm using. Not because I've arrived. Because I'm lost in chaos and need a wayfinder.^[1]

0) What This Actually Is

Most demo pages show you features and tell you how great they are.

This one is different because I need it to be.

I've spent five years walking to work, consuming content:

• Podcasts about systems thinking
• YouTube videos on economics
• Audiobooks about cognitive biases
• Papers on Promise Theory

And what do I have to show for it?

A vague sense of having "learned things." But ask me to explain them? To use them? To connect them?

Nothing.

The information goes in. The information dissolves. Like trying to hold water in my hands.

So Wisdom Reboot isn't a teaching platform.

It's my attempt to stop the leak.

To scratch my curiosity deep enough that something actually sticks. To unlearn what I think I know, relearn it properly, and turn consumption into comprehension.

If you're here, you might be lost in the same chaos.

Welcome, fellow traveler.

Optional depth (tap to explore):

• :What "excavation" actually means
• :The difference between summary and synthesis
• :Why I use Nutshell popovers
• :How to spot buried gold in any source

1) The Problem I'm Trying To Solve (Attention Debt)

Here's what doesn't work:

Information keeps arriving. Podcasts, books, papers, conversations. You encounter smart ideas, nod along, and three days later? Gone.

Not because you're not intelligent.

Because explanation doesn't stick. Story does.

Most content explains. I want to excavate stories that teach.

Think about the last podcast you heard. What do you remember?

Probably not the framework they explained.

You remember the moment the guest said something that made you think "Wait, that's what that means?"

That moment? That's what I'm learning to dig for.^[2]

2) How I Want Wisdom Reboot To Work (The Direction)

I'm not recapping content.

I'm learning to reboot it.

The Process I'm Building:

1. Source: Start with information-dense material (podcasts, books, papers)
2. Excavation: Find the story hiding in the explanation
3. Synthesis: Connect it to frameworks (Promise Theory, systems thinking, cognitive biases)
4. Reboot: Create the click moment where understanding shifts
5. Implication: Show what becomes possible when you see it this way

:See the full excavation framework

This isn't summarizing. It's archaeology.

David Senra pans for gold in biographies. I'm learning to do the same with podcasts and technical texts.

:pull I'm finding the buried insight in the throwaway line, the profound in the tangent, the teaching moment in the casual conversation.

3) A Concrete Example (How Compounding Works)

Let me show you what excavation looks like.

Standard Explanation:
"Compounding means small advantages accumulate over time."

Accurate. Forgettable.

Excavated Version:

Here's the problem: I've heard this explained a dozen times. Different podcasts, different books, different voices. And every time I nod along like I get it.

But do I really?

Let me try excavating it - turning the abstract into something I can actually see.

Two people start equal. Same skills, same opportunities, same effort level.

Person A learns 1% faster each day.

Nothing dramatic happens in week one. Or week two. Person B isn't worried - they're keeping up.

But compounding doesn't announce itself.^[3]

By month six, A has pulled ahead.
By year one, A is operating in a different league.
By year two, B isn't "behind."

B is irrelevant.

No villain required. No unfair advantage. Just math.

Winner-takes-all doesn't need villains. It emerges automatically when advantage compounds.

That's excavation. I took a concept everyone nods at and tried to make it visceral enough that I might actually remember it this time.^[4]

4) What Might Eventually Emerge (Still Figuring This Out)

I honestly don't know what form this will take.

Right now I'm experimenting with:

• Essays (however long they need to be)
• Articles (whatever the difference is)
• Letters via Substack (because I still don't understand how email newsletters actually work)
• Maybe eventually YouTube videos (long-form, essay-style)

What I Know I'm Working On:

The Ghost site has almost 50 free subscribers already. I haven't even published anything of value yet.

No idea if that means something or nothing.

The content types will reveal themselves through doing, not through planning.

This section might look completely different in six months.

5) The Writing Principles I'm Learning

I'm building these from "Writing With Flair" by Shani Raja and adapting them for excavation work.

Four Pillars:

Simplicity: Light & Fast

• Plain language unless technical precision matters
• Every word earns its place
• "Use" not "utilize," "help" not "facilitate"
• No careless repetition

Clarity: Bright & Sharp

• First sentence must be crystal clear - lose it, lose the reader
• No fuzzy thinking survives editing
• Complex ideas, simple sentences

Elegance: Beautiful & Balanced

• Sentence rhythm matters (vary length and structure)
• Parallel structures create clarity
• Strategic repetition for emphasis, never from laziness

Evocativeness: Vivid & Visceral

• Concrete details beat abstract concepts
• Sensory information makes ideas stick
• Stories teach what explanation can't

:See the full style guide principles

6) What I'm Aiming For: The Click Moment

Every piece needs one.

The moment where theory becomes concrete.
Where abstraction becomes visceral.
Where you go from "I know this" to "I get this."

Example From Earlier:

When I said "By year two, B isn't behind. B is irrelevant" - did something shift?

That's what I'm hunting for. The click moment.

Not because it's dramatic. Because it makes the mechanism visible.

A system doesn't need villains to produce villainous outcomes.
It only needs incentives and compounding.

This is why I'm learning excavation. Not to inform - to transform understanding.^[5]

7) Technical Features In Action

7.1 Nutshell Popovers (Optional Depth)

Main text stays clean. Optional depth lives behind tappable links.

Example: :Why this matters for AI

You choose your depth. I respect your attention budget.

7.2 Pull Quotes (Strategic Emphasis)

Used rarely. Like a bell, not wallpaper.^[6]

:pull Clarity is built. Not found.

7.3 Wisdom Reboot Notes (My Notes & Connections)

These aren't just for citing sources. They're for my own thinking:

:note Connected Thought
Author A says this. Author B says that. When you put them together... something clicks. Or a book summary I did links here. Or a connection I'm still working out.

Sometimes it's attribution. Sometimes it's synthesis. Sometimes it's just me thinking out loud and showing my work.

7.4 Interactive Simulations

Sometimes the best explanation is a toy model:

Try adjusting the feedback strength. Watch compounding in action.

7.5 Code Blocks (Mechanism in Miniature)

Sometimes the cleanest explanation is mathematical:

advantage(t+1) = advantage(t) × (1 + edge)

If edge > 0 and time is long enough,
the gap becomes unavoidable.

The math doesn't care who "deserves" what.

8) Navigation Features

Jump Links

• Back to the top
• Skip to the close
• See all content types

Cross-Page Nutshell Links

Connect to other essays: :Open a nutshell on another page

Inline Nutshells

Sometimes depth is mid-sentence :like this, part of the flow.

9) The Close (One Line, Then Stop)

If excavation doesn't create a click moment, I haven't done the work yet.

I'll fail at this a lot. But the direction is clear.^[7]

Footnotes

:x What excavation means

Excavation isn't summarizing.

When David Senra reads a biography, he doesn't recap the person's life. He finds the teaching moments - the decisions, the failures, the insights - and pulls them into the light.

I'm learning to do the same with podcasts and technical texts.

What I'm Looking For:

• The story hiding in the explanation
• The example glossed over too quickly
• The moment the speaker almost revealed something but moved on
• The place where theory meets reality and changes shape

What I'm Trying to Create:
The click. The shift. The moment you go from knowing about something to getting it.

That's excavation.

:x Summary vs synthesis

Summary = "Here's what they said"

• Preserves the original order
• Covers everything mentioned
• Feels comprehensive but forgettable

Synthesis = "Here's what this means"

• Reorders around insight
• Cuts ruthlessly to what matters
• Connects to frameworks and other ideas
• Creates new understanding

Summary is preservation.
Synthesis is transformation.

I'm learning to synthesize.

:x Why Nutshell

:note Credit Where Due
The Nutshell concept belongs to Nicky Case. I wanted to use his script, but it was too heavy for Ghost, so I rewrote it from scratch - building in only the features I needed. Some functionality got left behind, but the tradeoff was worth it (robust code, future update proof, simplified).

Your attention is finite.

Some readers want the spine - the main argument, clearly stated.

Others want scaffolding - the proof, the context, the connections.

Nutshell lets you choose.

Main text stays clean. Optional depth lives behind tappable links. No one pays for information they don't want.

Design Principle:
The cheapest sentence that carries the meaning stays in main text. Everything else moves to Nutshell.

This isn't hiding information. It's respecting attention.

(That's the theory, anyway. Whether I can actually execute this consistently is another question.)

:x Spotting gold in any source

The Gold Test:

When processing any source (podcast, book, paper), ask:

1. Where did my understanding shift?
   That's where teaching happened. Mark it.

2. What story is hiding in this explanation?
   Theory needs narrative to stick. Find it.

3. What did they almost say but didn't?
   The pregnant pause, the hedge, the "anyway, moving on" - that's often where gold lives.

4. Where does theory meet reality and change shape?
   Abstract principles behave differently in practice. Capture that.

5. What would make someone say "Oh, THAT'S what that means"?
   If you found it, excavate it. That's the click moment.

Red Flags (Not Gold):

• Obvious statements everyone already believes
• Explanations that sound smart but don't help predict anything
• "Interesting" facts with no teaching power
• Controversy that generates heat but no light

Gold teaches. Everything else is noise.

:x Excavation framework

Phase 1: Source Selection

• Information-dense material (podcasts, books, papers)
• Contains hidden teaching moments
• Expert speakers who've lived the concepts
• Technical content that needs translation

Phase 2: First Pass

• Where did understanding shift for you?
• What stories appeared in throwaway lines?
• What examples got rushed past?
• Where did the speaker hedge or pause?

Phase 3: Pattern Recognition

• Does this connect to frameworks? (Promise Theory, systems thinking, biases)
• Is there a mechanism I can make visible?
• What makes this inevitable, not just "interesting"?

Phase 4: Story Extraction

• Who experienced this principle?
• What did it cost them?
• Where did they fail before succeeding?
• What thought they was true that wasn't?

Phase 5: Synthesis

• Theory becomes concrete through story
• Framework becomes visible in action
• Click moment emerges naturally
• Implication: what becomes possible now?

Phase 6: Compression

• Cut everything that isn't load-bearing
• Move optional depth to Nutshell
• Test: can someone retell this story and teach the principle?

If yes: publish.
If no: excavate deeper.

:x AI implications

Compounding advantage becomes automated advantage when AI enters the picture.

Two firms start equal:

• Firm A integrates AI into shipping cycles
• Firm B stays manual

A doesn't just move 10% faster. A learns 10% faster. Every cycle.

The compounding isn't just operational anymore. It's epistemic.

By month six: A is shipping features B can't match.
By year one: A has pulled market gravity toward itself.
By year two: B isn't competing anymore.

B is data for A's models.

This isn't speculation. This is math + automation.

Winner-takes-all becomes winner-takes-everything when advantage compounds and self-reinforces.

No villain required.

:Read the full essay on AI and economic concentration

:x Style guide expanded

Simplicity: Light & Fast

Rules:

• Default to plain language
• Short words beat long words
• Cut redundant pairs: "past history" → "history"
• Every word earns its place

Test: Can you delete it without losing meaning?

Clarity: Bright & Sharp

Rules:

• First sentence must be crystal clear
• No fuzzy thinking survives editing
• Complex ideas, simple sentences
• If you can't explain it simply, you don't understand it yet

Test: Would a 15-year-old get it?

Elegance: Beautiful & Balanced

Rules:

• Vary sentence length and structure
• Use parallel structures for clarity
• Strategic repetition for emphasis
• Rhythm matters - read it aloud

Test: Does it flow naturally when spoken?

Evocativeness: Vivid & Visceral

Rules:

• Concrete details beat abstractions
• Use sensory information
• Stories teach what explanation can't
• Make ideas felt, not just understood

Test: Can the reader visualize it?

:See full style guide with examples

:x Workshop example

The Availability Cascade (How False Certainty Spreads)

This is the kind of thing I might do if "The Workshop" becomes real. Right now it's just an example of how I'm thinking about teaching biases through experience rather than definition.

You're scrolling. You see the same headline three times from different sources.

Must be true, right?

Here's what actually happened:

Source 1: Reports a claim (low confidence)
Source 2: Cites Source 1 (treats it as fact)
Source 3: Cites Source 2 (now it's "widely reported")

You: "Everyone's saying this - must be real."

That's availability cascade. The more you hear something, the more available it is in memory, the more true it feels.

The Mechanism:

• Repetition creates familiarity
• Familiarity creates trust
• Trust creates certainty
• None of this requires truth

How To Spot It:
Ask: "Am I seeing different evidence or the same evidence repeated?"

If it's one study cited twenty times, you haven't seen twenty studies.

You've seen one study and nineteen echoes.

What Becomes Possible:
When you spot cascades, you stop confusing consensus with truth.

Social proof is useful. Social proof amplified is dangerous.

Whether I actually build "The Workshop" or not remains to be seen. But this is the direction I'm thinking.

:x Inline example

Inline Nutshells are for quick clarifications that don't break flow.

Like when you need to define a term, provide a quick example, or offer an alternate perspective - but the main text shouldn't stop.

When to use:

• Technical term needs one-sentence clarification
• Alternative perspective adds nuance
• Quick example helps without derailing
• Reader might wonder "what does that mean?"

When not to use:

• Complex concepts needing full explanation (use main Nutshell)
• Long digressions (cut them entirely)
• Information that should be in main text (move it there)

some text

Markdown Formatting Reference

Text Styling

Bold: **text** or __text__ → text

Italic: *text* or _text_ → text

Bold + Italic: ***text*** or ___text___ → bold and italic

Strikethrough: ~~text~~ → strikethrough

Highlight: ==text== → highlighted (note: not standard Markdown, works in some editors)

Inline code: `text` → code

Headers

# H1
## H2
### H3
#### H4
##### H5
###### H6

Lists

Unordered:

- Item
* Item
+ Item

Ordered:

1. First
2. Second
3. Third

Nested:

- Item
  - Sub-item
    - Sub-sub-item

Links & Images

Link: [text](url) → example

Link with title: [text](url "title") → hover shows title

Image: ![alt text](url)

Image with title: ![alt text](url "title")

Quotes & Code

Blockquote:

> This is a quote
> Multiple lines

Special custom pull quote style.

:pull If your claim can’t survive compression, it isn’t truth yet.
— Wisdom Reboot

Special custom note quote style.

:note note
— special note

Code block:

```python
def hello():
    print("world")
```

Horizontal Rule

---
***
___

Tables

| Header 1 | Header 2 |
|----------|----------|
| Cell 1   | Cell 2   |
| Cell 3   | Cell 4   |

Other

Footnote: text[^1] then [^1]: footnote content

Task list: (GitHub-flavored)

- [ ] Unchecked
- [x] Checked

Subscript: H~2~O → H₂O (not standard)

Superscript: X^2^ → X² (not standard)

Escape characters: \*not italic\* → *not italic*