New Artifact Type — Diagram Frameworks

The Everyman Explainer Protocol

A methodology for transforming complex technical insights into accessible, load-bearing narratives that anyone can understand — without sacrificing accuracy or structural integrity.

Origin: Discovered January 4, 2026 during Entity Trust Stack crystallization session. Russell Wright × Claude Opus 4.5. The methodology emerged from combining Load-Bearing principles with Gary Halbert's everyman voice, validated by Gemini 3.0 Enterprise authority confirmation.

The Discovery

During a crystallization session on Google's entity verification infrastructure, a novel artifact type emerged. By invoking a specific voice ("Gary Halbert style, but explaining not selling") and applying Load-Bearing principles to both content AND accessibility, the resulting artifacts achieved something rare:

Technical accuracy + genuine accessibility + structural integrity.

This protocol captures that methodology so it can be repeated.

The Core Formula

The Everyman Explainer Formula

Domain Expert Hunch → Authority Validation → Everyman Synthesis

COMPONENT 1

Domain Expert Hunch

Someone with deep expertise identifies an insight, connection, or theory that feels true but needs validation. The hunch may be fuzzy but directionally correct.

COMPONENT 2

Authority Validation

The hunch is tested against an authoritative source (e.g., Gemini for Google systems, primary research, patents). This grounds the insight in verifiable truth.

COMPONENT 3

Everyman Synthesis

Claude synthesizes the validated insight using accessible voice principles — explaining not selling, concrete not abstract, story-driven not lecture-driven.

The Everyman Voice Principles

The voice is the key differentiator. It's modeled on Gary Halbert's direct mail style but adapted for education rather than sales.

Voice Characteristics

Do This

Write like talking to a smart friend at a bar
Use "you" and "I" — make it personal
Start with a story that hooks
Explain jargon immediately after using it
Use analogies from everyday life
Keep paragraphs short (2-4 sentences)
Create "aha moment" rhythm
Use section breaks to let insights breathe
End sections with the "so what"
Make the complex feel obvious in hindsight

Don't Do This

