review-architecture

To review compiler architecture, analyze cross-crate boundaries and subsystem layering to identify architectural drift. This process detects wrong-layer implementations and split-brain decision surfaces, producing a structured architecture report for governance.

Architectural drift is the degradation of intended subsystem layering across compiler and runtime boundaries. It manifests as duplicate policies, wrong-layer implementations, and split-brain decision surfaces that deviate from the original architectural design.

To enforce canonical registries during refactoring, perform an architecture pass that checks cross-crate boundaries for single-source-of-truth rules. This identifies duplicate policies and ensures shared semantics across subsystems.

You need an architecture pass for cross-crate reviews when executing broad refactors or when specifically asked to perform an architectural review. It verifies registry-driven behavior and compiler/runtime separation across touched subsystems.

Yes, you can check for split-brain decision surfaces by reviewing cross-crate boundaries for single-source-of-truth violations. The review identifies duplicate policies and wrong-layer implementations, outputting a structured findings report for planning.

The best way to identify wrong-layer implementations is to review touched subsystems for compiler and runtime separation. This architectural review detects boundary violations and registry consistency issues, generating an actionable architecture report.