Navigation
This document provides routing logic for the Full Stack Living knowledge base.
Diagnostic Entry Points
Route based on your current constraint:
😴 “I’m always tired”
Likely bottleneck: Health — sleep or energy systems
- Check sleep duration and consistency → Sleep Architecture
- Check circadian alignment → Circadian Rhythm
- Start protocol → Sleep Optimization
- If sleep is fine, check nutrition → Eat Well
- If still fatigued after 30 days, rule out medical causes → Preventive Screening
💸 “Money is stressing me out”
Likely bottleneck: Wealth — cash flow or debt
- Do you know where your money goes? If no → Cash Flow Principle
- Do you have high-interest debt? If yes → Manage Debt
- Do you have an emergency fund? If no → Build Emergency Fund
- Are you investing? If no → Automate Investing
- Paying too much tax? → Optimize Taxes
🧭 “I feel stuck or directionless”
Likely bottleneck: Meaning — purpose or values clarity
- Can you articulate your core values? If no → Define Core Values
- Do you know what you’d do if money weren’t an issue? Explore → Find Your Ikigai
- Are you setting goals that matter to you? → Set Meaningful Goals
- Is your attention captured by screens? → Attention Economics
- Are you anxious or scattered? → Practice Mindfulness
🤝 “I feel isolated or disconnected”
Likely bottleneck: Social — connection quality or frequency
- Understand the stakes → Loneliness Epidemic
- Map your circles → Dunbar’s Number
- Are existing friendships fading? → Maintain Friendships
- Do you need new connections? → Build New Friendships
- Want to become a connector? → Host Gatherings
Domain Structure
The system is organized into four domains plus a meta layer:
| Domain | Function | Entry Point |
|---|---|---|
| Health | Biological hardware | Health |
| Social | Network interface | Social |
| Meaning | Operating system / kernel | Purpose |
| Wealth | Resource allocation | Wealth |
| Meta | Execution layer | Meta |
Each domain contains:
- Concepts : Theoretical frameworks (why)
- Protocols : Executable algorithms (how)
Protocol Selection
High-Leverage Entry Protocols
| Protocol | Domain | Selection Criteria |
|---|---|---|
| Sleep Optimization | Health | Default starting point; upstream of all domains |
| Emergency Fund | Wealth | Prerequisite for financial stability |
| Daily Planning | Meta | Execution foundation |
Compound-Effect Protocols
| Protocol | Domain | Mechanism |
|---|---|---|
| Resistance Training | Health | Exponential strength gains |
| Automated Investing | Wealth | Compound interest |
| Habit Formation | Meta | Behavioral automation |
Execution Framework
- Identify constraint : Which domain is the bottleneck?
- Select protocol : One protocol, minimum viable implementation
- Execute 30 days : No modifications until data collected
- Measure KPIs : Protocol-specific success metrics
- Iterate or stack : Adjust based on data, then add next protocol
Key Resources
| Resource | Function |
|---|---|
| Minimum Viable System | Essential 5-protocol starting configuration |
| Reference Stack | Sample mature implementation |
| Failure Modes | Recovery protocols for system breakdown |
Cross-Domain Integration
Domains interact bidirectionally. See integration documentation:
- Meta → Health Integration
- Health → Meaning Integration
- Health → Wealth Integration
- Wealth → Meaning Integration
- Connection → Health Integration
- Connection → Wealth Integration
- Connection → Meaning Integration
Design Principle
Systems fail when they optimize for information collection over protocol execution.
This knowledge base is structured for action:
- Protocols specify inputs, steps, and measurable KPIs
- Concepts provide decision criteria and tradeoff analysis
- All content links to executable next steps