Public Diagnostic Examples (Release Validation)

Purpose

Five real startup URLs used to validate that the engine produces coherent output before v1 is considered live. CMO defines the URLs and the expected “coherent” criteria; runs are executed and sign-off is required.

Coherent output (definition)

For each of the 5 URLs, a run is considered coherent when:

1. Report 1 completes with a valid stage and recommendation (no generic or empty verdict).
2. Stage is one of: Idea Validation | Early Traction | Product-Market Fit | Scaling | Growth, and matches the public stage definition.
3. Recommendation is one of: Continue | Pause | Kill, with reasoning that references evidence (blockers/opportunities/focus area).
4. DRL and component analyses (brand, product, pricing, distribution, market) are present and consistent with the verdict (no contradictory signals without explanation).
5. One thing this week (or next milestone) is a single actionable sentence when Report 3 is run.

Golden URLs and baselines

• Regression baselines live in scripts/golden-baselines/ and scripts/golden-urls.json (key fields: stage, recommendation, component analyses, DRL).
• The 5 real startup diagnoses for release are to be chosen by CMO (URLs + short expected outcome). Placeholder list below; replace with actual URLs and expectations before release.

Placeholder: 5 startup URLs (CMO to fill)

After CMO fills this table, run the diagnosis for each URL, confirm coherent output per the definition above, and sign off. Until then, v1 is not “live” per release-scope.md.

Distribution strategy (CMO)

• Public diagnostic examples can be anonymized or named case studies for marketing (e.g. “Stage: Early Traction; recommendation: Continue; one thing: clarify pricing page”).
• Distribution strategy and channels are defined in distribution-plan.md; this doc is for release validation only.

Related Docs

• Release Scope
• PMF Stage Definition
• Output Narrative Structure