Launch readiness
Needs your attention
Pipeline funnel
By tour
Tier 2 — park coverage (outside the launch target)
Tier 3 — future locations
By district (legacy view — tell Code if you'd rather this was removed)
Management
Every stop across every tour that's Recorded and waiting on your listen-and-approve — oldest first, so nothing sits forgotten. Play it right here, then approve without opening the tour.
How a tour moves from an idea to a live, playable stop — in order. Each step says who does it and where to find it in the tracker.
The procedure — creation to deployment
Every tour comes from the project's location map, batched by district so one research pass covers driving, walking and heritage products at the same place. Tier 1 is the current build target — 14 tours, 150 scripts (A–N; Laurel Falls is trail-gated). Tier 2 runs as its own count, currently 2 tours / 17 scripts loaded of a 134-script plan. Tier 3 rows exist as unscripted placeholders.
Each stop becomes a new row — tour, district, type, stop title — created before or as the script is written.
Each stop is researched (5-source minimum), written to the Master Transcript Standard, and self-scored against the 100-point rubric before it's ever put in front of you — 96/100 clears content-tier. A verified pin (desk-GIS against two authoritative sources, or field-confirmed) or an interpolated pin (on the official trail centerline, wider radius) both pass the publish gate as-is; only a pin not yet in a valid state holds a script below the floor. 96 is the honest ceiling for content-tier — field-verifying an interpolated pin is a post-launch refinement, not a publish gate. These are Stage dots 1-3.
You review the script itself — not audio yet — and give the go-ahead to record. This is Stage dot 4, "Nicky Approval."
content_approved (Stage dot 4) directly.The earlier alternative — reading the batch .docx directly before it's ever seeded, with approval happening there ahead of seeding — was the locked process from 2026-08-16 through Batch 3. That path sets
content_approved at creation with no separate in-tracker click, since the row didn't exist yet to click on. Still available if you'd rather review a batch before it hits the tracker at all, but it's no longer the default. Either path, Stage 5 (Record) stays blocked until this is set, and rendering itself still waits on your separate, explicit go-ahead regardless.
Once content is approved, Code renders the script through ElevenLabs in Chris's locked voice and uploads it. Audio status moves to Recorded.
Once Code renders a script, every clip passes an automated decode/continuity check first — a machine gate that confirms the audio file itself is intact and matches the script's structure. It catches corruption, not narration quality, and there's no separate Code listening pass. Your listen is the real audio QA and your main action in the tracker: play the stop, and if it's right, click Approve Audio. If something's off, log a note instead (see Common Scenarios below) rather than approving — when in doubt, flag it, don't approve it. Stage dot 6.
Once approved, Code deploys the stop to the live site. Stage dot 7. This is the only step blocked by an unresolved GPS pin or open issue — see the rule below.
The one hard rule
Reading the tracker — what the colors mean
Pipeline stage (7 dots)
Content & Audio status
Issue pills
Common scenarios
+ Add note for Code on that row and describe it (e.g. "wrong accent, not Chris"). It logs as a blocking issue — don't click Approve Audio. Code re-renders and the status resets to Recorded for a fresh listen once fixed.+ Add note for Code on that row (e.g. "GPS: 35.6739, -83.4496"). Code sets the pin and marks it verified — no need to go through a separate form.Live from real telemetry — checked daily. Our own testing may still show up in these numbers until the paywall gives the site a real filter for who's a visitor.