Top-Band Runtime Route Coverage
A fast, rerunnable proof of how the current runtime contracts serve, abstain, or miss the top-band title cohort.
The engine room now has a top-band runtime route coverage lane. It checks the top 500/top 1,000 title band after JD-aware source-authority repair, without promoting public runtime or runtime embedding authority.
New Runtime Coverage Lane
Added top_band_runtime_route_coverage_v1, a local-only validation and reporting lane over the JD-aware top-band gap rows and promoted runtime contracts. It writes JSON, top 500/top 1,000 JSONL rows, and Markdown/HTML reports.
The role-context query code now exposes query_role_context_from_rows(), so bulk reports reuse one loaded contract set. The live command dropped from roughly 80 seconds to about 4 seconds on the VDS.
What The Current Top Band Says
| Metric | Value |
|---|---|
| Source top-band gap rows | 996 |
| Top 500 rows checked | 499 |
| Top 500 runtime matches | 486 |
| Top 500 guardrail/caveat routes | 16 |
| Top 1,000 rows checked | 996 |
| Top 1,000 runtime matches | 943 |
| Top 1,000 guardrail/caveat routes | 29 |
| Top 1,000 serve routes | 914 |
| Top 1,000 abstain routes | 29 |
| Top 1,000 not-found routes | 53 |
Interpretation: the top-band contract layer is mostly routeable today, but the missing and abstain rows are now explicit and measurable. They should feed the next source-authority/JD join repair slice instead of being hidden by title-only assumptions.
Commands That Passed
uv run pytest tests/test_role_context_query.py tests/test_top_band_runtime_route_coverage.py tests/test_role_context_runtime_fixtures.py -q uv run ruff check src/aina_data_engine/reports.py src/aina_data_engine/role_context_query.py src/aina_data_engine/top_band_runtime_route_coverage.py src/aina_data_engine/cli.py tests/test_top_band_runtime_route_coverage.py uv run aina-data-engine --root /srv/aina/aina-data-engine-room top-band-runtime-route-coverage --top-limit 1000 --top-500-limit 500 uv run aina-data-engine --root /srv/aina/aina-data-engine-room ain-506-p0-gate uv run aina-data-engine --root /srv/aina/aina-data-engine-room ain-510-retrieval-promotion-gate uv run aina-data-engine --root /srv/aina/aina-data-engine-room production-runtime-readiness uv run aina-data-engine --root /srv/aina/aina-data-engine-room validate
top_band_runtime_route_coverage_valid, top_band_runtime_route_coverage_has_runtime_matches, top_band_runtime_route_coverage_has_explicit_guardrails, and top_band_runtime_route_coverage_keeps_runtime_local.Repair What The Receipt Exposes
Use the 53 top-band not_found rows and 29 abstain rows as the next repair queue. Join those titles back to JD/company/industry/responsibility context and decide whether each should become serve, remain abstain, or stay unmapped with an explicit source-authority gap.
Start with the top-band route receipt, not title-only repair. The next useful work is shrinking explicit misses through JD-aware source context.