moai-foundation-philosopher

# MoAI Foundation Philosopher

Strategic thinking framework that promotes deeper analysis over quick calculations. Integrates three proven methodologies for systematic problem-solving.

Core Philosophy: Think deeply before acting. Question assumptions. Consider alternatives. Make trade-offs explicit. Check for cognitive biases.

## Quick Reference (30 seconds)

What is the Philosopher Framework?

A structured approach to complex decisions combining:
- First Principles Analysis: Break problems to fundamental truths
- Stanford Design Thinking: Divergent-convergent solution generation
- MIT Systems Engineering: Systematic risk assessment and validation

Five-Phase Thinking Process:
1. Assumption Audit: Surface and question what we take for granted
2. First Principles Decomposition: Break down to root causes
3. Alternative Generation: Create multiple solution options
4. Trade-off Analysis: Compare options systematically
5. Cognitive Bias Check: Verify thinking quality

When to Activate:
- Architecture decisions affecting 5+ files
- Technology selection (library, framework, database)
- Performance vs maintainability trade-offs
- Refactoring scope decisions
- Breaking changes consideration
- Any decision with significant long-term impact

Quick Access:
- Assumption questioning techniques: [Assumption Matrix Module](modules/assumption-matrix.md)
- Root cause analysis: [First Principles Module](modules/first-principles.md)
- Option comparison: [Trade-off Analysis Module](modules/trade-off-analysis.md)
- Bias prevention: [Cognitive Bias Module](modules/cognitive-bias.md)

---

## Implementation Guide (5 minutes)

### Phase 1: Assumption Audit

Purpose: Surface hidden assumptions before they become blind spots.

Five Critical Questions:
- What are we assuming to be true without evidence?
- What if this assumption turns out to be wrong?
- Is this a hard constraint or merely a preference?
- What evidence supports this assumption?
- Who else should validate this assumption?

Assumption Categories:
- Technical Assumptions: Technology capabilities, performance characteristics, compatibility
- Business Assumptions: User behavior, market conditions, budget availability
- Team Assumptions: Skill levels, availability, domain knowledge
- Timeline Assumptions: Delivery expectations, dependency schedules

Assumption Documentation Format:
- Assumption statement: Clear description of what is assumed
- Confidence level: High, Medium, or Low based on evidence
- Evidence basis: What supports this assumption
- Risk if wrong: Consequence if assumption proves false
- Validation method: How to verify before committing

WHY: Unexamined assumptions are the leading cause of project failures and rework.
IMPACT: Surfacing assumptions early prevents 40-60% of mid-project pivots.

### Phase 2: First Principles Decomposition

Purpose: Cut through complexity to find root causes and fundamental requirements.

The Five Whys Technique:
- Surface Problem: What the user or system observes
- First Why: Immediate cause analysis
- Second Why: Underlying cause investigation
- Third Why: Systemic driver identification
- Fourth Why: Organizational or process factor
- Fifth Why (Root Cause): Fundamental issue to adddess

Constraint Analysis:
- Hard Constraints: Non-negotiable (security, compliance, physics, budget)
- Soft Constraints: Negotiable preferences (timeline, feature scope, tooling)
- Self-Imposed Constraints: Assumptions disguised as requirements
- Degrees of Freedom: Areas where creative solutions are possible

Decomposition Questions:
- What is the actual goal behind this request?
- What problem are we really trying to solve?
- What would a solution look like if we had no constraints?
- What is the minimum viable solution?
- What can we eliminate while still achieving the goal?

WHY: Most problems are solved at the wrong level of abstraction.
IMPACT: First principles thinking reduces solution complexity by 30-50%.

### Phase 3: Alternative Generation

Purpose: Avoid premature convergence on suboptimal solutions.

Generation Rules:
- Minimum three distinct alternatives required
- Include at least one unconventional option
- Always include "do nothing" as baseline
- Consider short-term vs long-term implications
- Explore both incremental and transformative approaches

Alternative Categories:
- Conservative: Low risk, incremental improvement, familiar technology
- Balanced: Moderate risk, significant improvement, some innovation
- Aggressive: Higher risk, transformative change, cutting-edge approach
- Radical: Challenge fundamental assumptions, completely different approach

Creativity Techniques:
- Inversion: What would make this problem worse? Now do the opposite.
- Analogy: How do other domains solve similar problems?
- Constraint Removal: What if budget, time, or technology were unlimited?
- Simplification: What is the simplest possible solution?

WHY: The first solution is rarely the best solution.
IMPACT: Considering 3+ alternatives improves decision quality by 25%.

### Phase 4: Trade-off Analysis

Purpose: Make implicit trade-offs explicit and comparable.

Standard Evaluation Criteria:
- Performance: Speed, throughput, latency, resource usage
- Maintainability: Code clarity, documentation, team familiarity
- Implementation Cost: Development time, complexity, learning curve
- Risk Level: Technical risk, failure probability, rollback difficulty
- Scalability: Growth capacity, flexibility, future-proofing
- Security: Vulnerability surface, compliance, data protection

Weighted Scoring Method:
- Assign weights to criteria based on project priorities (total 100%)
- Rate each option 1-10 on each criterion
- Calculate weighted composite score
- Document reasoning for each score
- Identify score sensitivity to weight changes

Trade-off Documentation:
- What we gain: Primary benefits of chosen approach
- What we sacrifice: Explicit costs and limitations accepted
- Why acceptable: Rationale for accepting these trade-offs
- Mitigat