Source quality

Source depth and launch-readiness.

Prefer official/public-record sources first, then transport/weather/safety, then event directories and local media. Verify civic claims against original records before publishing.

Source registryOpen JSON reportChecks
106Total sources
51Live routes
35High priority
37Official-first

Category mix

Broad enough source coverage keeps the briefing useful and reduces single-source risk.

OpenEvents22 source routes in the registry.OpenGovernment and records16 source routes in the registry.OpenDemocracy14 source routes in the registry.OpenLocal news12 source routes in the registry.OpenPlanning9 source routes in the registry.OpenHealth9 source routes in the registry.OpenWeather5 source routes in the registry.OpenLocal media5 source routes in the registry.OpenTravel4 source routes in the registry.OpenTransport3 source routes in the registry.OpenSafety3 source routes in the registry.OpenOpen data2 source routes in the registry.OpenPolice2 source routes in the registry.

Format mix

RSS, APIs, official pages and JSON feeds each need different validation behaviour.

OpenPUBLIC-SOURCE43 monitored source routes.OpenRSS32 monitored source routes.OpenAPI14 monitored source routes.OpenEVENT-SOURCE9 monitored source routes.OpenMEDIA-SOURCE4 monitored source routes.OpenJSON3 monitored source routes.OpenATOM1 monitored source routes.

Coverage gaps

Patch-level source checks before adding public launch claims or sponsor promises.

OpenPatch coverageEvery named coverage area currently maps to at least three source routes.