version: 1
purpose: "Route user requests to the smallest suitable GameDesignOS entrypoint before reading long skill bodies."
status: candidate
promotion_gate:
  required_before_enforce:
    - "Run representative routing replay cases across all public skills."
    - "Confirm the router reduces mis-triggering without hiding relevant fallback skills."
    - "Keep manual override available when the user explicitly names a skill."
default_rules:
  - id: route_media_sample_to_gea
    when:
      any_input_type: [screenshot, gameplay_recording, video_url, trailer_pv, paid_creative, store_page]
    use: game-experience-analyzer
    reason: "Establish sample_boundary, evidence_index, access_notes, and evidence-linked issue cards first."
    primary_outputs: [evidence-index, issue-card, ed-handoff, validation-plan]
    runtime:
      signals: [screenshot, recording, gameplay, video, trailer, pv, store page, steam page, 截图, 录屏, 录像, 视频, 宣传片, 商店页, 试玩样本]
      reason_zh: "媒体或试玩样本要先建立证据边界和问题卡，再进入后续实验或策划判断。"
  - id: route_one_line_idea_to_gca
    when:
      user_intent: [one_line_game_idea, concept_seed, game_pitch, design_brief_request]
    use: game-concept-architect
    reason: "Turn the concept seed into player verbs, design nucleus options, player-promise-contract, scope gate, and validation plan."
    follow_on:
      when_user_also_intends: [game_proposal, commercial_product_proposal, indie_design_dossier, gdd_assembly, publisher_pitch, vertical_slice_doc]
      use: game-design-proposal-writer
      reason: "When the user asks for a proposal from a one-line idea, first create the concept contract, then assemble the decision-ready document."
    primary_outputs: [player-promise-contract, validation-plan]
    runtime:
      signals: [one line idea, one-line idea, game idea, concept seed, core loop, creative premise, 一句话创意, 游戏创意, 我想做, 想做, 做一款, 做一个游戏, 游戏项目, 玩法方向, 立项方向, 概念种子, 核心循环, 玩法点子]
      reason_zh: "粗创意要先变成玩家承诺、核心循环、范围门和验证计划，再进入策划案或立项判断。"
  - id: route_proposal_assembly_to_gdpw
    when:
      user_intent: [game_proposal, commercial_product_proposal, indie_design_dossier, gdd_assembly, publisher_pitch, investor_pitch, vertical_slice_doc, one_page_decision_memo, formal_project_review_doc, mindmap_to_game_proposal, xmind_to_game_proposal, gameplay_system_mindmap_to_proposal, existing_proposal_review, proposal_rewrite, gdd_review]
    use: game-design-proposal-writer
    reason: "Assemble existing research, concept contracts, evidence, validation plans, production constraints, and business goals into a decision-ready proposal, pitch, dossier, memo, or vertical-slice document."
    preferred_inputs: [player-promise-contract, validation-plan, evidence-index, issue-card, ed-handoff, mindmap/xmind/opml/markdown outline, existing proposal or GDD, market/source notes, production profile]
    guardrails:
      - "Do not override game-concept-architect when the user only has a one-line idea and wants concept viability."
      - "Do not override game-experience-analyzer when the task is media/sample diagnosis."
      - "Do not override game-experience-density-optimizer when the task is a retention, pacing, feedback, or instrumentation experiment."
    primary_outputs: [commercial_product_proposal, indie_design_dossier, one_page_decision_memo, publisher_pitch_outline, vertical_slice_design_doc, proposal_review_and_rewrite]
    runtime:
      signals: [proposal, publisher pitch, investor pitch, gdd, vertical slice, decision memo, 商业策划案, 立项案, 发行 pitch, 投资 pitch, 策划案, 垂直切片, 决策 memo]
      reason_zh: "面向决策的文档应整合已有概念、证据、验证和生产约束，而不是补编缺失上游。"
      required_any_upstream_types: [concept, validation, evidence, analysis, experiment, knowledge]
  - id: route_density_experiment_to_edo
    when:
      user_intent: [retention_experiment, first_session_pacing, cognitive_load, feedback_strength, embodiment_feel, atmosphere_pacing, demo_completion_quality, single_player_total_journey, return_session_rehook, old_player_habituation, telemetry_dashboard, weekly_ab_plan]
    use: game-experience-density-optimizer
    reason: "Convert evidence or hypotheses into one-week ED experiments, instrumentation, dashboards, decision rules, and rollback."
    preferred_inputs: [ed-handoff, issue-card, telemetry_snapshot]
    guardrails:
      - "If the input is a screenshot, recording, PV, store page, or other media sample without an evidence layer, route to game-experience-analyzer first."
      - "If the input is only a one-line concept without a core loop or player promise, route to game-concept-architect first."
      - "If the user asks for a proposal, pitch, GDD assembly, or decision memo from existing ED results, route to game-design-proposal-writer after the ED experiment artifact exists."
      - "Do not route ED tasks to external/global design skills; this contract only coordinates skills inside this repository."
    primary_outputs: [weekly_ed_experiment_plan, instrumentation_dictionary, dashboard_spec, decision_rules, experiment-plan.schema.json]
    runtime:
      signals: [retention, first session, pacing, feedback strength, cognitive load, instrumentation, dashboard, ab test, a/b test, 留存, 首局, 节奏, 反馈, 认知负荷, 埋点, 看板, a/b, 体验浓度]
      reason_zh: "体验问题要先有证据或问题层，才能转成一周实验、埋点和回滚规则。"
      required_any_upstream_types: [evidence, analysis, experiment]
  - id: route_information_value_audit_to_evolver
    when:
      user_intent: [information_value_audit, research_priority, decision_information_gate, fomo_or_information_overload, ai_branch_pruning, decide_whether_to_search_ask_or_test, rjr_ai_authority_gate, residual_judgment, judgment_authority, permission_boundary, ai_engineering_authority]
    use: paranoia-ai-system-evolver
    reason: "Define the decision object, current default action, RJR-AI authority boundary, signal-to-action map, EVPI/EVSI, smallest positive-net-VOI probe, and stop rule."
    primary_outputs: [information-value-assessment, decision-brief, ooda_voi_state]
    runtime:
      signals: [voi, fomo, research overload, ai fatigue, information value, residual judgment, judgment authority, authority gate, 信息价值, 信息焦虑, ai 疲劳, 剩余判断权, 判断权, 授权, 授权层, 权限系统]
      reason_zh: "信息获取和剩余判断权要先经过 VOI、授权边界、Human Gate 与停止规则。"
    guardrails:
      - "Do not produce a broad trend summary when no decision object exists; timebox exploration or classify it as model learning or information consumption."
      - "Do not let AI assume residual judgment for high-coupling, low-reversibility, under-evidenced choices; route to Human Gate."
      - "Limit candidate information actions to three and pre-register the action for each plausible signal."
      - "If all plausible signals lead to the same action, stop research and proceed with the current default action."
  - id: route_system_change_to_evolver
    when:
      user_intent: [skill_change, prompt_change, workflow_change, schema_change, eval_change, router_change, memory_or_feedback_loop_change, project_process_improvement, workflow_governance, output_quality_improvement, rjr_ai_absorption, authority_layer_change, delegation_matrix_change, intent_engineering, intent_work_order, ai_work_order, instruction_sheet_to_intent, commander_intent, uncertainty_ladder, progressive_uncertainty_release, bottleneck_attribution, transfer_validation]
    use: paranoia-ai-system-evolver
    reason: "Keep AI-system evolution and AI work-order upgrades candidate-gated with an Intent Work Order, decision object, RJR-AI authority gate, VOI/EVPI/EVSI, UL (Uncertainty Ladder), OODA, behavior evals, Human Gate, versioning, and rollback."
    primary_outputs: [intent-work-order, workflow-governance-review, evolution-proposal, information-value-assessment, ul-state, ooda-voi-state]
    runtime:
      signals: [prompt change, workflow change, schema change, eval change, router change, memory change, skill change, intent engineering, intent work order, ai work order, instruction sheet, commander intent, uncertainty ladder, progressive uncertainty, bottleneck attribution, transfer validation, rjr, rjr ai, rjr-ai, ai engineering, workflow, workflow governance, overall process, project process, process improvement, output quality, eval, human gate, rollback, ai 工程, ai工程, 不确定性阶梯, 逐步释放不确定性, 瓶颈诊断, 迁移验证, 意图工程, 意图单, 意图工作单, ai 工作单, ai工作单, 指令单, 作战意图, 组织记忆, 提示词改造, 工作流改造, schema 改造, 评测改造, 路由改造, 记忆改造, skill 改造, 整体流程, 项目流程, 流程优化, 产出优化, 产出质量]
      reason_zh: "系统改动、意图工作单升级和工作流治理要经过 VOI、UL（不确定性阶梯）、eval、Human Gate 和 rollback，先保持 candidate。"
  - id: route_translation_to_book_translator
    when:
      user_intent: [translate_game_design_book, polish_translation, terminology_table, pdf_or_ocr_translation]
    use: game-design-book-translator
    reason: "Handle terminology, copyright/source gates, figure/table structure, chapter packaging, and Chinese editorial quality."
    primary_outputs: [translated-reference, terminology-table, chapter-package]
    runtime:
      signals: [translate, translation, book chapter, terminology table, 翻译, 译文, 书籍章节, 术语表]
      reason_zh: "设计资料翻译需要术语、图表、来源边界和编辑检查。"
  - id: route_source_ingest_to_curator
    when:
      user_intent: [curate_sources, ingest_source, incremental_source_update, durable_knowledge_base]
    use: game-design-source-curator
    reason: "Turn sources into traceable, deduplicated, evidence-gated knowledge assets instead of one-off summaries."
    primary_outputs: [source-note, reference-boundary, knowledge-entry]
    runtime:
      signals: [curate sources, knowledge base, source ingest, article collection, 资料策展, 知识库, 来源整理, 文章收集]
      reason_zh: "散落资料应沉淀成可追踪知识资产，而不是一次性摘要。"
