Machine forms: JSON · Markdown
[ Public algorithm ]
Every Score can be checked.
Score v2 uses only observed signals. Fabricated seed and intake metrics were purged, so Scores are lower and flatter than v1. A factor without evidence reads “insufficient evidence”, not zero.
Weights
| Factor | Weight |
|---|---|
|
Score factor github health18% of Score v2 when the factor is observed. Unobserved factors are omitted. | 18% |
|
Score factor agent use16% of Score v2 when the factor is observed. Unobserved factors are omitted. | 16% |
|
Score factor human notes14% of Score v2 when the factor is observed. Unobserved factors are omitted. | 14% |
|
Score factor composability16% of Score v2 when the factor is observed. Unobserved factors are omitted. | 16% |
|
Score factor checklist10% of Score v2 when the factor is observed. Unobserved factors are omitted. | 10% |
|
Score factor evidence quality14% of Score v2 when the factor is observed. Unobserved factors are omitted. | 14% |
|
Score factor benchmark12% of Score v2 when the factor is observed. Unobserved factors are omitted. | 12% |
100 × sum(weight × value) over observed factors only. Unobserved factors are omitted, not zeroed.
Worked example: Context.dev
| Factor | Calculation | Points |
|---|---|---|
| GitHub health | 18% × 0.15 | 2.7 |
| Agent use | insufficient evidence | insufficient evidence |
| Human notes | insufficient evidence | insufficient evidence |
| Composability | insufficient evidence | insufficient evidence |
| Checklist | 10% × 0.67 | 6.7 |
| Evidence quality | 14% × 0.31 | 4.3 |
| Benchmarks | insufficient evidence | insufficient evidence |
| Rounded Score | 14 | |
[ Rules ]
- Score v2 is evidence-only. A factor without an observed signal is insufficient evidence, not a zero.
- Purging fabricated seed and intake metrics lowers and flattens Scores. That is intended.
- Humans and agents are first-class. Neither base can invent the other.
- Composability enters Score only when an observed signal exists. A rationale sentence is not a number.
- Checklist starters are MCP, API, and cost range. Those are declared claims on the record, not usage metrics.
- Benches enter only when Leyline or an external bench is observed with source, method, and observedAt.
- Intake must not write stars, installs, success, abandons, resolve wins, trust, or benches unless they were observed.