The Architecture Crusade
DDD layer boundaries. The forge-temple's walls MUST hold against the Scrapcode.
/church:arch-crusade
"The fortress-monastery of clean architecture will hold — or we will REBUILD IT from the foundation stones, brick by consecrated brick."
— Battle Cry of the Tech-Priests
The Architecture Crusade enforces the sacred boundaries of Domain-Driven Design with the fanaticism of a Skitarii maniple defending a Forge World. Four specialist squads ensure that no layer violation, no circular dependency, no shadow contract pollutes the sanctified architecture.
How the Crusade Operates
The sacred operational sequence, as prescribed by the Fabricator-General.
Reconnaissance
The forge-temple's blueprints are analyzed by sacred cogitators.
Squad Deployment
Four specialized squads take positions at each architectural boundary.
Violation Detection
Every import, every dependency is traced and judged.
Severity Classification
Violations ranked from minor heresy to existential threat.
Fix Proposals
Each violation receives a prescribed remediation ritual.
Victory Report
The fortress-monastery stands pure. The Omnissiah is satisfied.
The Sacred Laws
The holy laws this crusade enforces. Break them and face the Omnissiah's wrath.
The Domain is PURE — it depends on NOTHING but the Machine God's fundamental types. No infrastructure, no framework, no external heresy shall touch it.
No Upward Dependencies. Lower layers shall NEVER reach upward. Infrastructure serves the domain, not the reverse. To violate this is to invert the sacred hierarchy.
No Circular Dependencies. If module A depends on B and B on A, the architecture has become a WARP LOOP — reality itself begins to unravel.
Domain modules shall be ISOLATED like reactor cores. Cross-contamination leads to meltdown.
No Shadow Contracts. Every interface must be explicit and blessed by the Fabricator-General.
The Holy Squad
The specialist Tech-Priest agents deployed during this crusade. Each carries only the doctrine they need.