Data & measurement
Logistics, history, and saved briefs
Review priority, retained report history, operational information gaps, and private cloud captures.
A useful logistics brief makes missing information visible. Report volume and an absence of reports cannot establish that a route is safe.
Rank the need for review
Place cards are ordered first by confirmed safety-watch claims, then corroborated claims, conflicting or reported safety claims, road/access claims, and recency. The safety-watch group includes security, emergency, fire, flooding, protests, and accidents. These category and evidence labels describe the records; they are not an independent risk assessment.
Resolved and disputed claims do not count as active supported conditions. Disputes remain visible because they need review. A place with no safety information is labeled as missing information, never safe, low risk, or cleared. Broad location labels need exact local confirmation before being used for a journey.
Know which logistics inputs are present
The logistics view groups current claims into safety watch, road and transport, fuel and costs, power and water, communications, and weather and support. Each place card shows the available records, evidence states, source references, expiring signals, and absent categories.
The current feed does not supply complete vehicle restrictions, distances, journey durations, warehouse capacity, cold-chain capacity, supplier quantities, driver readiness, or movement tracking. Those inputs must be obtained separately. This dashboard supports planning; it does not choose or clear a route.
All time has a recording boundary
History is an aggregate of the retained first-publication ledger joined to eligible event clusters. It includes expired events, excludes merged duplicates, disputed claims, and events now hidden or under review, and never exposes raw historical observations, reporter identities, private headlines, or coordinates. The original ledger began after launch and had a limited backfill; earlier missing publications cannot be reconstructed from it.
The All time, 7 day, 30 day, and 90 day windows use publication-ledger timestamps. Daily or monthly charts group those timestamps in Haiti time, including the partial current period. Category and area labels use the current eligible event classification, so corrections can revise historical totals. Attached reports are the current report totals on the selected event clusters, not a count of reports submitted during the selected window. These totals are distinct from incident counts and from the legacy first-reported-time security metric.
Private saved captures
Cloud briefs require a WOUT account. The database generates each capture from public current reports and aggregate global history; clients cannot submit an arbitrary snapshot. Each account can retain up to 20 briefs, each capped at 512 KiB. Account ownership is enforced by database permissions and row-level security, with no direct client insert or update access.
A saved capture includes its capture time, up to 200 current public report records, source references, display-expiration times, and global history totals. It does not store news article bodies, precise coordinates, reporter identities, or planned journeys. A chosen place filters current reports only; history totals remain global. Owners can download or delete their briefs. Saved information can outlive its freshness window and is never a live safety clearance.
Export the evidence, with its time
CSV and JSON exports contain the full current returned report sample, rather than news article bodies. They include evidence states, attached-report counts, source references, the calculation time, and expiration times. CSV fields are quoted and spreadsheet formula prefixes are neutralized.
If the history or cloud interface has not been connected, the product shows that state directly. An unavailable historical source is not replaced with invented counts. Current reports, linked news, and local exports remain independent of those new interfaces.
Based on the WOUT implementation reviewed October 11, 2026. Rules and product availability can change. Examples are explanatory; current records appear in the public analysis.
Inspect the latest public calculation