arch-compliance

Architecture compliance verification audits implementation against documentation by classifying feature reality as REAL, PARTIAL, STUB, MISSING, or FACADE. It pinpoints broken wiring and missing code, actively implements remaining gaps, and reports honest coverage metrics to prevent overclaiming.

Distinguishing real features from stubs or facades involves a truthfulness audit that evaluates actual implementation status against documented plans. This classification categorizes features into REAL, PARTIAL, STUB, MISSING, or FACADE states, ensuring passing tests on non-functional features do not inflate coverage.

Closing architecture gaps requires a full-cycle compliance audit that identifies missing code and broken wiring, then actively implements the remaining in-scope features. It adds corresponding tests to verify the new implementation and reports honest coverage metrics for release readiness.

Honest coverage reporting provides clear metrics on feature completion and test effectiveness by factoring in the actual implementation status. It prevents overclaiming by ensuring that passing tests on STUB or FACADE features do not inflate the reported coverage of genuinely MISSING or PARTIAL functionality.

Architecture compliance auditing suits release readiness checks by confirming that all features planned for a development phase are genuinely implemented and tested. It verifies implementation against documentation, ensuring no planned functionality remains partially wired or missing before a release.

Test coverage reports show high scores with missing features when tests pass on STUB or FACADE implementations. An architecture compliance audit identifies this by classifying feature reality and reporting honest coverage metrics that reflect actual implementation status rather than inflated test pass rates.