Repair-First Semantic Bridge
A source-backed title repair moved from abstain to caveated local fallback, without promoting public runtime or embedding authority.
service delivery coordinator washington dc, into a caveated local runtime fallback. The original title stays as the runtime match key, service delivery coordinator is preserved as repair metadata, and the runtime decision remains fallback.
What Changed
The new semantic QA lane lives at /srv/aina/aina-data-engine-room/src/aina_data_engine/top_band_repair_first_semantic_qa.py. It checks ready repair-first rows for source-backed JD context, a changed cleaned title, no sensitive-policy tags, and responsibility snippets that actually support the repaired title.
| Artifact | Status | Metric |
|---|---|---|
top_band_repair_first_semantic_qa_v1.json | pass | 1 QA pass |
top_band_repair_first_semantic_qa_v1.jsonl | pass | 1 row |
top_band_repair_first_contract_bridge_v1.json | pass | 1 bridge row |
top_band_repair_first_contract_bridge_v1.jsonl | pass | 7 source-ref keys |
Runtime Effect
production_runtime_contracts_v1 now consumes the runtime bridge, abstain bridge, and repair-first bridge families. The new row is source-backed but still caveated, so route coverage improves without claiming full service authority.
Before
Top 500: 483 serve / 1 fallback / 15 abstain
Top 1,000: 944 serve / 25 fallback / 27 abstain
After
Top 500: 483 serve / 2 fallback / 14 abstain
Top 1,000: 944 serve / 26 fallback / 26 abstain
| Metric | Value |
|---|---|
| Runtime payload contracts | 1,030 |
| Role-resolution decisions | 1,030 |
| Combined top-band bridge rows | 26 |
| Repair-first bridge rows | 1 |
| Remaining repair queue | 26 rows |
Boundaries
No live Gemini call was made in this slice. No public runtime, real-user data, external writes, production telemetry, donor repo mutation, or runtime embedding authority promotion occurred.
human_review field or gate was introduced. The bridge is local-only and caveated.Verification
| Check | Result |
|---|---|
| Focused pytest | 8 passed |
| Ruff | pass |
| Validate | pass |
| AIN-506 gate | pass |
| AIN-510 gate | promotion_ready |
| Production runtime readiness | ready_to_harden_headless_production_runtime |
uv run pytest tests/test_top_band_repair_first_semantic_bridge.py tests/test_production_runtime_contracts.py -q uv run aina-data-engine --root /srv/aina/aina-data-engine-room validate 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
Resume Point
Next work should continue from the remaining 26 top-band route gaps. Start by inspecting /srv/aina/aina-data-engine-room/artifacts/validation/top_band_runtime_route_repair_queue_v1.jsonl.
cd /srv/aina/aina-data-engine-room git status --short --branch uv run aina-data-engine --root /srv/aina/aina-data-engine-room validate uv run aina-data-engine --root /srv/aina/aina-data-engine-room top-band-runtime-route-repair-queue --no-refresh-coverage
Start with source-authority-incomplete rows that have strong JD context and no sensitive policy hold; never bridge from title cleanup alone.