Location Pages Playbook — Blindspot Gap Report

Generated post-Playwright audit. Every contradiction + consumption-flow issue Audrey flagged, plus five new ones found in this pass.

Critical — fixed this pass

FIXED§ 12, 13, 14 polished demos were mis-mapped.

The DEMOS dict used architecture numbering (01 = Hero, 14 = Daniel) while specs use 1-indexed-from-sticky-bar (§ 01 = Sticky Bar, § 14 = Nearby Cities). Result: § 12 Financing showed FAQ content, § 13 FAQ showed Final CTA, § 14 Nearby Cities showed Daniel widget. Remapped to correct content.

FIXEDBroken "Manual (retired) (fully manual)" sentences.

Global Path A → "Manual (retired)" replace produced nonsense like Manual (retired) (fully manual) has been retired as of Apr 20. Rewrote the 2 broken sentences to read naturally.

Open — needs Robert / Audrey call

OPENCL-15 Availability Chip placement buries it at the bottom.

The component is referenced in § 02 City Hero (Availability Card pinned right 300×120) and § 05 Live Availability. But it's defined 50+ scroll-screens later inside the Live Fleet strategic section, numbered CL-15, after the Google API catalog. Audrey has to hunt.

Recommended fix: extract the CL-15 spec block and move it to sit with CL-01 through CL-14 in the Component Library section. Leave a small reference chip in the Live Fleet section pointing back to the main library entry.

OPEN"Availability Card" vs "Availability Chip" — same component, two names.

§ 02 and § 05 call it "Availability Card." § CL-15 is named "Live Availability Chip." Audrey opens Figma not knowing which name to use. Pick one and rename everywhere. Recommend "Availability Chip" (CL-15 is the canonical spec; "Card" reads as the bigger hero-pinned variant, "Chip" is the inline trust-bar variant, but the component IS the same base).

OPENSection numbering contradicts: architecture shows 14, specs have 15.

The 14-Section Architecture diagram lists 14 numbered content sections starting with 01 Hero. The Section-by-Section Figma Specs list § 01 Sticky Emergency Bar through § 15 Final CTA + Multi-Step Form. Off by one: spec § 01 (Sticky Bar) is un-numbered "🚨 STICKY EMERGENCY BAR (fixed top)" in the architecture diagram.

Fix: renumber architecture to "15-Section Architecture" starting with 01 Sticky Emergency Bar, OR renumber specs to match architecture (§ 01 = Hero, Sticky Bar = § 00). Recommend the first — Sticky Bar IS a section, it deserves a number.

OPENCross-reference matrix is off by one.

The "which component shows up in which section" matrix lists § 15 Final CTA but the architecture tops out at § 14. Rows for § 15 may or may not be correct depending on which numbering wins above.

OPENPhase/tier confusion in component build order.

Header says "Phase 1 ship priority" but the list mixes 11 Phase-1 components with 3 Phase-2 ones (Daniel widget, multi-step form). Split into two ordered lists: Phase 1 — must ship and Phase 2 — data-driven.

Minor — cleanup backlog

OPENBrand color swatch "--navy-deep #100B3E" isn't used anywhere in the specs.

Ghost token. Either remove or specify where it's used (e.g., hover-darken on primary CTAs).

OPEN"Free to $30/mo (Tier A)" calculations in Google API stack don't match the three-tier ship order.

Table says Tier A is "free or near-free" but lists 9 APIs, 4 of which charge beyond the $200/mo Maps credit once volume hits. Clarify or add "all within $200/mo Maps credit at current BSP volume" footnote.

OPENH1 formula example is Sewer Repair but Phase 1 sniff test is "4 T1 cities × 1 service (Plumber generic)".

§ 02 shows "Sewer Repair in Overland Park — 5th-Generation Master Plumbers" but the Phase 1 ship list says the service prefix is generic "Plumber." Pick one.

Flow recommendations for Audrey (document consumability)

  1. Move the TOC to the top with anchor links. Currently scattered across the intro. Audrey needs a single jump-nav.
  2. Add a "Start here" section for Audrey specifically. 5-step checklist: (1) read North Star, (2) read Figma Guide, (3) open Components, (4) read spec for Section 01, (5) design Mobile 390 first.
  3. Collapse the Live Fleet + Google API stack behind a summary + "expand for details" toggle. Audrey doesn't need to read 7,000 words on Routes API vs Distance Matrix to design a component. That content is for Robert.
  4. Put every polished demo right next to its spec (already done in this pass — verify visually after Playwright audit).
  5. Add a "quick visual index" at top: every section's polished demo in a grid, each linking to its full spec below. Audrey picks a demo, sees the spec.

Generated 2026-04-21 · Post-Playwright audit · Paired doc: BSP_Location_Pages_Playbook.html