Product Definition template

Emit the definition in this shape. Every section is filled from evidence or moved to Open Questions. No placeholders, no TBD. Each section carries an evidence grade (L1 to L5) and a source. When the definition lands in BluCity-Docs, split it across the AUTHORITY-MATRIX files (Vision.md, Architecture.md, API.md or Spec.md, Deployment.md or Runtime.md, Roadmap.md) and use the corpus frontmatter.

---
bluefly_document: true
status: candidate            # candidate | approved | canonical | deprecated
owner: <one accountable owner>
authority: Product Authority Matrix
created_at: <ISO 8601 with offset>
updated_at: <ISO 8601 with offset>
evidence_floor: L5           # lowest grade any load-bearing claim rests on
hypothesis_document: true    # true until evidence_floor is L3 or better
derived_from: []
verified_against: []
---

EXECUTIVE DECISION                PRODUCT_NAME, PRODUCT_TYPE (classification enum), PRODUCT_FAMILY,
                                  PRODUCT_OWNER, ONE_SENTENCE_DEFINITION, COMMERCIAL_CATEGORY,
                                  CURRENT_MATURITY, PRIMARY DECISION ("X is the product; do not create Y")

PRODUCT NAME                      checked against taxonomy and brand list

PRODUCT TYPE                      Product | Offering | Pack | Capability | Standard | ... (Stage 0)
PORTFOLIO PLACEMENT               Mountain / Product / Offering; existing product it belongs to
FACTORY MAPPING                   Product -> Factory -> Outputs -> Domains -> Systems (one line each)

ONE-SENTENCE DEFINITION

PROBLEM                           in the customer's words
WHY NOW                           the change in the world
TRIGGER EVENTS                    what happens right before they buy
CURRENT ALTERNATIVES              direct / indirect / internal / do nothing
JOB TO BE DONE                    thing vs outcome vs experience vs identity

TARGET MARKET                     category type and sizing method
ICP                               table per customer-psychology.md
USERS / BUYERS / CHAMPIONS / BLOCKERS   the persona map, one line each, plus top objection

VALUE PROPOSITION                 customer, problem, outcome, mechanism, differentiator, proof
POSITIONING                       FOR / WHO / IS A / THAT / UNLIKE / IT
DIFFERENTIATION                   evidenced claims only; struck words listed
COMPETITIVE LANDSCAPE             table with sources and dates

PRODUCT EXPERIENCE                what it feels like end to end; the activation event
CORE CAPABILITIES                 each composed from a named upstream
WHAT THIS PRODUCT IS NOT          explicit exclusions and neighbors it must not absorb
CUSTOM JUSTIFICATIONS             only where no upstream covers the gap; name the gap

MVP                               hypothesis, top risk, smallest test, success criteria, date
RISKS / ASSUMPTIONS               eight risks ranked with mitigations
EVIDENCE                          ladder position for each load-bearing claim

BUSINESS MODEL                    who pays whom, for what, when, why
PRICING (DRAFT)                   basis, strategy, tiers, caps; operator approval pending
COGS                              including model/API usage, labor, support, compliance
UNIT ECONOMICS (DRAFT)            revenue, gross margin, CAC, LTV, payback, sensitivity
OFFER                             package, price, terms, acceptance, guarantee, onboarding, proof
SERVICE-TO-PRODUCT POSITION       which rung today, which rung next, what earns the move

GTM                               channels (two to start), first ten prospect types
SALES MOTION                      chosen from evidence
DISTRIBUTION                      including product-native loops
COMMERCIAL WORK GATE              buyer, problem, offer, outcome, proof, reuse, horizon, next action

BRAND                             which existing brand; personality and promise
MESSAGING                         name, tagline, one-liner, headline, subheadline, 3 benefits + proof, CTA
VISUAL STORY                      the one image and its caption; narrative arc in six sentences

ACTIVATION                        the observable "I get it" event
RETENTION                         why return, what improves with use, what makes leaving costly, churn triggers
GROWTH LOOPS                      the native loop or the honest absence of one
MOAT                              evidenced, or "none yet"

METRICS                           North Star plus AARRR, cost, reliability
LIFECYCLE STAGE                   discovery ... retirement
ROADMAP                           outcomes and betting sequence, three horizons
PRODUCT OWNER                     one name
KILL CRITERIA                     number, threshold, date, exit options

OPEN SOURCE BOUNDARY              if any part is open (conditional)
ECOSYSTEM                         what Bluefly owns vs enables

EVIDENCE STATE                    every load-bearing claim tagged CANONICAL_POLICY /
                                  CURRENT_PRODUCT_DIRECTION / CURRENT_SOURCE /
                                  HISTORICAL_SUPERSEDED / NOT_ESTABLISHED, plus explicit
                                  non-dependencies ("X required for MVP: NO")

OPEN QUESTIONS                    every section that could not be graded above L5, with the
                                  next action that would resolve it

Derived artifacts (emit only what evidence supports)

positioning statement; pitch ladder (headline, sentence, 30 seconds, 2 minutes); competitive analysis; MVP test plan; pricing sheet (DRAFT); offer sheet; GTM plan; roadmap; kill criteria; factories/<sku>/factory.yaml patch when the product is a Factory SKU; Portfolio-Registry offerings: entry; Beads for the next commercial action.

Governance block (append to every landed document)

<!-- BLUEFLY-DOC-GOVERNANCE
This is a governed Bluefly document.

Agents and humans making substantive changes MUST:
1. update `updated_at` in the YAML front matter;
2. never alter `created_at`;
3. preserve this governance block;
4. preserve authoritative content and provenance.
-->