# Example brief: a clear crossing decision

DIGITO-authored practice brief, version 0.1, October 25, 2026. This is not a model response or evidence of audience testing.

Audience: someone unfamiliar with BorderPulse who is comparing nearby El Paso–Juárez crossings.
Decision: compare reported waits for the same lane without mistaking the shortest queue for the shortest whole trip.
First output: a local six-scene HTML story with Previous/Next controls and a complete text alternative.

## Approved reference material

- Recorded screens and implemented case: https://digito.technology/projects/borderpulse
- Interface reasoning: https://digito.technology/insights/designing-decisions-imperfect-data
- Use the full-size comparison and history capture links on the case. Capture date: October 24, 2026 UTC. The screenshot interface is English; report/fetch clocks can be older. Historical patterns are not forecasts.

## Six-scene direction

1. Introduce the traveler's crossing question.
2. Explain why lane type makes a comparison meaningful.
3. Show the actual recorded comparison.
4. Distinguish closed lanes from missing reports.
5. Keep report age, extra driving and the limits of history visible.
6. Lead to the actual case or product without inventing an outcome.

No invented UI, refreshed numbers, customer claims, conversion metrics or implied time savings. Do not publish from this brief. Inspect each image you use; if you cannot open it, say visual verification is pending.