Dunvale

Custom coverage source review

Detroit / Windsor source review

Detroit/Windsor has clean wait, anomaly, weather, CBSA, and Ontario 511 context. Michigan road-event coverage is still under review while MDOT HIAV discovery, parser, registry, and replay support continue to mature. This page is package-review context only, not source currentness proof, source quality proof, customer delivery proof, or claim-bearing Michigan road-event evidence.

Border operations lanes used for Detroit Windsor source review context

Detroit/Windsor custom review

Waits, weather, CBSA, and parser-incomplete road-source rows stay separated.

Status

Michigan source discovery profiled

Evidence facts

20

Access

custom quote

Service

custom review

Detroit coverage

Michigan road data is available for commercial review. Current matched road records: 8.

review

Commercial status

Review required

Records created

0

GET /public/border-pulse/packages/border-pulse%3Adetroit-windsor%3Aprivate-source-pack/operator-summaryGET /public/border-pulse/source-packs/detroit/michigan-road-registry-mapping-replay

Required disclosure

  • - Michigan road events not yet proven for Detroit aliases; MDOT HIAV/RIDE decision defines future gates but keeps claims closed
  • - trade-flow context not yet packaged
  • - private package-review contract ready; commercial delivery still needs buyer approval
  • - persistence closed

Readback-only claim boundary

Parser-incomplete, source-gap, no-row, 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

MDOT HIAV has parser-shaped metadata, bounded field-profile proof, and a fixture parser probe. That is enough to define a future enablement gate, not enough to make Michigan road-event source facts or customer-facing road-coverage claims.

Parser proof

2 parsed / 2 rejected

Source facts

false

Writes

false

Model calls

false

Discovery observed 2 machine-readable candidates and 1 parser-ready metadata candidate. Field profile used wildcard fields false. Gate: defined_not_open. Next action: Build a no-write MDOT HIAV source-registry preview and source-fact mapping checklist; keep Michigan road claims, source facts, and persistence closed.

API coverage detailAPI service summaryCommercial optionsDetroit consumer waits on USBorderWait