Measure architecture quality — a grade you can argue with
Every team has an opinion about its architecture; almost none has a measurement. So the argument runs on gut feeling — the loudest senior wins, the refactor gets deferred again, and “we have tech debt” stays a mood instead of a number that could go up or down.
prism0x2A turns the opinion into a measurement: a scan on your machine, scored against established architectural frameworks, compressed into a grade — with every step from finding to score to grade open for inspection.
One grade, fourteen perspectives
The GREEN layer synthesizes the structural scan (BLUE) and the capability map (AMBER) across 14 architectural frameworks — SOLID, Clean Architecture, Hexagonal and eleven more — into a single A–F coherence grade per repository. One number the whole team can see move.
The breakdown that shows the working
A grade you can't interrogate is a vibe with a letter on it. Every grade drills down to its per-framework scores, and every framework score drills down to the findings behind it — so an argument about the grade becomes an argument about specific code, which is the argument worth having.
The trend matters more than the number
A C+ codebase getting better every sprint is a healthier place than an A codebase quietly slipping. prism0x2A tracks the score over time and flags regressions — and shows the score delta at pull-request level, so you see what a change costs before it lands.
The honest part
A letter grade is a compressed opinion, and the frameworks it compresses genuinely disagree with each other — a hexagonal purist and a pragmatist will never score the same codebase alike, and no scan has seen your requirements. That is why the breakdown exists: the grade starts the conversation, the findings underneath decide it. The scoring method is published — recompute any number you don't believe.