docs: add 哲学与方法论 module to README and project structure

i18n/en/documents/-01-philosophy-and-methodology/README.md

@@ -0,0 +1,99 @@
+# -01- Philosophy & Methodology: The Underlying Protocol of Vibe Coding
+
+> **"Code is a projection of thought; philosophy is the operating system of thought."**
+
+In the paradigm of Vibe Coding, we are no longer just "typists" but "architects of intention." This module transforms cross-disciplinary philosophical tools into executable engineering directives, aimed at eliminating cognitive friction in human-AI collaboration and enhancing the precision of intention delivery.
+
+---
+
+## Index
+
+1. [Perception & Definition: Seeing the Truth](#1-perception--definition-seeing-the-truth)
+2. [Logic & Refinement: Deep Reasoning](#2-logic--refinement-deep-reasoning)
+3. [Verification & Correction: Countering Hallucinations](#3-verification--correction-countering-hallucinations)
+4. [Systems & Evolution: Global Decision Making](#4-systems--evolution-global-decision-making)
+5. [Frontier Cognitive Tools: Formalization & Computation](#5-frontier-cognitive-tools-formalization--computation)
+
+---
+
+## 1. Perception & Definition: Seeing the Truth
+*Goal: Eliminate subjective bias and linguistic ambiguity before prompting.*
+
+### Phenomenological Reduction
+*   **Method**: **Epoche (Suspension of Judgment)**. Describe "what is actually happening" rather than "what should happen."
+*   **Vibe App**: When describing bugs, provide raw logs and observed outputs; avoid injecting "I think it's this function" biases.
+
+### Hermeneutics
+*   **Method**: **Hermeneutic Circle**. Understand the part through the whole and the whole through the part.
+*   **Vibe App**: Ask the model to restate requirements and list ambiguities before writing code.
+
+### Steelmanning
+*   **Method**: Addressing the strongest possible version of an opponent's argument.
+*   **Vibe App**: In refactoring, ask: "Prove why my current solution is reasonable first, then propose a new one that surpasses it."
+
+---
+
+## 2. Logic & Refinement: Deep Reasoning
+*Goal: Elevate the model's thinking depth towards optimal rather than just feasible solutions.*
+
+### Socratic Questioning
+*   **Method**: Continuous inquiry. Why? What's the evidence? What's the counterexample?
+*   **Vibe App**: Use 5 layers of "Why" for model solutions, focusing on performance, edge cases, and graceful degradation.
+
+### Occam's Razor
+*   **Method**: Entia non sunt multiplicanda praeter necessitatem (Entities should not be multiplied beyond necessity).
+*   **Vibe App**: Demand the model to "remove 30% complexity while keeping core requirements," favoring stateless designs.
+
+### Bayesian Epistemology
+*   **Method**: Dynamically updating beliefs based on new evidence.
+*   **Vibe App**: Treat error logs as "new evidence" to update the prompt strategy via conditionalization, rather than repeating the same path.
+
+---
+
+## 3. Verification & Correction: Countering Hallucinations
+*Goal: Establish scientific feedback loops to ensure code determinism.*
+
+### Popperian Falsifiability
+*   **Method**: A theory that is not falsifiable is not scientific.
+*   **Vibe App**: Every "seemingly correct" code must have a test case that could prove it wrong. Shift from "I think it's right" to "I haven't falsified it yet."
+
+### Counterfactual Thinking
+*   **Method**: Ask "What if X were not the case?"
+*   **Vibe App**: Build test matrices: What if the network times out? What if the disk is full? What if API returns are out of order?
+
+### Experimental Philosophy (x-phi)
+*   **Method**: Using data to test intuitions.
+*   **Vibe App**: Don't argue over which API is better; generate A/B test scripts and let the benchmark data decide.
+
+---
+
+## 4. Systems & Evolution: Global Decision Making
+*Goal: Maintain elegance in complex engineering, balancing speed and quality.*
+
+### Systems Thinking / Holism
+*   **Method**: Focus on boundaries, feedback, and coupling.
+*   **Vibe App**: Visualize data flows and dependency graphs to decouple high-risk points and shorten feedback loops.
+
+### Dialectical Contradiction Analysis
+*   **Method**: Identify and resolve the primary contradiction.
+*   **Vibe App**: When stuck, analyze if it's "unclear requirements," "unstable APIs," or "slow feedback." Resolve the core bottleneck first.
+
+### Pragmatism
+*   **Method**: Truth is defined by its utility and effect.
+*   **Vibe App**: Define quantifiable metrics (P95 latency, cost, delivery time). Optimize one metric per iteration.
+
+### Decision Theory
+*   **Method**: Distinguish between reversible and irreversible decisions.
+*   **Vibe App**: Label modifications as "fragile" or "foundational." Prioritize high-value, reversible actions (MVP).
+
+---
+
+## 5. Frontier Cognitive Tools: Formalization & Computation
+
+*   **Formal Methods**: Using math and modal logic to make epistemological problems computable and cumulative.
+*   **Computational Philosophy**: Using simulations and agent models to turn mental models into runnable experiments.
+*   **Reflective Equilibrium**: Iteratively calibrating specific judgments and general principles for systemic consistency.
+*   **Conceptual Engineering**: Actively engineering and optimizing conceptual tools to serve Vibe Coding practices.
+
+---
+*Note: This content evolves continuously as the supreme ideological directive of the Vibe Coding CN project.*

i18n/en/documents/README.md

@@ -8,6 +8,7 @@
 
 ```
 documents/
+├── -01-philosophy-and-methodology/ # Supreme ideological directive
 ├── 00-fundamentals/         # Core concepts & principles
 │   ├── Glue Coding.md
 │   ├── Language Layer Elements.md
@@ -47,6 +48,10 @@ documents/
 
 ## 🗂️ Categories
 
+### -01-philosophy-and-methodology
+Supreme ideological directive and epistemological tools:
+- **Philosophy & Methodology** - The underlying protocol of Vibe Coding
+
 ### 00-fundamentals
 Core concepts and methodology:
 - **Glue Coding** - Revolutionary programming paradigm