# venture-option-spec.yaml — opportunity/venture-option 데이터 스키마(§6.1).
# 변경 이유 = 산출물 구조 변화. 역할 매핑은 venture-validation-map.yaml(변경 이유 다름).
venture-option-spec:
  version: 1
  opportunity-cluster:      # opportunity-discovery 산출(제품명 이전, 문제 클러스터)
    required: [id, problem-domain, target-user, triggering-event,
               current-alternative, why-now, founder-fit]
  venture-option:           # venture-validation 산출(옵션별)
    required: [id, customer, painful-job, current-alternative, wedge,
               monetization, expected-price, reachable-customers,
               rough-revenue-ceiling, acquisition-channel, build-cost,
               operation-cost, founder-fit, defensibility, kill-criteria,
               unresolved-assumptions]
    notes:
      - "'unknown' 은 허용값(모른다고 적을 수 있어야 한다) — 단 unresolved-assumptions 에 명시."
      - "kill-criteria 는 필수 — 없으면 venture-validation→venture-decision 차단."
  validation-result:        # 게이트별 판정 스냅샷
    required: [option-id, gate, verdict, evidence, dissent]
    verdict-enum: [pass, fail, unknown]