{
  "schema_version": "myriuna-worlds.workflow.public.v1",
  "content_status": "working baseline",
  "purpose": "Show how work moves through Myriuna Worlds as its dominant question changes, from studio intent through product development, specialist execution, review, release, public communication, feedback, and post-mortem learning.",
  "interpretation": "This is a routing map for decision ownership and handoffs, not a mandatory conveyor belt or sequence of meetings.",
  "common_rhythm": [
    "intent",
    "bounded attempt",
    "evidence",
    "contradiction",
    "revision",
    "acceptance"
  ],
  "role_activation_rule": "Activate only the roles needed for the questions currently being answered. The narrowest role capable of answering the current question should remain active.",
  "stages": [
    {
      "id": "studio-direction",
      "name": "Studio conditions and direction",
      "owners": [
        "studio-lead"
      ],
      "purpose": "Set studio course, major priorities, commitments, operating conditions, and accepted studio-level risk."
    },
    {
      "id": "product-pass",
      "name": "Product outcome and development pass",
      "owners": [
        "product-lead"
      ],
      "purpose": "Define what should become true for the product or user, what remains outside scope, and how completion will be recognized."
    },
    {
      "id": "specialist-planning",
      "name": "Specialist interpretation and planning",
      "owners": [
        "research-lead",
        "gameplay-lead",
        "creative-lead",
        "tech-lead",
        "devops-lead",
        "studio-operations-and-compliance-lead"
      ],
      "purpose": "Expose consequences, dependencies, missing decisions, risks, and viable routes before work is commissioned."
    },
    {
      "id": "bounded-production",
      "name": "Bounded design, production, and implementation",
      "owners": [
        "gameplay-designer",
        "researcher",
        "technical-engineer",
        "writer",
        "visual-designer",
        "animator",
        "audio-producer",
        "voice-director",
        "video-editor",
        "narrative-systems-designer"
      ],
      "purpose": "Perform specialist work inside an accepted authority boundary and return evidence or artifacts."
    },
    {
      "id": "domain-review",
      "name": "Domain review and integration",
      "owners": [
        "gameplay-lead",
        "creative-lead",
        "senior-engineer"
      ],
      "purpose": "Review work against the commissioned intent, domain standards, integration needs, and accepted design."
    },
    {
      "id": "independent-readiness",
      "name": "Independent readiness evidence",
      "owners": [
        "software-tester",
        "gameplay-and-ux-tester",
        "creative-asset-tester",
        "devops-lead",
        "licence-and-provenance-researcher",
        "studio-operations-coordinator"
      ],
      "purpose": "Inspect the integrated result, operational state, permission state, and organizational records independently of production."
    },
    {
      "id": "acceptance",
      "name": "Acceptance and release decision",
      "owners": [
        "product-lead",
        "studio-lead"
      ],
      "purpose": "Accept, reject, constrain, defer, or return work according to the authority affected."
    },
    {
      "id": "deployment-publication",
      "name": "Trusted deployment or publication",
      "owners": [
        "devops-lead",
        "publisher"
      ],
      "purpose": "Promote approved work into trusted live or public state and verify the result."
    },
    {
      "id": "observation-feedback",
      "name": "Live verification and public response",
      "owners": [
        "devops-lead",
        "publisher",
        "community-manager"
      ],
      "purpose": "Observe the live result, verify public execution, and return significant defects or feedback."
    },
    {
      "id": "learning-loop",
      "name": "Post-mortem, correction, and next pass",
      "owners": [
        "product-lead",
        "studio-lead"
      ],
      "purpose": "Review the result and the role system, preserve corrections, and inform the next development loop."
    }
  ],
  "routes_by_dominant_question": [
    {
      "question": "What course should the studio take, and under which operating conditions?",
      "active_owners": [
        "studio-lead"
      ],
      "normal_return": "Delegated studio direction or revised conditions"
    },
    {
      "question": "What should Myriuna achieve next, and why does it matter to the product?",
      "active_owners": [
        "product-lead"
      ],
      "normal_return": "Accepted outcome, pass, or product decision"
    },
    {
      "question": "What uncertainty prevents responsible action?",
      "active_owners": [
        "research-lead"
      ],
      "normal_return": "Evidence, interpretation, remaining uncertainty, and recommendation"
    },
    {
      "question": "What should the player be able to do, understand, and experience through play?",
      "active_owners": [
        "gameplay-lead",
        "gameplay-designer"
      ],
      "normal_return": "Reviewed player-facing ruleset"
    },
    {
      "question": "What should the work express, sound like, look like, and feel like?",
      "active_owners": [
        "creative-lead"
      ],
      "normal_return": "Reviewed creative assets or specifications"
    },
    {
      "question": "Which broad technologies and approaches should the studio use?",
      "active_owners": [
        "tech-lead"
      ],
      "normal_return": "Technical direction and constraints"
    },
    {
      "question": "What structure, ownership, interfaces, and invariants must support the change?",
      "active_owners": [
        "system-architect"
      ],
      "normal_return": "Accepted structural design"
    },
    {
      "question": "How should that design be implemented in bounded steps?",
      "active_owners": [
        "senior-engineer"
      ],
      "normal_return": "Sequenced task briefs and technical review"
    },
    {
      "question": "How is the accepted task implemented and verified?",
      "active_owners": [
        "technical-engineer"
      ],
      "normal_return": "Working change, tests, and implementation evidence"
    },
    {
      "question": "Does the integrated result withstand independent inspection?",
      "active_owners": [
        "software-tester",
        "gameplay-and-ux-tester",
        "creative-asset-tester"
      ],
      "normal_return": "Defects, limitations, readiness evidence, and recommendation"
    },
    {
      "question": "Can this candidate safely become trusted live state?",
      "active_owners": [
        "devops-lead"
      ],
      "normal_return": "Promotion, rejection, rollback, or operational evidence"
    },
    {
      "question": "Do the administrative records, terminology, licences, provenance, and obligations match project reality?",
      "active_owners": [
        "studio-operations-and-compliance-lead",
        "studio-operations-coordinator",
        "licence-and-provenance-researcher"
      ],
      "normal_return": "Reconciled records, flagged drift, or unresolved exposure"
    },
    {
      "question": "Is the available evidence sufficient to accept, decline, constrain, or escalate the risk?",
      "active_owners": [
        "compliance-and-risk-reviewer",
        "studio-operations-and-compliance-lead"
      ],
      "normal_return": "Recommendation to Product Lead or Studio Lead"
    },
    {
      "question": "How should accepted work enter public view?",
      "active_owners": [
        "marketing-publishing-and-communications-lead"
      ],
      "normal_return": "Publication-ready communication package and release plan"
    },
    {
      "question": "How is the approved package carried into the public channel?",
      "active_owners": [
        "publisher"
      ],
      "normal_return": "Verified live publication and publication record"
    },
    {
      "question": "What is the public experiencing, asking, or repeatedly misunderstanding?",
      "active_owners": [
        "community-manager"
      ],
      "normal_return": "Bounded feedback and escalations to the responsible role"
    }
  ],
  "handoff_standard": [
    {
      "id": "intent",
      "name": "Intent",
      "description": "What should become true and why it matters."
    },
    {
      "id": "boundary",
      "name": "Boundary",
      "description": "What is fixed, excluded, delegated, or prohibited."
    },
    {
      "id": "context",
      "name": "Context",
      "description": "The smallest sufficient set of accepted facts and artifacts."
    },
    {
      "id": "expected-return",
      "name": "Expected return",
      "description": "The asset, specification, evidence, decision, or report required."
    },
    {
      "id": "return-path",
      "name": "Return path",
      "description": "Who receives success, contradiction, missing authority, or failure."
    }
  ],
  "recurring_artifacts": [
    {
      "name": "Studio direction or operating condition",
      "primary_owners": [
        "studio-lead"
      ],
      "purpose": "Establish the course and delegated boundaries"
    },
    {
      "name": "Product pass",
      "primary_owners": [
        "product-lead"
      ],
      "purpose": "Define outcome, scope, trade-offs, and acceptance surface"
    },
    {
      "name": "Research commission and report",
      "primary_owners": [
        "research-lead"
      ],
      "purpose": "Bound uncertainty and return inspectable evidence"
    },
    {
      "name": "Gameplay ruleset",
      "primary_owners": [
        "gameplay-lead",
        "gameplay-designer"
      ],
      "purpose": "Translate world capability into player-facing behaviour"
    },
    {
      "name": "Creative brief and selected assets",
      "primary_owners": [
        "creative-lead"
      ],
      "purpose": "Produce coherent expressive work for an accepted purpose"
    },
    {
      "name": "Technical direction",
      "primary_owners": [
        "tech-lead"
      ],
      "purpose": "Establish broad stack and integration choices"
    },
    {
      "name": "Structural design",
      "primary_owners": [
        "system-architect"
      ],
      "purpose": "Define ownership, interfaces, invariants, and failure behaviour"
    },
    {
      "name": "Task brief and implementation report",
      "primary_owners": [
        "senior-engineer",
        "technical-engineer"
      ],
      "purpose": "Bound execution and preserve verification evidence"
    },
    {
      "name": "Quality report",
      "primary_owners": [
        "software-tester",
        "gameplay-and-ux-tester",
        "creative-asset-tester"
      ],
      "purpose": "Provide independent readiness evidence"
    },
    {
      "name": "Release manifest and recovery record",
      "primary_owners": [
        "devops-lead"
      ],
      "purpose": "Describe and preserve the actual operational change"
    },
    {
      "name": "Licence and provenance reconciliation",
      "primary_owners": [
        "licence-and-provenance-researcher"
      ],
      "purpose": "Match recorded permission state to project reality"
    },
    {
      "name": "Operations and terminology report",
      "primary_owners": [
        "studio-operations-coordinator"
      ],
      "purpose": "Expose obligations, ownership gaps, and terminology drift"
    },
    {
      "name": "Compliance review",
      "primary_owners": [
        "compliance-and-risk-reviewer"
      ],
      "purpose": "Recommend accept, decline, constrain, or escalate"
    },
    {
      "name": "Publication package and record",
      "primary_owners": [
        "marketing-publishing-and-communications-lead",
        "publisher"
      ],
      "purpose": "Prepare, release, and verify public communication"
    },
    {
      "name": "Community report",
      "primary_owners": [
        "community-manager"
      ],
      "purpose": "Return significant public evidence to responsible roles"
    },
    {
      "name": "Pass report and post-mortem",
      "primary_owners": [
        "product-lead"
      ],
      "purpose": "Reconcile outcomes, evidence, failures, and workflow learning"
    }
  ],
  "return_paths": [
    {
      "trigger": "Studio direction or major commitment conflict",
      "returns_to": [
        "studio-lead"
      ]
    },
    {
      "trigger": "Product identity, priority, or feature trade-off",
      "returns_to": [
        "product-lead"
      ]
    },
    {
      "trigger": "Uncertainty blocking responsible action",
      "returns_to": [
        "research-lead"
      ]
    },
    {
      "trigger": "Player-facing rule or experience conflict",
      "returns_to": [
        "gameplay-lead"
      ]
    },
    {
      "trigger": "Creative direction, continuity, or cross-media conflict",
      "returns_to": [
        "creative-lead"
      ]
    },
    {
      "trigger": "Broad stack or lasting technical dependency",
      "returns_to": [
        "tech-lead"
      ]
    },
    {
      "trigger": "Structure, ownership, interface, or invariant conflict",
      "returns_to": [
        "system-architect"
      ]
    },
    {
      "trigger": "Implementation sequencing or technical review",
      "returns_to": [
        "senior-engineer"
      ]
    },
    {
      "trigger": "Bounded implementation problem",
      "returns_to": [
        "technical-engineer"
      ]
    },
    {
      "trigger": "Integrated defect or insufficient readiness evidence",
      "returns_to": [
        "software-tester",
        "gameplay-and-ux-tester",
        "creative-asset-tester"
      ]
    },
    {
      "trigger": "Deployment, recovery, or live-state safety",
      "returns_to": [
        "devops-lead"
      ]
    },
    {
      "trigger": "Account, obligation, terminology, licence, or provenance issue",
      "returns_to": [
        "studio-operations-and-compliance-lead"
      ]
    },
    {
      "trigger": "Material compliance uncertainty",
      "returns_to": [
        "compliance-and-risk-reviewer"
      ]
    },
    {
      "trigger": "Material business risk decision",
      "returns_to": [
        "product-lead",
        "studio-lead"
      ]
    },
    {
      "trigger": "Public claim, audience, channel, or release strategy",
      "returns_to": [
        "marketing-publishing-and-communications-lead"
      ]
    },
    {
      "trigger": "Channel execution or live publication defect",
      "returns_to": [
        "publisher"
      ]
    },
    {
      "trigger": "Community conduct or recurring public feedback",
      "returns_to": [
        "community-manager"
      ]
    }
  ],
  "completion_conditions": [
    "Stronger evidence that changes a decision",
    "An accepted rule, specification, asset, or implementation",
    "A verified internal or production candidate",
    "A recoverable trusted deployment",
    "A truthful and verified public release",
    "Actionable feedback returned to its responsible authority",
    "A post-mortem correction that improves the next loop"
  ],
  "source_path": "studio_workflow_map.md"
}