# Shared narrative brief



Write `onboarding/narrative-brief.json` schemaVersion 2 after reviewed business evidence and inspected media. This artifact is shared by every concept. It is not marketing copy and not a style direction. Include visitor questions, proof status (`strong`, `limited`, or `missing`), asset strengths and limitations, tone constraints, recorded user goals, and design opportunities. An opportunity is `evidence-backed` only with evidence ids. A `design-hypothesis` must include `uncertainty`. Do not treat a filled opportunity as proof of aesthetic merit.



Identify the actual customer, the customer problem, the distinct offer, service scope, the best available proof, the primary conversion, purchase objections, and claims the source does not support. Every factual claim and proof choice must cite harvested evidence IDs or fact IDs. If a relationship is unresolved, record it as an uncertainty rather than flattening it into a slogan.



Do not import the operator's future platform strategy, harness internals, or reference-site demo people, phone numbers, ratings, or awards as this customer's facts. Keep audit caveats in this operator artifact; public copy later may preserve only the qualifications that affect a purchase decision.



The homepage first screen must be explainable from this brief: who this is for, what is offered, and the next step. Interior pages get their own purpose from the same facts, not a restatement of the hero.