CONSISTENCY
Lowercase or leave
Files, classes, and controllers use lowercase naming. Filesystem sanity matters more than creative capitalization.
The Chaos MVC Manifesto
Architecture Without the Shadows
Clear execution. Visible structure. A framework that expects developers to understand and own the systems they build.
01 — Ownership
Stop fighting the framework.
Modern development too often buries straightforward logic beneath layers of abstraction and bloat. Chaos MVC takes the opposite approach. It is built for developers who want to understand their stack, trace its behavior, and remain responsible for the application they ship.
The framework supports your work. It does not ask you to surrender your judgment to it.
02 — Transparency
We don’t hide the wires.
Transparency is an architectural requirement, not a slogan. From the Example Module to the Developer Portal, Chaos MVC exposes the structure developers need to understand how the system operates.
Request → Controller → Model → View → Response
A predictable execution path in which every step can be located, read, and traced.
03 — Discipline
Discipline is your freedom.
Clear rules prevent the framework from decaying into a collection of exceptions.
TRACEABILITY
Annotation protocol
AI-assisted changes are marked. Core changes are signed. The history of a decision remains visible in the code it affected.
FOCUS
Zero bloat
If a capability is not essential to the framework, it stays out of Core and belongs in an optional module or project-specific code.
04 — Determinism
No magic. No nonsense.
Chaos MVC does not depend on telemetry, hidden tracking, or automatic behavior that conceals the state of your application. Important operations should be explicit, inspectable, and based on the real condition of the system.
We would rather diagnose and harden a schema deliberately than trust automation that cannot explain what it changed or why.
05 — Craft
Competency is the watchword.
Chaos MVC is for developers who respect the craft enough to keep their work precise. The framework provides a clear architecture; the developer brings the judgment and skill required to use it well.
The goal is an ecosystem in which code is readable, execution is predictable, and developers can confidently explain the systems they maintain.