Custom coverage source review
Otay Mesa source review
Otay has CBP wait, anomaly, and weather context. For Otay, road-event context remains a disclosed gap: alternate source discovery found no usable machine-readable event endpoint, so private quote review must keep road claims closed unless the buyer accepts the gap. This page is package-review context only, not source currentness proof, customer delivery proof, or claim-bearing road-event evidence.
Otay custom review
Wait, anomaly, and weather context stay separated from road-event source gaps.
Status
alternate-source discovery profiled
Evidence facts
16
Access
custom quote
Service
custom review
Required disclosure
- - California/Baja road-event context not yet proven; alternate discovery found 0 usable machine-readable event endpoints
- - private package-review contract ready; commercial delivery still needs buyer approval
- - persistence closed
border-pulse:otay-mesa:road-gap-audit:2026-05-12T06-01Z
Readback-only claim boundary
Source-gap, no-row, parser-incomplete, and planned package rows stay non-claim-bearing. They do not prove source currentness, source quality, customer receipt, account entitlement, grant creation, delivery, settlement, source conditions, or causality. Claim-bearing source use still requires sourceClaimAudit review, /v1/sources claimBearing=true, sourceFactHealth.total > 0, sourceFactHealth.claimBearingPolicyRows > 0, parser-lag, future-row, embedding-backlog, degraded-run, no blocking claimWarnings, and cited packet/report evidence or saved source_ref claim policy gates.
Parser and write gates
Caltrans/511 evidence is still operator-review context. The connector probe proved fixture parser shape, but the bounded field profile did not expose usable parser text for Otay road-event claims. Source facts, source enablement, model calls, delivery, and persistence stay closed.
Parser proof
fixture shape proven
Source facts
false
Writes
false
Model calls
false
Field profile: 2 rows, 2 non-null values, wildcard fields false. Decision: caltrans_candidate_insufficient_for_otay_claims. Next action: Keep Otay road-event coverage disclosed as a gap; run a separate no-write alternate-source discovery profile before any source enablement.