review/architecture

To verify architectural boundaries stay intact, run a design check that evaluates whether touched modules retain a single reason to change, preserve policy above detail, and maintain interface truthfulness across package boundaries.

Registry normalization ensures that interface registrations and runtime surfaces follow consistent mapping rules, preventing smeared kernel policy and maintaining clear separation between source, artifact, and installed package boundaries.

To check if a module has a single reason to change, apply architectural review checks that verify policy is not smeared across boundaries, interfaces remain truthful, and kernel responsibilities are distinctly separated from package tasks.

You need an architectural design check when changes affect package boundaries, registry normalization, kernel versus package responsibilities, or runtime surfaces, ensuring degraded-path visibility and fallback behavior remain testable.

The best way to review surface separation is applying checks that confirm clear boundaries between skills, commands, orchestrators, and providers, verifying that policy remains in the kernel and degraded paths are explicitly visible.

Code review fails on degraded-path visibility when fallback behavior is hidden or untestable, violating the architectural boundary check that requires degraded paths to remain explicitly visible across module runtime surfaces.