review-community-standard-componentization-wiring-knowledge

To verify public exports are not orphaned, check that each new export has at least one production caller, explicitly excluding tests, barrels, and bin entries from the static caller count. This confirms the export is used in production wiring.

The wiring triad for componentization is a canonical standard requiring static caller presence, integration tests against real boundaries, and declared runtime metrics to ensure robust and auditable codebase wiring.

Check for integration tests and runtime metrics by guiding evidence collection to confirm new public exports are tested against real boundaries and explicitly declare runtime metrics for monitoring during the re-validation process.

Yes, you can defer wiring requirements by following canonical patterns for dead-wiring or ADR-based deferrals, allowing exceptions to the static caller, integration test, and metric mandates when appropriately documented.

You need to run a wiring review when validating canonical definitions and verifying wiring discipline across a codebase, specifically during re-validation to ensure new public exports satisfy the static caller, integration test, and metric requirements.