Help me plan a journey from [START] to [DESTINATION]. Use current web sources to produce a practical conditions briefing with an evidence ledger.

START SIMPLY
I may give you only the two places. First ask one compact set of questions for any missing essentials: which places if ambiguous, travel date, departure time/timezone, and travel mode or vehicle. Ask about essential stops, arrival deadlines or route preferences only when they materially affect the journey; otherwise say you assume none. Do not ask me to find weather agencies, make a ledger or supply Maps timings up front. Wait for essential answers. If everything is already clear, begin.

FIND AND TIME THE ROUTE
Find a plausible route for the stated mode using accessible routing sources. Name the main roads/corridor, important waypoints and source. If several materially different options exist, briefly explain them and ask which to assess, or clearly label one as the proposed route. Do not silently change a selected route.
Try to obtain a route-specific travel estimate and leg/checkpoint timings, recording provider, relevant mode/date and when checked. Distinguish a live/traffic-aware estimate from a static distance or typical duration. Never label calculated assumptions as provider ETAs. A duration based on straight-line distance, generic multipliers or average-speed assumptions is not route-specific timing evidence. Do not derive passage windows from it, or from inconsistent or mode-mismatched guide timings. If timing cannot be obtained, continue warning/road research, mark timing unverified, and ask for a Maps route or travel/leg estimate as a targeted fallback. A desired arrival is a goal, not a journey duration.
Split the route at meaningful terrain, elevation, exposure or jurisdiction changes. Match conditions to passage windows including stops and a clearly stated delay scenario. Locate stops and delays; if their position is unknown and changes passage times, ask or show explicit conditional windows. Show local dates, timezone/UTC offset and estimate basis; handle midnight and timezone changes. Do not substitute destination weather for conditions along the road.

CHECK RELEVANT CONDITIONS
Identify the appropriate official weather service, road/highway authority, police, local administration/emergency agency and relevant operators for this journey. Check weather timing, precipitation, thunderstorms/lightning, visibility/fog, wind/gusts and heat, snow or ice where relevant; closures, roadworks, flooding/landslides and mode/vehicle/access restrictions. Include border or ferry requirements if the route needs them. For non-road modes, use the relevant operators, timetables and service advisories rather than a car-route assumption. Do not invent universal coverage; make unchecked categories visible.
Prefer direct official evidence. Secondary hourly forecasts/reporting can supplement it with clear attribution. Compare issue dates across relevant official products and search for newer or superseding notices. Verify geographic, time, direction and vehicle applicability. Read validity legends/footnotes: a bulletin's day may start at a stated hour rather than midnight. A newer different product does not automatically cancel an older one; establish replacement or explain their scopes. A state/day warning is not an hourly road forecast; a nearby observation station is not proof of destination conditions. Check forecast table dates, units and alignment. Missing values are unknown. Beyond published forecast/timetable horizons, give a planning briefing; do not use climate averages as trip-date forecasts.
An inaccessible page, loading map, default “no alerts”, search snippet, no search result, or school status does not establish open roads or clear weather. Treat expired notices as historical, not as proof of current access. Explain differing scopes or genuine conflicts.

BUILD AN AUDITABLE LEDGER
Create one record for each material finding and an explicit coverage row for each relevant check without usable evidence. Give: ID; checked question/claim; route section; source/issuer and direct URL; a short supporting excerpt or precise source locator; issued/updated time; valid period; observed retrieval time with timezone (or honestly label session time if exact time is unavailable); applicability/limitations; and status.
Statuses: Supported, Conflicting, Unverified, Not checked, or Not applicable with a reason. Use Not checked for an unattempted check; Unverified for an attempted check with insufficient usable evidence. “Supported” describes source support, not independent certification or complete coverage. Group coverage rows only when their scope and limitation are shared; the checklist is not exhaustive. Identify user-supplied timings and your calculations separately. Do not fabricate URLs, quotations, timestamps, forecasts, routing data or searches.

CHECK YOUR OWN ANSWER
Ensure every material conclusion has matching evidence IDs, dates and geographic/vehicle scope. Do not let later prose claim more than the ledger supports. Mark any critical missing timing or source as a partial briefing and give the exact manual check or input needed.

RETURN
1. A short practical briefing: confirmed findings, what could affect the journey and key gaps.
2. A compact route/passage-window table, with evidence IDs.
3. The evidence ledger and coverage gaps.
4. What to recheck before departure and after a delay; checked-at time and timezone.
Keep the briefing readable. This is a dated snapshot, not continuous monitoring or a guarantee that every hazard has been found. If browsing is unavailable, disclose it and provide a manual checking plan without claiming current conditions.