fallback_rule:
  when: ambiguous_or_multi_skill_request
  action:
    - "Name the decision or next stable artifact before expanding the task."
    - "Select the smallest skill that can produce the next stable artifact."
    - "Prefer contracts over broad prose handoff."
    - "State which follow-on skill should consume the artifact."
collaboration_rules:
  - id: project_internal_only
    rule: "Route only among skills shipped inside this repository. Do not introduce external/global design-master skills into this collaboration graph."
  - id: decision_before_information
    rule: "Before broad research, retrieval, memory reads, tests, or extra AI branches, define the decision, options, current default action, boundary status, signal-to-action map, costs, and stop rule."
  - id: rjr_authority_before_execution
    rule: "Before AI execution, publication, durable memory, project-direction changes, or system-rule promotion, define coupling, reversibility, authority level, delegation matrix, residual judgment, Human Gate, and rollback."
  - id: concept_to_evidence_to_experiment
    flow:
      - skill: game-concept-architect
        stable_outputs: [player-promise-contract, validation-plan]
      - skill: game-experience-analyzer
        stable_inputs: [player-promise-contract, media sample]
        stable_outputs: [evidence-index, issue-card, ed-handoff]
      - skill: game-experience-density-optimizer
        stable_inputs: [ed-handoff, issue-card, telemetry_snapshot]
        stable_outputs: [weekly_ed_experiment_plan, instrumentation_dictionary, dashboard_spec, decision_rules]
  - id: proposal_after_artifacts
    rule: "Use game-design-proposal-writer only after concept, evidence, ED, source, or production artifacts already exist; it assembles decisions rather than replacing upstream diagnosis or experiment design."
  - id: evolver_as_project_governance_layer
    rule: "Every end-to-end workflow should expose paranoia-ai-system-evolver checkpoints at intake intent, VOI/RJR boundary, midstream drift, final Human Gate, rollback, and retrospective candidate learning; keep the checkpoints in shadow or warn mode until eval evidence justifies enforcement."
  - id: evolver_scope
    rule: "Use paranoia-ai-system-evolver for controlled system mutations, workflow governance reviews, RJR-AI authority gates, or explicit VOI decision audits; do not use it to replace concept architecture, media diagnosis, ED experiments, or proposal assembly."
  - id: source_curator_as_knowledge_input
    rule: "Use game-design-source-curator to create traceable knowledge assets; it may enrich references but should not replace concept architecture, evidence diagnosis, ED experiments, or proposal assembly."
  - id: translator_as_knowledge_production
    rule: "Use game-design-book-translator for translation and polishing of design sources; translated knowledge becomes reference input, not a runtime routing target for ED experiments."