demo:
  id: saas-product-discovery
  title: SaaS Product Discovery Demo
  domain: b2b_saas
  purpose: >
    Demonstrates how one SaaS interface can project different meaning,
    hierarchy, and calls to action depending on visitor intent, role, and
    semantic weighting.

semantic_contract:
  name: saas_product_discovery_contract
  principle: One product content model can produce multiple role-aware projections.
  sma_pattern: signal_meaning_action

deployment:
  type: embedded_layer
  modes:
    default: avatar_driven
    supported:
      - avatar_driven
      - headless
  entry_signal:
    avatar_driven: declared_role_or_session_intent
    headless: selected_use_case_behavior_or_weighted_content_signals
  identity_model:
    avatar_driven: declared_identity
    headless: data_driven_no_avatar
  note: >
    This demo shows SMA embedded directly into a marketing/product interface.
    The IA remains stable while hierarchy and calls to action are projected differently.

source_signals:
  provider: site_content_model
  default_fields:
    - page_title
    - hero_copy
    - feature_groups
    - use_cases
    - proof_points
    - pricing_cta
    - technical_specs

sma_enrichment:
  fields:
    business_value:
      label: Business Value
      group: executive
      type: score
      range: 0_to_1
      meaning: Revenue, efficiency, risk reduction, and executive relevance.
    technical_depth:
      label: Technical Depth
      group: technical
      type: score
      range: 0_to_1
      meaning: Architecture, integrations, APIs, security, and implementation detail.
    speed_to_value:
      label: Speed to Value
      group: adoption
      type: score
      range: 0_to_1
      meaning: How quickly the user can understand and act.
    trust_signal:
      label: Trust
      group: proof
      type: score
      range: 0_to_1
      meaning: Evidence, credibility, proof, case studies, and adoption cues.
    operational_fit:
      label: Operational Fit
      group: workflow
      type: score
      range: 0_to_1
      meaning: Fit with team workflow, process, and current tooling.
    strategic_alignment:
      label: Strategy
      group: executive
      type: score
      range: 0_to_1
      meaning: Alignment with larger organizational goals.

avatars:
  executive_buyer:
    meaning: Needs clarity, business value, risk reduction, and proof.
    ux_mode: focus
    scoring:
      business_value: 0.35
      trust_signal: 0.25
      strategic_alignment: 0.20
      speed_to_value: 0.15
      operational_fit: 0.05
      technical_depth: 0.00
    directions:
      business_value: higher_better
      trust_signal: higher_better
      strategic_alignment: higher_better
      speed_to_value: higher_better
      operational_fit: higher_better
      technical_depth: neutral
    ipc:
      rule: Technical detail is available but not foregrounded.
      forbidden_behaviors:
        - lead with implementation detail before business value
        - hide proof points below generic product claims
        - make pricing or demo CTA harder to find

  technical_evaluator:
    meaning: Needs architecture, integrations, API details, and implementation proof.
    ux_mode: explore
    scoring:
      technical_depth: 0.35
      operational_fit: 0.25
      trust_signal: 0.15
      speed_to_value: 0.10
      strategic_alignment: 0.10
      business_value: 0.05
    directions:
      technical_depth: higher_better
      operational_fit: higher_better
      trust_signal: higher_better
      speed_to_value: higher_better
      strategic_alignment: higher_better
      business_value: higher_better
    ipc:
      rule: Technical content is promoted and executive abstraction is reduced.
      forbidden_behaviors:
        - bury architecture behind marketing claims
        - remove implementation evidence from the first scan path
        - overstate certainty without supporting technical proof

  product_operator:
    meaning: Needs workflow fit, usability, implementation effort, and handoff clarity.
    ux_mode: balanced
    scoring:
      operational_fit: 0.35
      speed_to_value: 0.20
      technical_depth: 0.15
      business_value: 0.15
      trust_signal: 0.10
      strategic_alignment: 0.05
    directions:
      operational_fit: higher_better
      speed_to_value: higher_better
      technical_depth: higher_better
      business_value: higher_better
      trust_signal: higher_better
      strategic_alignment: higher_better
    ipc:
      rule: Workflow clarity and next-step visibility are prioritized.
      forbidden_behaviors:
        - hide setup effort
        - place workflow content behind abstract positioning
        - present CTA without next-step clarity

headless_scoring:
  description: >
    Visitor behavior and selected filters adjust page hierarchy without requiring
    an explicit persona declaration.
  controls:
    - business_value
    - technical_depth
    - speed_to_value
    - trust_signal
    - operational_fit
    - strategic_alignment
  output: adaptive_page_hierarchy_without_persona_picker

projections:
  human_ui:
    - adaptive hero hierarchy
    - weighted feature ordering
    - role-sensitive CTA emphasis
    - proof-point reshuffling
    - semantic filter controls
  structured_data:
    type: product_semantics
    format:
      - JSON
      - JSON-LD
      - YAML contract
  agent_response:
    behavior: role_aware_product_explanation

proof_points:
  - Same page content produces different hierarchy by user meaning.
  - Avatar mode demonstrates declared intent.
  - Headless mode demonstrates inferred or selected weighting.
  - SMA governs what gets foregrounded before interface projection.
