The evidence layer behind the Journeys page: every ranked walk, the single-step flow, dwell by zone, and individual stitched timelines. Opens from journeys.html — not a subnav page of its own.

Talk track. The Journeys page gives the reading; this page is why you can trust it. The wow is a stitched row: one person, nine broken tracker fragments, one continuous visit.

Claims. REAL numbers: RB’s fountain camera, Sat 18 Jul, shown on the demo store. The visit list is the 10-journey curated sample from the fixture payload (7 stitched, 2 quality-excluded, 1 unlinked single); the full surface lists all 320. Fixture spans are disjoint, so entry order is the walk. Ambient container zones (area / general traffic) are context lanes and the “entered the area at all” denominator — never a step, never summed into fixture dwell. Store-local times, UTC−5. No person imagery — crops stay in the system-admin audit view.

Build readiness. Journey linkage, stitching, and the journeys API are a shipped primitive; an internal audit view exists. The blocks here are derivable from the API’s per-journey timelines. Not built: this page as a tenant surface.