This guide explains what the dashboard score is trying to mean.
The most important thing is this:
A score is useful only if people understand what reality it compresses.
What a Dashboard Score Should Represent¶
A useful score should reflect more than raw defects.
It should balance:
- code health;
- review risk;
- compliance posture;
- release readiness;
- context trustworthiness.
Why Methodology Matters More Now¶
With the new architecture, a project can have:
- decent code quality;
- weak session continuity;
- stale project memory;
- degraded retrieval behavior.
If the score ignores that, the number becomes misleading.
Good Scoring Principle¶
A good score should go down when:
- memory becomes stale;
- sync stays behind too long;
- release blockers appear;
- important findings accumulate;
- governance friction starts affecting real work.