module-designlisted

# Module Design Method ## Overview A unified design methodology: architectural principles (SRP / Unix / Atomicity / Isolation / Composability / Fractality / DRY) plus inversion navigation (necessary conditions, subtraction, constraint, kill criteria) plus the infrastructure triad (Config / Client / Storage) plus the module template (collapsed or expanded form). The central question: **"Without what does it fail?"** Decomposition runs from the TEP toward necessary conditions, not from a plan toward steps. ## Base hierarchy **Conceptual (always three levels):** System, Module, Stage, Operation. **Physical (expands by load):** collapsed form (stages as files) or expanded (stages as folders). Each level has its own TEP, a specific product required by the next link. ## Workflow Apply step by step. Do not skip Step 2. Inversion comes before decomposition, not after. ### Step 1, define the system TEP One sentence. A specific product, not a process. "Valuable" here is a technical term: value is defined by the need of the next link, not by judgment. Test: if you remove any single word from the wording, does it become ambiguous? If not, the TEP is blurry. ### Step 2, inversion (before decomposition) Apply three forms: 1. **Target:** "how to guarantee NOT getting the TEP?" 2. **Premortem:** "the project failed catastrophically. why?" Write the causes as if they already happened. 3. **Attribute:** flip a key property. What if you swap the flow / role / sequence? (TRIZ 13) F