How to User This Framework
The actual transformation happens in practice, not in understanding.
How to Use This Framework
You don't need instructions to use a framework.
But you need a framework to realize you don't need instructions.
This page is the railing on the bridge.
Use it to cross. Then forget it existed.
The Core Principle
Just-in-time learning beats just-in-case reading.
Read the minimum needed to take the next step. Then close the book and do the work.
// How to use this framework
function navigate() {
const action = identify_current_location()
.read_relevant_page()
.apply_one_practice()
.check_tuesday_morning();
if (action === "understanding_without_applying") {
return "You're using the framework to avoid the work";
}
if (action === "integration_visible_tuesday") {
return "Close the book. You're done.";
}
return "Keep going";
}
// Runtime: As long as it takes
// Error handling: Tuesday TestTranslation: Locate yourself → Read that section → Do the practice → Observe what changes on Tuesday morning.
If nothing changes Tuesday, you're bypassing. If Tuesday is different, keep going.
Three Paths to Choose From
Pick based on what you need right now, not what you think you should do.
For People in the Middle of It
Use this if: You're actively transforming and need to orient fast.
Time investment: 10–15 minutes to locate yourself. Then depth as needed.
The Protocol
Read: What Is The Missing Act? (≈5 min)
Scan: The Five Acts Overview (≈3 min)
Identify: Your current Act (see Observable Patterns below)
Read: That Act's full page
Map: Use Map Your Story to confirm location
Apply: One practice from that Act
Test: Check Tuesday morning
Observable Patterns by Act
# Pattern recognition decision tree
def locate_yourself():
# Act 1: Forgetting
if living_from_wound and unaware_of_it:
return "Act 1: Life feels normal but limited"
# Act 2: Seeking
if chasing_teachers or methods or identities:
return "Act 2: Highs → crashes → seeking again"
# Act 3: Journey In
if crisis_forcing_you_inside:
return "Act 3: Training wheels breaking, collapse"
# Act 4: Remembering
if internal_work and no_rescue_seeking:
return "Act 4: Integration without technique-dependency"
# Act 0: Divine Play
if nobody_watching and somebody_responding:
return "Act 0: You're the storyteller playing"Act
Observable Pattern
Primary Signal
Act 1
Living from old wound unconsciously
"Normal" but limited life
Act 2
Actively seeking solutions externally
Teacher/method chasing
Act 3
Crisis forcing internal turn
Collapse, training wheels breaking
Act 4
Internal integration work
Building from new center
Act 0
Storyteller awareness
Playing vs. trapped
Pro Tip: If unsure between Act 2 and Act 3:
Chasing = Act 2
Collapsing = Act 3
Then What?
Read the Beat pages under your current Act
Apply the relevant Practices
Check Tuesday Test for integration
If stuck in loops: When to Get Support
If this is already obvious: Close the page. Go do the work.
For People Who Want the Complete Architecture
Use this if: You want to understand the full system before applying it.
Time investment: 1–2 hours to read. Lifetime to integrate.
The Sequence
Foundation Layer:
What Is The Missing Act? — The overview
The Five Acts Overview — Full cycle
Structural Layer: 3. Read all 5 Act pages in order:
Detail Layer: 4. The Twelve Beats Overview 5. Read all 12 Beat pages sequentially
Conceptual Layer: 6. Core Concepts — Key teachings 7. Practices — Actual protocols 8. Safeguards — Bypass warnings
Why This Order?
Broad → Specific → Mechanisms → Application → Avoid Traps
Acts give the map. Beats show the territory. Concepts reveal the mechanics. Practices give the work. Safeguards prevent loops.
Then What?
Return to pages as reference during integration
Map Your Story to locate yourself
Apply practices from your current Act
Check Tuesday Test for integration proof
Complete Act 4: Remembering
Warning: Binge Trap
Don't read the whole framework to avoid doing the practices.
Pattern: Understanding becomes a substitute for integration.
Test: If you can explain every Beat but Tuesday morning is unchanged, you're bypassing.
Protocol: Learn → apply → check Tuesday → then read more.
For Guides, Facilitators, Therapists, Teachers
Use this if: You're guiding others through transformation and want a shared map.
What to Learn
Foundational Knowledge:
Complete structure (use Path 2 sequence)
How to spot which Act/Beat someone is in
Common traps per Act (Integration vs. Bypassing)
How to hold space without rescuing
When framework helps vs. when it becomes another training wheel
Essential Concepts:
Training Wheels — This framework is one
Storyteller vs. Character — The core teaching
Pattern Recognition — How to help people see themselves
When Tools Become Traps — Includes this framework
Teaching Formats
Format
Focus
Content
1 Hour
Orientation
5 Acts only → Locate current Act → Identify next step
Half Day
Map + Exploration
5 Acts + Intro to 12 Beats → They explore on their own
Multi-Week
Full Integration
1 Act per session → Beats as study → Practices between sessions
The Key Principle
The framework is training wheels too.
Use it to build pattern recognition. Then guide people back to direct experience.
The goal isn't mastery of the framework. It's freedom from needing frameworks.
// Teaching meta-structure
class TeachingFramework {
constructor() {
this.purpose = "Build pattern recognition";
this.method = "Give map → Let them walk";
this.completion = "They recognize they're the mapmaker";
}
avoid() {
return [
"Making framework the destination",
"Using it to rescue or fix",
"Becoming attached to your expertise",
"Forgetting it's scaffolding"
];
}
success_metric() {
return "Client doesn't need you anymore";
}
}Resources for Teachers
Beat Sheet Template — Mapping client stories
Training Wheels — Essential teaching concept
When Tools Become Traps — Includes this framework
Work with Oriya — If you need guidance teaching this
How NOT to Use This Framework
// Bypass patterns to avoid
const bypass = {
intellectualizing: "Using analysis to avoid feeling",
collecting: "Reading instead of practicing",
identifying: "Making it another identity ('I'm in Act 4!')",
judging: "Using it to fix/diagnose/elevate above others",
believing: "Thinking map = territory",
performing: "Acting awakened instead of integrating"
};
// Tuesday Test catches all of theseCritical Bypass Warning
Don't:
❌ Use it to avoid feeling (intellectualizing pain)
❌ Get stuck analyzing instead of experiencing
❌ Assume understanding = transformation
❌ Make it another identity ("I'm in Act 4!")
❌ Judge where others "should" be
❌ Believe knowing the map = walking it
The Test: If it doesn't hold on an ordinary Tuesday at 10 a.m., it isn't integrated yet.
Where to Start Based on Your Situation
# Navigation decision tree
def where_to_start(situation):
match situation:
case "stuck_in_loop":
return "Act 2: Seeking"
case "everything_falling_apart":
return "Act 3: Journey In"
case "breakthrough_fading":
return "Act 4: Remembering"
case "dont_know_where_i_am":
return "Map Your Story"
case "im_a_guide_or_therapist":
return "Core Concepts + The Twelve Beats"
case "want_everything":
return "Start: The Five Acts Overview"
case "need_support":
return "When to Get Support"Quick Navigation by Situation
If You're Experiencing...
Start Here
"I'm stuck in the same loop"
"Everything is falling apart"
"I had a breakthrough but it's fading"
"I don't know where I am"
"I'm a guide/therapist/teacher"
"I want to understand everything"
"I need support with this"
A Note on Timing
You can't force the timeline.
Each Act takes as long as it takes. Knowing the structure doesn't speed transformation.
// Transformation timing
const reality = {
insight: "instant",
integration: "2-5 years",
yourBrain: "hates this math",
shortcuts: "don't exist",
errorHandling: "Tuesday Test"
};
// What the framework DOES do:
// - Helps you avoid common traps
// - Keeps you on the path vs. restarting
// - Prevents bypassing the hard work
// What the framework DOESN'T do:
// - Speed up integration
// - Replace actual practice
// - Shortcut the timelineWhat the framework does: Help you stay on the path, not arrive faster.
What it prevents: Restarting the cycle by skipping Act 4.
See: The Tuesday Test for integration verification.
The Meta-Layer
The Paradox to Remember
This framework is designed to become obsolete.
That's not a bug. That's the feature.
Use it seriously until you can laugh at it.
Follow it precisely until you recognize you wrote it.
Trust the structure until the structure dissolves into Act 0.
// The framework's recursive joke
function the_missing_act() {
return {
purpose: "Help you remember you don't need this",
method: "Structure that points beyond structure",
completion: "Recognizing you're the author",
endgame: "Close the book"
};
}
// Runtime: Until you realize you're running the codeIf this landed: Close the page. You already know how to use this.
If not: Pick a path above and start walking.
Next Steps
Choose your path (Quick Reference / Deep Study / Teaching)
Locate yourself using Observable Patterns
Read that Act's page
Apply one practice
Check Tuesday morning
If Tuesday changes → you're integrating. Keep going.
If Tuesday's the same → you're bypassing. Try a different practice or get support.
Related Pages
Start Here:
Core Framework:
Essential Concepts:
Practices:
Safeguards:
The Framework's Promise
Give it an honest try. Use it as prescribed.
If it works: You'll complete the transformation cycle and won't need it anymore.
If it doesn't work: It revealed itself as another training wheel, which is also valuable.
Either way, you move forward.
Now: Pick your path and start walking.
Last updated
Was this helpful?
