Files
veripath/founding-partner-audit/report-template.md
T

41 lines
2.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Golden Ticket Report — Template
Built on the locked beta pipeline (`multi_scraper → audit_engine → report_generate → report_gate`; see `docs/operations/beta-audit-process.md`). The Golden Ticket report is the synthesized, client-facing artifact: physician tone, x-ray in hand, no sales pitch.
## Rules
- **35 findings max.** Every finding = plain-English explanation + concrete evidence (quoted field value, screenshot, date). No finding without evidence.
- **Tiered language:** Tier 1 (verified) → state as fact. Tier 2 (corroborated) → "appears to," "in our sample."
- **Banned language** (same gate as `docs/agents/audit-findings-template.md`): *should, recommend, fix, opportunity, package, solution, proposal, next step.* We show the x-ray; the owner draws conclusions.
- No hard close. No pricing. No "free trial" framing anywhere.
## Structure
### 1. Recognition
One sentence that proves we actually looked. Must be specific to *this* business — if the sentence would fit any other business, rewrite it.
### 2. What we found (35 findings)
For each:
- **Title** — plain English, no jargon (e.g., "Your hours disagree across three places," not "temporal inconsistency vector")
- **What it looks like** — the evidence: the quoted value, the screenshot reference, the date observed
- **Who it touches** — customers, or how AI surfaces describe the business
### 3. Consequence (quiet)
Two to four sentences: what this means for customers finding the business, and how AI answer engines currently represent it. State it flat. Let it land.
### 4. Two doors
- **Door A — the work.** "If you want, we close these gaps and keep watching." (No pricing here.)
- **Door B — do it yourself.** "The attached guide covers each finding with exact steps and values. It's complete on its own."
Both doors real. Neither pitched over the other.
### 5. Method footer
One line: surfaces checked, date, tool. No disclaimer wall.
## Production checklist (before print)
- [ ] Every engine finding resolved per beta-audit reviewer loop (VALIDATION.md exists)
- [ ] Banned-language gate pass
- [ ] Recognition sentence is wrong-for-anyone-else test
- [ ] Door B attachment present and standalone-complete
- [ ] Findings count 35, each with evidence + tiered phrasing