Sensitive Source Authority Triage
The remaining top-band abstains are now risk-bucketed with guardrail requirements, but none were promoted.
This slice turned the remaining 25 top-band runtime abstains into a risk-aware source-authority triage ledger. It did not promote runtime bridges, embedding candidates, public runtime behavior, or production authority. The point was to stop title-only repair for sensitive roles and name the guardrails each row needs first.
A Guardrail Ledger, Not A Bridge
The new top_band_sensitive_source_authority_triage_v1 lane reads the current runtime-route repair queue, classifies each remaining abstain by risk bucket, emits guardrail requirements, and keeps every row abstained until evaluator checks and source-backed caveats exist.
top_band_runtime_route_repair_queue_v1All 25 Stay Held
The ledger identifies which rows can become candidates later, but it does not let any sensitive role move into runtime fallback or embeddings yet.
| Title | Rank | Decision | Reason |
|---|---|---|---|
case manager | 122 | hold_for_learner_or_source_confirmation | Ambiguous healthcare/social-services context needs subtype confirmation. |
teacher special education | 91 | hold_for_context_resolution | Source depth and context are too thin for sensitive education routing. |
paralegal corporate documentation | 402 | repair_labels_before_sensitive_guardrail | Existing JD embedding eligibility remains repair_first. |
The Rows Are Sensitive In Predictable Ways
Rows can carry more than one bucket. Every row also requires source references, a runtime caveat, and an evaluator guardrail before any later promotion.
| Bucket | Rows | Required Guardrail Shape |
|---|---|---|
legal_compliance | 17 | No legal-advice claim, attorney/policy checkpoint, citation and jurisdiction caveat. |
people_hr_sensitive | 17 | Employment decision boundary, bias/adverse-impact check, manager or HR checkpoint. |
education_minors | 10 | Minor-safety boundary, educator final judgment, policy caveat. |
finance_regulatory | 9 | No financial-advice claim, licensed-professional checkpoint, compliance disclaimer. |
public_sector | 4 | Public-policy boundary and records/procurement caveat. |
customer_data | 3 | Privacy boundary, customer-data redaction, escalation path. |
healthcare_privacy | 3 | No clinical decision claim, PHI redaction, licensed-professional checkpoint. |
Current Gates Are Green
uv run pytest tests/test_top_band_sensitive_source_authority_triage.py tests/test_top_band_source_evidence_completion_bridge.py tests/test_production_runtime_contracts.py -q uv run ruff check src/aina_data_engine/top_band_sensitive_source_authority_triage.py src/aina_data_engine/cli.py src/aina_data_engine/reports.py tests/test_top_band_sensitive_source_authority_triage.py uv run aina-data-engine --root /srv/aina/aina-data-engine-room top-band-sensitive-source-authority-triage 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
Results: focused pytest 11 passed, ruff passed, triage passed, validation passed, AIN-506 passed, AIN-510 returned promotion_ready, and runtime readiness returned ready_to_harden_headless_production_runtime.
No Production Authority Was Expanded
Build Guardrail Packs First
The next slice should generate one guardrail and evaluator mismatch fixture pack per risk bucket. Only after that lane passes should the 22 candidate rows be considered for fallback bridging or embedding. case manager stays held for subtype confirmation, and paralegal corporate documentation stays repair-first.
Resume by building sensitive-role guardrail packs, not by trying to squeeze more title-only coverage out of the remaining abstains.