Navigation
This document provides routing logic for the Full Stack Living knowledge base.
Diagnostic Entry Points
Route based on current constraint:
| Symptom | Diagnostic |
|---|---|
| Chronic fatigue | |
| Financial stress | |
| Lack of direction | |
| Social isolation |
Domain Structure
The system is organized into four domains plus a meta layer:
| Domain | Function | Entry Point | | :---------- | :------------------------ | :------------------- | --------- | | Health | Biological hardware | Health | | Wealth | Resource allocation | Wealth | | Meaning | Operating system / kernel | Meaning | | Social | Network interface | Social | | 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
- Wealth → Meaning Integration
- Health → Wealth 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