Why
Third-party quality badges (e.g. Glama) nail someone else's ruler to our front door. BoJ-server currently scores License A / Maintenance B / Quality C on Glama — and the Quality C is driven almost entirely by fixable presentation (README rendering, version/count drift, catalogue-vs-live claims), not the design. Tellingly, Glama's own author was fascinated by BoJ but didn't think it warranted changing his framework — i.e. what makes BoJ significant sits outside the frame of a generic MCP scorer. A red-looking grade from a rubric that admits it can't see your value is noise, not signal.
We've removed the Glama grade badge from BoJ's README. This issue proposes the positive replacement.
What
An honest, adoptable readiness/insight badge framework — an outward-facing extension of the estate's existing CRG / *-readiness-grades work — that:
- Grades our own projects for continuous improvement — honest self-assessment with confidence ranges (measured vs estimated), not a vanity score.
- Evaluates other projects and other frameworks — including the evaluators themselves — on the axes generic scorers ignore.
- Surfaces the dimensions that matter but don't fit a generic rubric — the "this is significant; think about it" axes.
- Is adoptable by others — a badge other maintainers can "shove on theirs," backed by a shared, published criteria spec.
- Challenges evaluators: "consider this, because it is not insignificant."
Relation to existing work
Builds on component-readiness-grades, adoption-readiness-grades, foundations-readiness-grades, and CRG-SELF-ASSESSMENT.adoc already in this repo. This is CRG pointed outward and turned into a badge.
Right-sized first version (big soul, small finished body)
Do not build a cross-project evaluation engine first. In order:
- Write the criteria/axes spec — what we measure that generic scorers don't, and how honesty/ranges are expressed.
- A self-assessment badge for one repo (BoJ-server) generated from that spec — read-only, honest, on our own criteria.
- Only then generalise to evaluating other projects and frameworks.
Honesty principle
Report ranges; mark measured-vs-estimated. A badge that wears its confidence intervals out-credentials a single confident (often wrong) number. Honesty is the differentiator.
Motivation captured 2026-07-01, arising from the BoJ-server Glama experience.
Why
Third-party quality badges (e.g. Glama) nail someone else's ruler to our front door. BoJ-server currently scores License A / Maintenance B / Quality C on Glama — and the Quality C is driven almost entirely by fixable presentation (README rendering, version/count drift, catalogue-vs-live claims), not the design. Tellingly, Glama's own author was fascinated by BoJ but didn't think it warranted changing his framework — i.e. what makes BoJ significant sits outside the frame of a generic MCP scorer. A red-looking grade from a rubric that admits it can't see your value is noise, not signal.
We've removed the Glama grade badge from BoJ's README. This issue proposes the positive replacement.
What
An honest, adoptable readiness/insight badge framework — an outward-facing extension of the estate's existing CRG /
*-readiness-gradeswork — that:Relation to existing work
Builds on
component-readiness-grades,adoption-readiness-grades,foundations-readiness-grades, andCRG-SELF-ASSESSMENT.adocalready in this repo. This is CRG pointed outward and turned into a badge.Right-sized first version (big soul, small finished body)
Do not build a cross-project evaluation engine first. In order:
Honesty principle
Report ranges; mark measured-vs-estimated. A badge that wears its confidence intervals out-credentials a single confident (often wrong) number. Honesty is the differentiator.
Motivation captured 2026-07-01, arising from the BoJ-server Glama experience.