architect-validate

To validate plan alignment with architectural decisions, run a read-only check against your repository to verify ADR coherence and detect gaps. This process examines cross-ADR consistency and data flows without modifying files.

Cross-ADR consistency checking verifies that architectural decisions do not conflict across components and data flows. It detects inconsistencies and plan gaps to ensure project plans remain aligned with the established architecture.

You can check for missing ADRs and plan gaps by applying pillar-based validation to your repository. This read-only process detects potential escalations and reports issues in either JSON or console output formats.

Yes, architectural validation supports both JSON and console outputs. This allows you to programmatically capture detected alignment issues and inconsistencies or review them directly in your terminal.

Yes, you can validate plans against team directives stored in repository memory. The validation process applies to ADRs kept in memory or drafts, ensuring plan-to-architecture coherence across all components.

Architectural plan validation is read-only to enforce safe checking that reports issues without modifying existing plans or ADRs. This prevents accidental changes to documented decisions during the consistency review.