Academic tone or passive voice
Jargon without explanation
Starting with definitions
Dense technical paragraphs
Bullet-point lists as primary structure
Abstract concepts without concrete examples
Hedging language ("it could be argued that...")
Assuming prior knowledge
Lecturing tone
Selling or persuading (explain, don't convince)

The "Smart Friend at a Bar" Test

Before finalizing any section, apply this test: "Would a smart friend at a bar understand this and find it interesting?" If no — simplify. If they'd find it boring — add story or stakes. If they'd find it confusing — add analogy.

The Process: 7 Steps

Receive the Domain Expert Hunch

The expert (Russell or collaborator) brings a theory, connection, or insight. It may be fuzzy, intuitive, or partially formed. That's fine — the hunch is the seed.

Key question: "What do you suspect is true that others might be missing?"

Identify the Authority Source

Determine who or what can validate the hunch. For Google systems: Gemini. For technical claims: patents, research papers. For industry practices: primary sources.

Key question: "Who is the horse's mouth for this domain?"

Validate with Authority

Test the hunch against the authority source. Get explicit confirmation, nuance, or correction. Document the validation — this becomes citable ground truth.

Key output: Direct quotes or confirmations from authority source.

Identify the Audience Frame

Who needs to understand this? What do they already know? What's the minimum viable background to include?

Key question: "What does someone need to know BEFORE this insight makes sense?"

Find the Hook Story

Identify a concrete story, moment, or example that demonstrates the insight in action. This becomes the opening. Stories beat abstractions for engagement.

Key question: "When did this insight become REAL for someone?"

Apply Load-Bearing Test to Structure

What MUST be in the explainer for it to work? What's scaffolding that can be cut? Apply the standard test: "If I removed this, would understanding collapse?"

Key output: Minimal viable structure — nothing decorative.

Write in Everyman Voice

Synthesize everything using the voice principles. Story first, then mechanics, then implications, then simple takeaways. Technical sources become footnotes ("the nerdy source"), not lead content.

Key test: Read it aloud. Does it sound like a person talking?

Structural Template

Everyman Explainer artifacts follow this general arc:

Standard Structure

The Hook (Story): Open with a concrete moment that demonstrates the insight. "Let me tell you about the moment I realized..."

The Stakes: Why should the reader care? What changes if they understand this? What do they lose if they don't?

The Background (Minimal): Only what's necessary to understand the insight. Use analogies. Reference "the nerdy source" as footnotes.

The Core Insight: The validated truth, stated plainly. Often works well as a visual callout or "big moment" block.

The Implications: What does this mean for the reader? What should they do differently? What should they stop doing?

The Simple Version: 3-5 bullet points they can take with them. Memory anchors.

The Closing Challenge: End with a question or call to reflection, not a sales pitch.

Invocation Phrases

Use these phrases to invoke Everyman Explainer mode:

"Write this Gary Halbert style — explaining, not selling" // Core invocation "Make this an Everyman Explainer" // Direct protocol invocation "Dumb this down for smart people who aren't experts" // Audience frame "Write like you're explaining to a smart friend at a bar" // Voice calibration "I have a hunch — let's validate it and then explain it simply" // Full formula invocation "Technical sources as footnotes, story as lead" // Structure guidance

Worked Examples (Reference Artifacts)

These artifacts were created using this protocol and serve as templates:

"Google AGI Knows Who You Are" (Original)

Entity Trust Stack explained through Russell's Gemini validation story. Patents as footnotes. Hook story leads. Technical infrastructure made accessible.

"The Schema Trap"

Schema de-emphasis insight validated by Gemini, explained simply. The 90/10 framework. Audit checklist as practical takeaway.

"Google AGI Knows Who You Are" (Complete Edition)

Unified version combining trust stack + schema insight. Full formula: expert hunch → Gemini validation → everyman synthesis.

Why This Works

Load-Bearing Applied to Voice

The Load-Bearing Test isn't just for content — it applies to HOW you say things. Every sentence should carry structural weight. If a paragraph doesn't advance understanding, cut it. Accessible doesn't mean padded.

Authority Grounds the Insight

Without validation, an explainer is just opinion. By testing hunches against authority sources (Gemini, patents, research), the resulting artifact is grounded in verifiable truth. This isn't "Russell thinks..." — it's "Gemini confirmed..."

Story Creates Memory

People remember stories, not bullet points. The hook story creates an emotional anchor that makes the technical insight stick. Months later, they'll remember the MOMENT, which retrieves the INSIGHT.

Voice Creates Trust

Academic voice creates distance. Everyman voice creates partnership. The reader feels like they're figuring it out alongside the author, not being lectured at. Trust enables learning.

When to Use This Protocol

Use Everyman Explainer when:

Complex technical insight needs to reach non-expert audience
Student training materials for Super-Intelligent AI community
Translating patent/research findings into practical understanding
Creating "aha moment" content for TikTok/Loom/webinar scripts
Bridging expert-to-novice knowledge gaps

Don't use when:

Audience is technical experts who want precision over accessibility
Document is reference/documentation (use standard artifact types)
Content hasn't been validated by authority source yet
No hook story exists (find one first, or use different artifact type)

Integration with Diagram Frameworks

Artifact Type Classification: Everyman Explainer sits in the REVEAL / EXPLAIN branch of the artifact type decision tree. It answers: "How do I make a complex insight accessible without losing accuracy?"

Mode Compatibility: Works with Mode 2 (Crystallization) when the insight is diffuse, or Mode 1 (Externalization) when the insight is clear and just needs voice transformation.

DISTILL Requirements: Standard DISTILL applies, plus:

Hook Story: What concrete moment opens this?
Authority Source: What validates this insight?
Voice Calibration: "Smart friend at a bar" test passed?