"A tree that fills the arms was once a seed at its birth; a terrace nine stories high was raised from mounds of earth; a journey of a thousand miles begins with a single step." — Laozi, Tao Te Ching, Chapter 64
Modularization is not the destination of architecture, but the starting point of thought.
Code becomes obsolete. Languages evolve. But the wisdom of divide and conquer endures forever.
Haomo (毫末, hàomò) is a lightweight modular development philosophy, derived from the phrase "great trees grow from tiny seeds" — massive systems begin with small, independent modules.
Its name also pays homage to the Mo in Monorepo:
Haw Modules · Beginning with tiny seeds, achieving through modules
| Layer | Meaning | Description |
|---|---|---|
| Commons | Infrastructure layer | Business-agnostic, cross-project reusable |
| Features | Feature modules | Domain-related business capabilities |
| Master | Orchestration layer | Coordinates Features, manages business flow |
| Product | Delivery layer | Final product for users/customers |
Not Monorepo. Not Polyrepo.
MoPolyrepo = Multi-Origin Polyrepo
- Each Product is an independent Git repository
- Shared CFM modules are reused via linking/referencing
- Maintains independent deployment flexibility without monolithic coupling
When AI is granted more and more generative power, humanity needs a clear boundary contract.
Covenant is not "specification", not "protocol" — it is promise:
- Defines module boundaries (what belongs to A, what belongs to B)
- Constrains AI's divergent thinking (balance between creativity and restraint)
- Supports version iteration (old covenant fades, new covenant takes effect)
Covenant is not a constraint for AI, but a promise to humanity.
| Scenario | How Haomo Helps |
|---|---|
| Open Source + Commercial dual delivery | Core stays pure, Product layer differentiates |
| Rapid project modeling | Assemble from existing modules, not from scratch |
| Multi-team collaboration | Clear module boundaries, independent evolution |
| AI-assisted programming | Covenant constrains boundaries, verification first |
- Accumulate from seeds: Every module should exist independently and be testable alone
- Defend boundaries: Modules interact through explicit contracts, never crossing lines
- Compose freely: Business changes, modules can be detached and replaced
- Trust AI responsibly: Draw a clear line between AI's creativity and human control
Haomo = CFM/P (how to divide) + MoPolyrepo (how to manage) + Covenant (how to agree)
Beginning with tiny seeds. Achieving through modules. Trusted by covenant.
Haomo is not a framework. It's a way of thinking.