arch-check

Architecture validation checks feature code against charter-defined rules for dependency layering, cycles, forbidden patterns, and file size. It reports structural drift as fitness violations with file and line context for human triage.

Architecture fitness validation enforces static analysis constraints to prevent AI-written feature code from drifting away from the charter's intended architecture. It turns machine-readable architecture rules into an objective, checkable gate before work is considered complete.

Run a post-implementation checkpoint audit using the charter's architecture manifest to check dependency layering and cycle detection. The audit enforces naming and size constraints, failing with fitness violations for human triage.

Architecture validation provides read-only reporting and does not auto-fix code. It surfaces forbidden patterns, dependency cycles, and layering violations with file and line context so developers can manually triage and resolve the issues.

Yes, architecture validation supports both targeted feature checks and full-project reviews using the charter's architecture manifest. Both modes enforce layering, cycle, forbidden pattern, naming, and size constraints through static analysis.

Run charter compliance checks during post-implementation checkpoint audits after completing feature code. The workflow enforces required handoff, branch hygiene, and progress breadcrumb steps so the architecture validation executes at the right pipeline stage.