Midday Border Update - June 8, 2026
Generated Jun 8, 12:00 PM PDT
- **san_ysidro** - **passenger_standard:** **130 min** (highest)
Full report available to subscribers
Get the complete Midday Update with inline charts, structured data, and analysis.
Login for full accessCommercial coverage
Cited border evidence with source policy for sales, operations, and agent workflows
Coverage options
4
Listed service
1
Custom quote
2
Planned
1
Recommended next step
Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.
Pricing
Laredo has a listed monthly service. Otay Mesa and Detroit/Windsor are available for custom quotes. Additional crossings remain in coverage planning.
Account setup
Account teams can activate delivery after scope, access, and billing are approved.
Delivery controls
Commercial delivery, account access, billing, alerts, and automated workflows require an approved account setup.
No delivery, alerts, or account keys are activated from public pages.
Laredo policy watch
2 MVE/USMCA dates tracked for Laredo operating context.
Market context
4 operating context families drawn from 268 reports.
Coverage detail
Laredo Border Pulse
commercial ready; listed price; $199/month; 14 facts.
Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.
Otay Mesa / San Diego planned coverage
custom review ready; not yet priced; 16 facts.
Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.
Otay Mesa custom coverage review
custom review available; custom quote; 16 facts.
Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.
Detroit / Windsor custom coverage review
custom review available; custom quote; 21 facts.
Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.
Why It Matters
Claim Policy
Cited report/packet claims only
Use cited packet/report evidence for claims; weather, road, policy, and map overlap stays contextual unless evidence proves causality.
Packet or replay citations must expose evidenceId, claimBearing, claimGuidance, evidenceMode, and source_ref claim policy.
Broad source-level claims also require sourceClaimAudit review, /v1/sources claimBearing=true, sourceFactHealth.total > 0, sourceFactHealth.claimBearingPolicyRows > 0, and no blocking claimWarnings for the source family.
Raw-current, raw-only, stale, no-row, scheduled, planned, future, retired, unknown, feed, search, and briefing source rows remain caveated context unless report citations explicitly review them.
Planned/future traffic rows must be labeled non-current planning context and not cited as current evidence.
Model Generation Policy
modelProvider/modelVersion: openai / gpt-5.4-nano
Lane: openai_content_optional
OpenAI content/report lanes require explicit gates and use store:false; no-call previews write local artifacts only.
Generated reports inherit cited report text, source facts, packet evidence, saved source_ref claim policy, and /v1/sources source-fact health.
Generated narrative may use only supplied data context, cited report text, cited packet evidence, or saved source_ref claim policy.
Broad source-level claims require /v1/sources claimBearing=true, sourceFactHealth.total > 0, and sourceFactHealth.claimBearingPolicyRows > 0.
Raw-current policy/map rows, no-row, stale, scheduled, planned, retired, inactive, future, and unknown rows are context only unless cited evidence explicitly says otherwise.
Do not assert causality from co-occurrence; say cause not identified in current feeds when context lacks causal evidence.
Persisted with report: yes