liveBook · Manning

Architectural compliance

As explained in Vibe Engineering

The consistency of software components with a system's intended architecture, conventions, and integration boundaries.

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

How Vibe Engineering covers it

How deep it goes
Explains convention drift and seam failures through a concrete build-system incident, but stops short of prescribing a formal compliance process.
Examples
Uses generated components, project conventions, integration seams, and the NX publishing-rights compromise.
What you can do after
Diagnose integration risk by inspecting conventions, seams, surrounding system context, and operational permissions.
How it connects
Connects architectural compliance to technical debt, software architecture, build systems, and comprehensive verification.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.