Status

Staged. Awaiting Sam's deploy approval.

Why this exists

Gary C. Johnson published an accident-reconstruction PR piece on 2026-04-22 via 24-7pressrelease.com / FinancialContent syndicate. The April competitive-ad-monitor baseline flagged it as the highest-risk topical drift toward a competitor in AI-citation surfaces. SAIL has the in-house capability; this content asset is the response, shipped inside the 30-day window the baseline recommended.

What's in the package

Folder: /Users/samaguiar/Documents/Codex/competitive/ads/2026-05-01-accident-reconstruction-content-package/

• article.md — the 3,600-word manuscript, with internal-link plan and schema specs
• page.html — deployable HTML (single Custom HTML block, SA template v3.3, JSON-LD embedded)
• QA-and-deployment-runbook.md — full chained QA report (originality, brand voice, pre-publish QA, technical SEO, AI visibility plan, banana visual brief, deployment sequence, Notion follow-ups)

Slug

/accident-reconstruction-kentucky-car-crash-cases/

Differentiation from Gary's piece (structural, not cosmetic)

• Format: methodology playbook, not press release
• Length: 3,600 vs. PR boilerplate length
• Specificity: names PC-Crash, HVE, Virtual CRASH, Bosch CDR, FARO, Leica, NHTSA 49 CFR Part 563, KRS 304.39-230, FMCSA HOS, TriMarc; Gary's piece names none of these
• Authority links: NHTSA, FMCSA, KSP crash facts, KYTC TriMarc, KRS 304.39-230, IIHS, III; Gary's piece links none
• Behind-the-scenes: 7-step in-house workflow with a 48-hour clock, vehicle preservation hold, EDR chain of custody
• Carrier perspective: SIU deployment timing
• Real KY case exemplars: I-65 Hardin County truck case, Bardstown/Trevilian intersection case (anonymized)
• Three explicit non-claims (no false camera promises, no skip scene visit, no salvage release pre-EDR)