-
Notifications
You must be signed in to change notification settings - Fork 4.4k
14 Maturity Framework
The Maturity Framework is a set of five RFCs that define how ZeroClaw is built and maintained — not just what the code looks like, but how the team works, what the pipeline guarantees, and how documentation stays useful as the project scales.
The five RFCs are designed to be read as a whole. Each one stands on its own, but they reference each other because the decisions they describe are connected: governance without CI is wishful thinking, CI without documentation is a black box, documentation without architecture drifts into fiction, and none of it survives without a contribution culture that can sustain it.
| # | Page | Scope | Source |
|---|---|---|---|
| 14.1 | Intentional Architecture | What ZeroClaw is and how its microkernel is structured. Establishes the principle that dependencies flow inward, and structure is enforced by the compiler. | #5574 |
| 14.2 | Documentation Standards | How the project documents what it builds — classification, the repo/wiki split, ADRs, i18n strategy, and the replacement docs-contract. |
#5576 |
| 14.3 | Project Governance | The lightweight scaffolding for team coordination: GitHub Projects, Discussions, tier-based authority, CODEOWNERS, the RFC loop, and label taxonomy. | #5577 |
| 14.4 | Engineering Infrastructure | The target CI/CD pipeline, security scanning as a lifecycle, and release automation aligned to the distribution model. | #5579 |
| 14.5 | Contribution Culture | How humans and AI collaborate on this project — feedback, ownership, responsible tool use, and team growth. | #5615 |
If you are new to the project, read them in order (14.1 → 14.5). Each RFC assumes context from the ones before it.
If you are looking for a specific decision, jump straight to the relevant page. Each RFC includes its own table of contents, revision history, and discussion questions.
If you want to participate in shaping these decisions, the canonical discussion thread for each RFC is on the linked GitHub issue. The wiki pages are mirrors for long-form reference; comments and proposals belong on the issues.