PDR-009: Formalize Six-Family Product Mapping and Buyer Taxonomy

[kas1987]

Objective

Create the taxonomy backbone for the ZELEX Concierge Atlas by formalizing the six body families, mapping every ZELEX body/product to those families, and defining how the taxonomy powers discovery, quiz scoring, comparison, character pages, inquiry routing, and CEO-facing product strategy.

Strategic thesis

The site should not behave like a flat product catalog. It should guide buyers from intent to silhouette family to body architecture to character to private inquiry.

Core model:

ZELEX product / body code
→ measured body profile
→ WHR + BWR classification
→ one of six body families
→ persona / character layer
→ buyer-facing catalog, quiz, compare, and inquiry flow

Six families to formalize

Family	Silhouette	Buyer archetype	Strategic role
The Classic	Timeless hourglass	First-time premium buyer	Safe entry point / balanced recommendation
The Icon	Glamour model	Photographer / curator	Editorial, photogenic, camera-forward
The Muse	Tall, hip-dominant	Realism / European aesthetic buyer	Naturalism and believable presence
The Siren	Bust-dominant fantasy	Character / anime crossover buyer	High-drama fantasy and statement presence
The Empress	Maximum plush	Body-positivity / plush collector	Abundance, softness, regal presence
The Sculpt	Muscular definition	Fitness realism seeker	Athletic/defined realism

Scope

• Document the canonical definition of all six body families.
• Confirm and version the WHR/BWR thresholds for each family.
• Map every body_code in db/body_profiles.json, db/body_types.json, and db/characters.json to a family status.
• Mark each assignment as exact, near, estimated, manual-review, or unclassified.
• Define buyer-facing copy tone for each family.
• Define visual treatment guidance for each family.
• Define quiz scoring weights and result explanation logic.
• Define compare-page interpretation rules: easiest handling, most natural, most camera-forward, most statement-heavy, most plush, most athletic.
• Define character-page modules using family data: family badge, buyer-fit notes, more from this family, sister body alternatives.
• Define contact/inquiry payload fields so family, body, character, quiz result, and compare selections pass into the concierge intake.
• Define CEO-facing product matrix columns for strategy review.

Data model additions / checks

Proposed fields to standardize:

{
  "body_code": "ZG162D",
  "family": "The Muse",
  "family_confidence": "exact",
  "family_basis": "WHR/BWR/spec-card",
  "estimated": false,
  "buyer_archetype": "Realism / European aesthetic buyer",
  "best_for": ["naturalism", "first serious buyer", "photography realism"],
  "watchouts": ["less fantasy volume", "may feel understated to glamour buyers"],
  "handling_class": "solo-manageable",
  "visual_treatment": "soft editorial naturalism"
}

CEO-facing product matrix

Create a matrix with at least:

• body_code
• series
• line
• height_cm
• cup
• weight_kg
• bust / waist / hip
• WHR
• BWR
• bust_drop_cm
• family
• family_confidence
• estimated
• product_count
• persona
• target_buyer
• best_for
• watchouts
• inquiry_priority
• visual priority
• notes

Acceptance criteria

• Every known ZELEX body has a family status.
• Every family has a defined buyer persona, copy tone, visual language, CTA strategy, and comparison meaning.
• Estimated and near-match bodies are visibly marked and not misrepresented as verified specs.
• The family assignment method is documented enough to regenerate from measurements.
• Manual override rules exist for CEO/brand curation.
• Quiz, compare, character page, and contact flow have clear taxonomy integration rules.
• A PDR markdown file is created as PDR-009-six-family-product-taxonomy.md.

Dependencies

• db/body_profiles.json
• db/body_types.json
• db/characters.json
• assets/site.js
• PDR-003 Body Compare Tool
• PDR-004 Quiz Match-Score Funnel
• PDR-005 Character Detail Premium Conversion
• PDR-006 Concierge Intake

Suggested owner agent

Archivist for schema/taxonomy, Cartographer for UI integration, Auditor for data validation.

Output package

• docs/pdr/PDR-009-six-family-product-taxonomy.md
• docs/taxonomy/body-family-method.md
• docs/taxonomy/body-family-copy-guide.md
• docs/taxonomy/body-family-product-matrix.md
• Optional generated JSON: db/family_taxonomy.json