architecture-audit

An architecture audit evaluates system health and produces spinoff-ready findings while enforcing non-inline edits, ensuring your codebase governance review remains completely code-free. It orchestrates reviewer analysis to identify structural issues safely.

Rotational target selection picks the highest-priority system for an architectural audit using staleness, criticality, open items, and roadmap-activity signals. This weighting ensures ongoing system health monitoring focuses on the most needy codebase.

You prioritize audits by applying health-ledger and roadmap-activity weighting to evaluate system staleness and criticality. This dependency analysis identifies the highest-priority system for targeted rotational audits based on open items.

Yes, you need jq installed because it is a required dependency for parsing atlas metadata and health-ledger data during the architecture audit. This command-line JSON processor enables the review orchestration logic.

Yes, you can run a targeted re-audit by providing a specific system as an argument, which overrides the rotational targeting. This updates the Last targeted audit clock while preserving the Last full audit timestamp.

The best way is converting audit findings into a disposition ladder: immediate executor for trivial non-structural items, PM-gated spinoff candidates for structural work, or escalation to planning. This packaging keeps the architectural review code-free.