The Architecture Integrity Index is a 0-100 score of a codebase's structural health, computed as 100 minus the sum of entropy impacts from architectural findings. It is produced by VibeCop's detector agents, not a linter — it tracks how consistently new code follows a codebase's established patterns over time.
Each architectural finding deducts points from the index based on its severity: critical (P1) findings cost 5.0 points, high (P2) findings cost 2.5 points, medium (P3) findings cost 0.75 points, and low (P4) findings cost 0.1 points. Only architectural findings carry a weight — hygiene issues carry none.
| Severity | Entropy weight | Meaning |
|---|---|---|
| P1 — Critical | 5.0 | Blocks the pattern outright |
| P2 — High | 2.5 | Significant drift from established patterns |
| P3 — Medium | 0.75 | Minor inconsistency |
| P4 — Low | 0.1 | Cosmetic / low-impact drift |
VibeCop weighs four axes equally at 25% each: Pattern Coherence (similar problems solved the same way), Knowledge Reuse (logic reused rather than re-implemented), Abstraction Discipline (abstractions earning their weight, no hallucinated layers), and Architectural Complexity (cycles, fan-out, and coupling kept in check).
No. Security and complexity hygiene issues — dependency CVEs, exposed secrets, SAST findings, and infrastructure misconfigurations — are surfaced in a separate hygiene tray. They are real issues worth fixing, but they carry no entropy weight and never move the Architecture Integrity Index up or down.