Evidence map
Generated evidence boundary. This page is generated from the checked-in selection, review, source-lock, promotion, and cohort manifests. It does not run Bifrost and it does not copy provisional scores.
The shortest honest answer is currently the published real-project-v1 result: its historical v0.2.0 page reports the measured Bifrost/reference comparison. Published result status is derived from the immutable bundles supplied to this generation run; no score is copied into this evidence map.
Evidence breadth
Section titled “Evidence breadth”| Slice | Frozen identity | Selection and review tier | Frozen denominator | Result publication |
|---|---|---|---|---|
| Prospective v1 | real- · v0.2.0 | prospective_ · human_ | 36 cases (12 per profile) | Historical release; current v1 result |
| Prospective v2 | real- · v0.3.4 | prospective_ · human_ | 36 cases (12 per profile) | Immutable release v0.3.4; generated report provenance is recorded below |
| Reviewed legacy core | legacy- · v0.3.1 | retrospectively_ · legacy_ | 110 cases (10 × 11 languages) | Immutable release v0.3.1; generated report provenance is recorded below |
The denominators above are not interchangeable. In particular, v1 and v2 are prospective source-only selections, while the legacy core is a separately frozen retrospective promotion of analyzer-informed development cases. A later report may present a documented stratified aggregate, but it may not flatten these trust tiers into one accuracy score.
Prospective profile denominators
Section titled “Prospective profile denominators”Each profile remains visible before any aggregate. The numbers here are selected-case counts, not analyzer outcomes.
| Slice | Language | Candidate/ | Repositories | Cases |
|---|---|---|---|---|
| v1 | go | gopls | 4 | 12 |
| v1 | python | pyright | 4 | 12 |
| v1 | typescript | typescript- | 4 | 12 |
| v2 | java | eclipse-jdtls | 4 | 12 |
| v2 | rust | rust-analyzer | 4 | 12 |
| v2 | cpp | apple- | 4 | 12 |
Reviewed legacy boundaries
Section titled “Reviewed legacy boundaries”The immutable promotion is legacy-promotion-v1-balanced-core. Its balanced core is 110 cases, with 42 overflow candidates and 6 controls kept outside the correctness denominator. The source-only legacy inventory contains 158 cases.
| Language | Balanced-core cases |
|---|---|
| cpp | 10 |
| csharp | 10 |
| go | 10 |
| java | 10 |
| javascript | 10 |
| php | 10 |
| python | 10 |
| ruby | 10 |
| rust | 10 |
| scala | 10 |
| typescript | 10 |
Immutable report provenance
Section titled “Immutable report provenance”The entries below are derived only from checksum-verified release bundles. The generated result pages remain the score authority; this index records their exact release, snapshot, manifest, and report identities without retyping score totals.
| Slice | Release | Revision | Freeze manifest SHA-256 | Report artifacts |
|---|---|---|---|---|
| v1 | v0.2.0 | 6ea6056fa6b3eb | 3258e3269c98baa9 | bifrost 702a73c97d86a4c9, gopls 679796a7a8f3d5b5, pyright c6899baca9154f46, typescript- 8dda75467e0bd249 |
| v2 | v0.3.4 | e9ffdf26a2a216 | c6eece246a748d21 | apple- 2e8167d21745617e, bifrost 0341a8f8aee26d5f, eclipse-jdtls b0b41090ff1d6f1f, rust-analyzer b039a8be30056835 |
| legacy | v0.3.1 | 8393dafe6b9af6 | 6c64323d6c3289ab | apple- fe15d95580e5837f, bifrost 593cc3580d5a8e97, eclipse-jdtls c6367a23bc6d1d65, gopls f3abe0cd3abf4d82, intelephense 29669d93db3f097a, metals ea522be8abfc92fd, pyright 33f89e7f54252bcd, roslyn 16b7815b9cd48227, ruby-lsp 027c6761459f6032, rust-analyzer 1c0ba625f2a3ae8d, typescript- 2919729c212746b9 |
Remaining development evidence
Section titled “Remaining development evidence”The checked-in development corpus contains 158 cases. The reviewed legacy core accounts for 110; the 48 cases outside that core comprise 42 frozen overflow candidates and 6 unsupported/not-planned controls. This remainder is retained for regression and diagnosis; it is not silently added to v1, v2, or the legacy denominator.
Publication safeguards
Section titled “Publication safeguards”- Prospective v1 and v2 keep separate profile/language denominators; v2 permits only documented stratified aggregation.
- The legacy manifest records
retrospectively_selected,legacy_promoted,source_only, andanalyzerOutcomeUse: forbidden; re-review cannot make the source contract preregistered. - Controls and overflow remain explicit partitions and cannot enter the balanced-core score.
- Score tables must be generated from a checksum-verified immutable report artifact bound to the matching manifest. This page records published provenance when such a bundle is supplied and otherwise reports readiness, never guessed scores.
Manifest provenance is machine-readable in docs/src/data/evidence.json and is checked in CI with scripts/generate-docs-evidence.py --check. See the current v1 result, the historical development result, and the human ground-truth audit for retained historical evidence.