Architectural compliance means fitting components into the system that already exists: its conventions, established patterns, build assumptions, and integration boundaries. A component can pass its own tests yet become a perfect puzzle piece for the wrong puzzle. section 1.6
Check compliance where components meet the surrounding system:
- Compare generated code with project conventions and established implementation patterns. section 1.6
- Inspect seams between components rather than trusting isolated unit-test success. section 1.6
- Evaluate build-system permissions and publishing consequences before accepting locally reasonable changes. section 1.6
The wrong puzzle piece
The NX compromise entered through an integration seam: code that appeared reasonable in isolation became catastrophic because it operated inside a build system with publishing rights. section 1.6
