Engineering factory / code generation
SPAZ / SpazOut
Make repeated engineering structure consistent.
SPAZ / SpazOut automates supported code-generation operations. Retained components include typed entity-to-view-model projections and request-to-command/query mappings. Ownership markers and manual overrides help distinguish generated structure from human-owned behavior.
WHERE IT HELPS
Start with the work you want to improve.
- Reduce repeated architecture wiring
- Generate supported typed mappings
- Preserve the distinction between generated and handwritten code
HOW IT CONNECTS
A clear responsibility.
A place in the bigger picture.
SPAZ works within the broader factory direction alongside DNF, the scaffolders, and ABCSHARP utilities. The generated code still has to compile and satisfy the application’s checks.
IMPLEMENTATION STATUS & EVIDENCEActive development
What the source record shows
The retained SpazOut README documents ExplicitMappingGeneration, generated ownership tags, component replay, and limits of the current CLI safety/acceptance surface.
Read the relevant experiment notes ↗Current scope
The current notes distinguish mapping/component checks from a complete CLI and factory acceptance pass. The broader rewrite specification describes planned work.
Current availability and integration fit are established in a walkthrough of the implementation.
A PRACTICAL NEXT STEP