Inverse Organization · Public role model · Working baseline
The organization in full.
Thirty-one durable roles give Myriuna Worlds an explicit shape before those roles are distributed across a larger team.
Today, one accountable developer moves through the organization with role-specific AI assistance. Each card begins as a compact position in the whole and opens into the complete public role definition.
Model overview
Roles persist while occupants change.
The roles are not simulated employees or fragments of one personality. They are durable operating contexts with distinct purposes, boundaries, evidence standards, authority relationships, and return paths.
The same human currently inhabits every role through different human–AI pairings. As collaborators join, occupancy can be distributed without rebuilding the studio from private founder knowledge.
Occupants change; roles accumulate. Completed work returns to shared project state, while improvements to methods, standards, handoffs, and boundaries return to the role itself. The next occupant should begin further ahead.
Role explorer
Browse the organization by domain.
Every card is generated from the complete public dataset in roles.json. Open a card to inspect its mandate, scope, authority, review boundary, return path, and operating principles.
Executive authority
Executive
Myriuna Worlds is shaped as a small, modular studio in which work is divided into bounded roles without losing one shared product direction. The same person may currently perform many roles, but each role should retain its own purpose, authority boundary, assistant profile, context surface, and lightweight way of receiving and returning work. These roles are not merely job titles. They are human-readable control surfaces that allow a large and complex project to be handled through smaller, intelligible units of responsibility.
2 roles
Studio Lead
The Studio Lead keeps Myriuna Worlds coherent as a studio.
Open full role
Studio Lead
Mandate
The Studio Lead keeps Myriuna Worlds coherent as a studio. The role owns the studio’s overall direction, scope, major prioritization, risk acceptance, and final studio-level decisions. Its purpose is to keep the company focused and ensure that specialist work continues to serve the wider product and studio.
Scope and boundary
The Studio Lead does not own specialist execution. Engineering, operations, creative production, automation, licensing, publishing, and other recurring functions remain separate roles with their own responsibilities and evidence standards. One person may perform several roles, but the boundaries should remain clear enough to support future handoff and hiring.
Authority and review
Final authority remains with the human Studio Lead. Specialist findings and approvals must still come from the relevant roles; top-level authority cannot replace their evidence or completed workflows.
Return path
When major work returns, the Studio Lead receives a concise account of what was done, why that approach was chosen, and what risks or consequences remain. It may then accept the outcome, change the course, request further work, or leave execution with the responsible role.
Operating principle
- Set the course, delegate the passage, return when the course or the conditions materially change.
Public source: executive/studio_lead.md
Product Lead
The Product Lead keeps Myriuna coherent as a product.
Open full role
Product Lead
Mandate
The Product Lead keeps Myriuna coherent as a product. The role owns product identity, product scope, feature direction, major prioritization, and final product-level decisions. Its purpose is to keep development focused on a clear user experience and ensure that specialist work contributes to the same product rather than producing disconnected systems and assets.
Scope and boundary
The Product Lead does not own specialist execution. Engineering, creative production, operations, licensing, publishing, and other roles determine how work is carried out inside their own domains. One person may perform several roles, but specialist evidence and conclusions must still come from the relevant role.
Authority and review
Final product authority remains with the human Product Lead. This includes deciding what feature comes next, which approach best fits Myriuna, what is deliberately excluded, and when product considerations justify choosing one valid path over another. These decisions should be explainable through product intent, constraints, evidence, or accepted trade-offs rather than preference disguised as certainty.
Return path
When work returns, the Product Lead receives a concise account of what was done, why that approach was used, and what risks or consequences it carries for the product. The result may then be accepted, revised, rejected, deferred, or used to define the next product task.
Operating principle
- Choose the direction, define the outcome, delegate the execution, reconcile the product.
Public source: executive/product_lead.md
Operating domain 01
Research
Research is activated when uncertainty prevents productive implementation. Its purpose is not to accumulate knowledge indefinitely, but to investigate the specific question blocking progress until enough evidence exists for implementation to resume. When no meaningful blocker is present, the studio should favour building and testing the product over continuing research for its own sake.
2 roles
Research Lead
The Research Lead governs investigations into genuine blockers that cannot be responsibly resolved through ordinary product, technical, or implementation work.
Open full role
Research Lead
Mandate
The Research Lead governs investigations into genuine blockers that cannot be responsibly resolved through ordinary product, technical, or implementation work. The role distinguishes formal Research from routine task understanding, documentation lookup, library evaluation, and local technical investigation. Research begins when unresolved uncertainty materially prevents the studio from choosing, designing, or implementing safely.
Scope and boundary
The Research Lead converts the blocker into a bounded research question and defines the investigation’s scope, methods, evidence needs, resource limits, artifact requirements, and stopping conditions. Because research rarely has a simple pass-or-fail result, the role also controls interpretation: what is being tested now, what remains uncertain, which claims the evidence can support, and which worthwhile questions must be deferred rather than allowed to hijack the active loop.
Authority and review
The Research Lead directs and reviews the Researcher’s work but does not automatically authorize findings as project truth. It preserves distinctions between sources, observations, working interpretations, reviewed findings, and accepted knowledge. Review may establish that a finding is credible and useful; the commissioning Product Lead, Tech Lead, System Architect, or other responsible authority decides whether it becomes accepted direction or reusable project knowledge.
Return path
When research requires software, prototypes, test harnesses, datasets, or technical experiments, the Research Lead returns a bounded request to the appropriate Engineering roles rather than absorbing implementation into Research. The role closes the investigation once the original blocker has been reduced enough for responsible action, returning the evidence, interpretation, remaining uncertainty, limitations, recommendation, and deferred questions. Research supports development; it must not become an open-ended substitute for it.
Public source: specialist/research/research_lead.md
Researcher
The Researcher carries out bounded investigations into genuine studio blockers.
Open full role
Researcher
Mandate
The Researcher carries out bounded investigations into genuine studio blockers. The role gathers sources and observations, compares evidence, runs non-production experiments where appropriate, analyses results, and preserves an inspectable artifact trail throughout the work.
Scope and boundary
The Researcher has substantial freedom to pursue subquestions required to understand the main research question. When those subquestions materially expand the expected time, cost, or complexity of the investigation, the Researcher reports that change to the Research Lead rather than allowing the scope to grow invisibly.
Authority and review
The Researcher returns the full research record rather than only a polished conclusion. This includes evidence, observations, contradictions, uncertainty, limitations, unsuccessful approaches, possible interpretations, and relevant records of human learning or reasoning. The Research Lead is responsible for reviewing and shaping that material into a coherent research document.
Return path
When the investigation reveals a need for software implementation, a different research question, or a major expansion beyond the accepted scope, the Researcher stops and returns the issue to the Research Lead. The Research Lead then re-scopes the investigation, defers the question, or delegates bounded implementation work to Engineering.
Public source: specialist/research/researcher.md
Operating domain 02
Gameplay
Gameplay is the translation layer between what a Myriuna world is capable of and what a player can meaningfully do within it. Modules define the world’s rules, state, and behaviour. Gameplay determines how those realities become available, constrained, communicated, and experienced through play.
2 roles
Gameplay Lead
The Gameplay Lead owns the coherence and direction of the Gameplay stream.
Open full role
Gameplay Lead
Mandate
The Gameplay Lead owns the coherence and direction of the Gameplay stream. The role represents Gameplay during development-pass planning as an equal specialist voice, identifying how proposed product, module, creative, and technical decisions affect what the player can do and how the world responds through play.
Scope and boundary
The Gameplay Lead translates accepted product and module intent into bounded gameplay commissions. It directs the Gameplay Designer, determines which gameplay questions must be answered, and ensures that resulting rulesets remain consistent across player actions, limits, timing, consequences, feedback, and interaction with the wider Myriuna environment.
Authority and review
Gameplay specifications return to the Gameplay Lead for review before moving into Architecture and Engineering. The role checks whether they express the intended experience, remain compatible with accepted module rules, expose the necessary technical requirements, and are sufficiently clear to support structural design and bounded implementation.
Return path
The Gameplay Lead does not redefine product direction, module behaviour, system architecture, creative content, or implementation merely to complete a gameplay design. Conflicts return to the role that owns them, with the relevant gameplay consequences and viable options made clear.
Public source: specialist/gameplay/gameplay_lead.md
Gameplay Designer
The Gameplay Designer translates accepted module behaviour and product intent into a coherent player-facing ruleset.
Open full role
Gameplay Designer
Mandate
The Gameplay Designer translates accepted module behaviour and product intent into a coherent player-facing ruleset. The role defines available actions, prerequisites, limits, timing, consequences, feedback, edge cases, and examples of intended play. It does not create the underlying content or entity; it defines how something such as a dragon can exist and function within Myriuna’s accepted rules.
Scope and boundary
Gameplay Design serves as the translation surface between creative ideas and technical requirements. The Designer determines what an idea means in playable terms and returns a specification clear enough for the System Architect and Senior Engineer to identify affected systems, structural needs, and implementation tasks without prescribing ordinary code-level solutions.
Authority and review
The Gameplay Designer works within accepted product direction, module rules, and system capability. It does not redefine the module, invent missing technical behaviour, or alter product intent merely to make a ruleset complete. The Technical Engineer implements the resulting bounded task briefs, including isolated gameplay controllers or scripts where required.
Return path
When desired gameplay depends on a capability, rule, or creative decision that does not yet exist, the Gameplay Designer returns the gap to the appropriate owner. Product questions go to the Product Lead, structural questions to the System Architect, module questions to the module owner, and expressive questions to Creative.
Public source: specialist/gameplay/gameplay_designer.md
Operating domain 03
Creative
Creative exists to turn product intent, research, and practical studio needs into expressive material people can experience. This includes writing, imagery, video, audio, music, narration, sample worlds, scenarios, and other content used to explore or support the product. Creative is also a problem-solving layer: when another role lacks meaningful content with which to test an idea or system, Creative may produce bounded datasets, examples, or scenarios that make the problem concrete.
9 roles
Creative Lead
The Creative Lead owns the overall creative direction of commissioned work and the point where Myriuna’s media forms come together.
Open full role
Creative Lead
Mandate
The Creative Lead owns the overall creative direction of commissioned work and the point where Myriuna’s media forms come together. The role coordinates prose, dialogue, speech, music, sound, story, visual design, animation, and other expressive material so that they form a coherent experience. The Product Lead governs the product across all studio streams; the Creative Lead performs a comparable coordinating function within Creative.
Scope and boundary
The Creative Lead translates accepted product or project intent into creative briefs and directs the relevant creative disciplines. These briefs should remain proportionate to the work and may be deliberately lightweight—for example, a bounded request to generate a broad cast of villagers rather than an engineering-style specification. Creative work needs clear intent, useful boundaries, and an expected return, but not procedural detail that constrains productive exploration.
Authority and review
Creative outputs return to the Creative Lead for review across tone, continuity, purpose, usability, and cross-media fit. The role may accept the work, request another creative pass, combine outputs from several disciplines, or return material that does not serve the commissioned intent. Final product acceptance remains with the role that commissioned the creative work.
Return path
When creative work encounters a conflict involving scope, technology, cost, licensing, quality requirements, or another studio domain, the Creative Lead returns the conflict to the commissioning role with the relevant evidence and options. That role determines how the work should be rescoped or which other specialist must become involved; Creative does not quietly redefine the commission simply to make it pass.
Public source: specialist/creative/creative_lead.md
Animator
The Animator creates moving-image assets from approved still images or visual source material.
Open full role
Animator
Mandate
The Animator creates moving-image assets from approved still images or visual source material. The role is responsible for what moves, how it moves, how the camera behaves, and how the resulting clip preserves the subject, scene, visual style, and intended meaning of the source.
Scope and boundary
The Animator has meaningful creative freedom, but within a tighter frame than the Visual Designer. Animation always places one thing in relation to another: a subject to its environment, motion to timing, camera movement to composition, and action to narrative intent. The role may iterate on motion prompts, models, duration, framing, frame rate, and movement details, but it does not redesign the underlying image or change the purpose of the scene.
Authority and review
The Animator returns selected moving-image assets with proportionate production records, known artifacts, continuity notes, and any reusable learning needed for later work. Automatic metadata should carry technical details wherever the production tools already preserve them.
Return path
When the requested animation cannot be completed without changing the accepted visual design, narrative intent, technical limits, or scope of the commission, the Animator stops and returns the conflict to the role that created the task. The work may then be clarified, rescoped, or divided into several bounded animation tasks.
Public source: specialist/creative/animator.md
Audio Producer
The Audio Producer creates and assembles finished audio for Myriuna and the studio, working from raw recordings, written material, prompts, generated assets, or combinations of these.
Open full role
Audio Producer
Mandate
The Audio Producer creates and assembles finished audio for Myriuna and the studio, working from raw recordings, written material, prompts, generated assets, or combinations of these. The role carries production from source to exported result, including voice and TTS generation, music, ambience, sound effects, editing, cleanup, timing, processing, synchronization, mixing, and mastering.
Scope and boundary
The Writer or commissioning role provides the underlying prose, meaning, and purpose. The Audio Producer may rework that material into a form suited to listening rather than reading by adjusting structure, phrasing, rhythm, pauses, delivery, and repetition, while preserving the accepted message, character, scene intent, and claim.
Authority and review
The Audio Producer has broad creative freedom over voices, models, prompts, generation settings, instrumentation, sound design, performance treatment, processing, and mix decisions within the brief. The Creative Lead is responsible for ensuring that available tools and models are appropriate for the intended use; licensing decisions are not pushed into the production role during execution.
Return path
The Audio Producer returns finished audio with proportionate production records, known artifacts, and reusable learning. Generated audio should preserve model, version, prompt, and workflow details in asset metadata wherever supported. Live recordings require separate records for performers, permissions, source ownership, and permitted use before they can become approved production assets.
Public source: specialist/creative/audio_producer.md
Module Creative Director
The Module Creative Director becomes active when creative production across multiple modules, specialists, or concurrent bodies of work can no longer be directed personally by the Creative Lead without reducing…
Open full role
Module Creative Director
Mandate
The Module Creative Director becomes active when creative production across multiple modules, specialists, or concurrent bodies of work can no longer be directed personally by the Creative Lead without reducing agility. At the studio’s current scale, these responsibilities remain with the Creative Lead and the role should not be inserted into ordinary production.
Scope and boundary
The Module Creative Director owns the creative direction of one assigned module. Within that module, the role defines and maintains its visual language, atmosphere, tone, continuity, and relationships across characters, environments, objects, lighting, composition, animation, voice, audio, prose, and other expressive media.
Authority and review
The role also performs the module-specific Narrative Systems Designer function. It determines how the module’s rules, identity, themes, and world conditions should become perceptible across the media stack, then translates that direction into coherent commissions for the relevant creative and gameplay roles. Production specialists remain responsible for creating the actual assets.
Return path
The Creative Lead retains direction across the full Myriuna product suite and determines how modules relate to the wider product. Conflicts involving product identity, shared systems, cross-module consistency, scope, or studio-wide creative direction return to the Creative Lead rather than being resolved solely within one module.
Public source: specialist/creative/module_creative_director.md
Narrative Systems Designer
The Narrative Systems Designer defines how a module’s identity and narrative potential operate across the full media stack.
Open full role
Narrative Systems Designer
Mandate
The Narrative Systems Designer defines how a module’s identity and narrative potential operate across the full media stack. The role examines what the module offers narratively, why those possibilities matter, and how its tone, themes, rules, and world conditions should become perceptible through prose, visuals, voice, animation, audio, and gameplay.
Scope and boundary
The role produces module-level narrative specifications rather than finished scenes or media assets. These specifications may define narrative principles, expressive styles, continuity requirements, example situations, emotional qualities, cross-media relationships, and the ways module behaviour should influence what the player sees, hears, reads, and experiences.
Authority and review
The Narrative Systems Designer works between Product, Creative, Gameplay, Architecture, and the individual production roles. It may establish that a dark science-fiction module requires particular relationships between language, visual atmosphere, vocal delivery, sound, and playable behaviour, but the Writer, Visual Designer, Audio Producer, Animator, and Gameplay Designer create the corresponding work.
Return path
When narrative intent exposes a missing rule, structural limitation, product conflict, or production problem, the role returns it to the domain that owns it. Product direction goes to the Product Lead, structural issues to the System Architect, gameplay issues to Gameplay, and medium-specific problems to the relevant creative role.
Public source: specialist/creative/narrative_systems_designer.md
Video Editor
The Video Editor assembles approved source media into a coherent finished video.
Open full role
Video Editor
Mandate
The Video Editor assembles approved source media into a coherent finished video. The role works with animation, still images, narration, dialogue, music, ambience, sound effects, titles, and other supplied assets, creating the cuts, fades, loops, transitions, synchronization, pacing, and final sequence.
Scope and boundary
The Video Editor has broad freedom over assembly within the accepted vision of the Creative Lead or Publishing role that commissioned the work. It may determine shot order, timing, rhythm, transitions, repetition, and edit structure, but it does not change the underlying message, story, visual identity, setting, or purpose of the commission.
Authority and review
The Video Editor does not generate replacement creative assets. When the supplied material cannot support the intended video, the role returns a clear request for what is missing, such as another shot, voice line, image, animation, or audio element. Work resumes once the required source material has been added.
Return path
The Video Editor returns the finished video together with proportionate edit records, known limitations, and any reusable lessons needed for later work. Changes that would require new creative direction or different source content return to the commissioning role rather than being disguised through editing.
Public source: specialist/creative/video_editor.md
Visual Designer
The Visual Designer creates and develops visual concepts, characters, environments, objects, compositions, style explorations, and finished image assets for Myriuna and the studio.
Open full role
Visual Designer
Mandate
The Visual Designer creates and develops visual concepts, characters, environments, objects, compositions, style explorations, and finished image assets for Myriuna and the studio. Visual work often becomes the foundation for later animation, video, voice, music, and cross-media production, and may serve as the first strong point of contact between the work and its audience.
Scope and boundary
The Visual Designer has broad freedom to explore models, prompts, settings, source images, compositions, styles, and visual details within the accepted brief. Local iteration should remain creatively open so the role can discover strong solutions rather than merely execute predetermined images. Changes to established identity, continuity, module truth, intended function, or the purpose of the commission must be returned rather than silently introduced.
Authority and review
The Creative Lead is responsible for ensuring that the Visual Designer’s available workspace contains tools and models appropriate for the intended use. The Designer may treat those approved tools as available for local creation and experimentation. Licensing, commercial-use restrictions, and distinctions between finished-asset generation and direct model or API exposure are defined before the commission reaches the role, rather than being solved by the artist during production.
Return path
The Visual Designer returns the selected work together with proportionate production records and any continuity or learning notes needed for later use. Where model, version, prompt, and workflow information are already preserved automatically in asset metadata, the role should rely on that infrastructure and remain focused primarily on making strong visual work.
Public source: specialist/creative/visual_designer.md
Voice Director
The Voice Director owns coherence across Myriuna’s cast of voices.
Open full role
Voice Director
Mandate
The Voice Director owns coherence across Myriuna’s cast of voices. The role translates accepted character, module, and creative direction into recognizable vocal identities that remain consistent across scenes, production passes, and recurring appearances.
Scope and boundary
The Voice Director prepares bounded voice briefs covering qualities such as vocal character, accent, pronunciation, rhythm, emotional range, delivery, and relationships between voices in the wider cast. These are broad production guidelines rather than rigid performance rules, allowing the Audio Producer to work within the practical strengths and limitations of available TTS models or performers.
Authority and review
Completed voice work returns to the Voice Director for review. The role assesses character fit, intelligibility, continuity, emotional credibility, technical usability, and consistency with the commissioned scene. It may accept the result, request another production pass, refine the brief, or divide work into smaller tasks when the original commission proves too broad.
Return path
The Voice Director does not write the underlying prose or produce, edit, and master the audio. Problems involving wording, dialogue, narration, character language, or narrative meaning return to the Creative Lead, who determines whether revised writing is required. Production execution remains with the Audio Producer, while questions involving consent, licensing, or usage rights return to Studio Operations & Compliance. Broader character or module conflicts return to the Creative Lead or Module Creative Director.
Public source: specialist/creative/voice_director.md
Writer
The Writer creates language-based material for Myriuna and the studio, including characters, histories, dialogue, narration, world prose, scenarios, module content, website text, development articles, and publi…
Open full role
Writer
Mandate
The Writer creates language-based material for Myriuna and the studio, including characters, histories, dialogue, narration, world prose, scenarios, module content, website text, development articles, and public-facing descriptions. The commission determines the audience, voice, purpose, and required form.
Scope and boundary
The Writer has broad creative freedom within the accepted claim and brief. It may shape language, tone, characterization, imagery, and local detail, but it must not overclaim, manufacture hype, misrepresent product capability, or silently change established continuity, module rules, product truth, or the purpose of the commission.
Authority and review
The Writer returns the completed work in the form required by the task. Where the work exposes reusable knowledge, assumptions, continuity decisions, or supporting principles, it also returns a compressed supporting document so later roles can understand how the material was constructed and what must be preserved.
Return path
Complex writing may function as operational creative context rather than merely finished prose. Material such as a module’s rules for magic, the consequences of a world-changing event, or a seed history for an LLM may need to define enough coherent reality to become an initial context packet from which the world can begin behaving consistently.
Public source: specialist/creative/writer.md
Operating domain 04
Technical
Technical designs, builds, integrates, and maintains the systems that make Myriuna work. This includes architecture, data models, APIs, interfaces, development environments, AI-worker integration, asset integration, and deployable builds. Technical creates the working system; Quality tests whether it is ready, and DevOps controls its promotion into live operation.
4 roles
Tech Lead
The Tech Lead owns the broad technical direction of Myriuna.
Open full role
Tech Lead
Mandate
The Tech Lead owns the broad technical direction of Myriuna. The role decides which languages, frameworks, libraries, runtimes, services, and development approaches are appropriate for the work, and maintains coherence across those choices. Its central question is whether the studio is using the right technical tools and whether the wider system can behave reliably within the resulting stack.
Scope and boundary
The Tech Lead is not primarily responsible for day-to-day implementation or local code decisions. Detailed system structures belong to the System Architect, while bounded implementation belongs to Engineering. The Tech Lead becomes active when a decision affects multiple systems, establishes a lasting technical dependency, changes the development approach, or determines how major parts of the stack communicate—for example, how CLE accesses authentication values or how the LLM and TTS systems synchronize.
Authority and review
Technical choices must remain subordinate to product needs. The Tech Lead may propose a framework, platform, or integration approach and explain its costs, constraints, risks, and benefits, but product-facing trade-offs return to the Product Lead. A technically attractive choice should not redefine Myriuna merely because it is interesting or convenient to build.
Return path
The Tech Lead returns clear technical direction: the selected approach, why it fits the problem, which constraints it creates, and which questions must move to Product, Architecture, Research, or another role. It does not decide visual presentation, write ordinary feature code by default, or treat technical preference as product authority.
Public source: specialist/technical/tech_lead.md
Senior Engineer
The Senior Engineer turns accepted architecture into bounded, implementation-ready work.
Open full role
Senior Engineer
Mandate
The Senior Engineer turns accepted architecture into bounded, implementation-ready work. The role breaks a pass or Block into sequenced task briefs such as environment setup, configuration, test preparation, component construction, integration, and verification. It defines enough implementation detail for a Technical Engineer or coding agent to work safely without redesigning the underlying system.
Scope and boundary
The Senior Engineer owns implementation coordination rather than product direction, stack selection, or architecture. The Architect defines the data, structures, boundaries, and permitted change; the Senior Engineer determines how that accepted design should be built in manageable steps. Questions outside that boundary return to the Product Lead, Tech Lead, System Architect, Research, or another appropriate role.
Authority and review
Completed task briefs return to the Senior Engineer for technical review. The role checks scope, behaviour, tests, maintainability, integration, evidence, and conformity with the accepted brief. It may accept the work, return it for correction, or steer implementation away from an obvious failure, but it should not conceal a missing design decision by improvising one through code.
Return path
When all task briefs in a pass are complete, the Senior Engineer consolidates their results into a pass report describing what was implemented, how it was verified, what changed, and what remains uncertain. The Product Lead then accepts the completed pass, rejects it, or returns it for further work.
Public source: specialist/technical/senior_engineer.md
System Architect
The System Architect turns an accepted development pass into a concrete structural design.
Open full role
System Architect
Mandate
The System Architect turns an accepted development pass into a concrete structural design. The role identifies exactly which parts of the system must change and defines the relevant boundaries, data ownership, interfaces, authority flow, invariants, dependencies, and failure behaviour before implementation tasks are written.
Scope and boundary
The System Architect does not choose the product goal or the broader technology stack. Product direction belongs to the Product Lead, while major language, framework, library, and platform choices belong to the Tech Lead. Research may supply missing evidence or test uncertain approaches; the Architect converts accepted findings into a system design that Engineering can safely act upon.
Authority and review
Once the architecture is sufficiently defined for bounded task briefs to be created, the Architect’s normal work on that pass is complete. The Senior Engineer prepares or guides the implementation work, and the Technical Engineer executes it. The Architect does not remain inside ordinary implementation, review, or day-to-day steering.
Return path
The System Architect re-enters when Engineering discovers a genuine structural conflict, an unanswered architectural question, or evidence that the accepted design cannot work as intended. The role then re-evaluates the affected structure and returns the missing decision or revised constraints without taking over implementation.
Public source: specialist/technical/system_architect.md
Technical Engineer
The Technical Engineer owns implementation of accepted, bounded task briefs.
Open full role
Technical Engineer
Mandate
The Technical Engineer owns implementation of accepted, bounded task briefs. The role changes code and configuration, writes and runs tests, integrates approved components, verifies the requested behaviour, and returns a clear completion report with supporting evidence.
Scope and boundary
The Technical Engineer works with substantial freedom over ordinary implementation details already permitted by the brief, but the important terms should be mapped before execution begins. Product behaviour, architecture, data shape, technology choices, scope, authority boundaries, and destructive actions are not silently re-decided during implementation.
Authority and review
When a task cannot be completed without violating or changing its accepted terms, the brief becomes an invalid instruction for the Technical Engineer—an “illegal order” within the role model. The Technical Engineer stops, preserves the current state, and returns the conflict or missing decision rather than inventing a solution through code.
Return path
The Senior Engineer receives completed work and implementation blockers. The Technical Engineer may report observations and suggest possible options, but does not resolve questions that fall outside the accepted implementation boundary.
Public source: specialist/technical/technical_engineer.md
Operating domain 05
Quality
Quality exists to test whether a candidate meets the studio’s accepted standard for its actual purpose. It applies across technical, creative, operational, and public-facing work, but it does not apply identically in every domain. The operating principle remains stable while the review lens changes according to the work being examined.
3 roles
Creative Asset Tester
The Creative Asset Tester independently inspects completed asset sets, production cycles, patches, and release candidates after the normal Creative workflow has already maintained and reviewed individual work.
Open full role
Creative Asset Tester
Mandate
The Creative Asset Tester independently inspects completed asset sets, production cycles, patches, and release candidates after the normal Creative workflow has already maintained and reviewed individual work. The role is not inserted into every asset task; it examines whether the assembled body of creative material remains coherent and ready for its intended use.
Scope and boundary
The Tester evaluates prose, images, animation, video, voice, and audio for technical defects, continuity failures, fidelity to the accepted brief, cross-media consistency, export quality, and suitability within the final production context. The role tests and reports only. It does not revise assets, replace creative direction, or judge work according to personal taste.
Authority and review
Routine defects discovered during production return through the established Creative workflow to the responsible role. Release-based testing produces a consolidated report describing what was examined, which problems were found, what could not be verified, and any risks or limitations affecting readiness.
Return path
Questions involving licensing, permissions, or provenance remain with Studio Operations & Compliance. The Creative Asset Tester may identify missing clearance or metadata as a release dependency, but does not interpret licences or authorize use.
Public source: specialist/quality/creative_asset_tester.md
Gameplay & UX Tester
The Gameplay & UX Tester independently evaluates completed gameplay cycles, patches, and release candidates through actual play.
Open full role
Gameplay & UX Tester
Mandate
The Gameplay & UX Tester independently evaluates completed gameplay cycles, patches, and release candidates through actual play. The role examines the user-facing experience rather than reviewing gameplay specifications, system architecture, or engineering implementation.
Scope and boundary
The Tester evaluates whether rules behave as intended, actions and consequences are understandable, feedback is sufficient, controls and interaction flows are usable, and difficulty or friction supports the intended experience. Testing also covers the combined feel and tone of the product, including how art, audio, prose, pacing, and interface design work together during play.
Authority and review
The role pays particular attention to experience patterns that may not appear defective in isolation but become disruptive in practice. This includes repeated actions, playstyle-specific friction, awkward navigation, poor information placement, tonal inconsistencies, and interface decisions that become burdensome during normal use.
Return path
The Gameplay & UX Tester returns a test report and readiness recommendation describing what was tested, the experiences observed, significant defects or friction, affected playstyles, unresolved risks, and suggested priorities. The role does not redesign or repair the product; findings return through the appropriate Gameplay, Creative, Product, or Technical workflow.
Public source: specialist/quality/gameplay_UX_tester.md
Software Tester
The Software Tester performs independent inspection of the wider codebase after a development pass or other meaningful body of technical work has been completed.
Open full role
Software Tester
Mandate
The Software Tester performs independent inspection of the wider codebase after a development pass or other meaningful body of technical work has been completed. Task-level testing and technical review remain part of Engineering; this role examines how the completed changes behave together and whether they have introduced problems beyond the boundaries of the individual task briefs.
Scope and boundary
The Software Tester evaluates observable behaviour, regressions, integrations, data integrity, permissions, failure handling, edge cases, and reproducibility across the affected system. The role works from the accepted pass, architecture, implementation reports, and available evidence, but tests the resulting software independently rather than assuming the supplied evidence is sufficient.
Authority and review
The Software Tester records defects, contradictions, missing evidence, and areas that could not be verified. Routine findings return to the Senior Engineer for correction and targeted retesting. The Tester does not redesign the system, repair the implementation, or replace Engineering’s responsibility for code quality and maintainability.
Return path
For broader codebase inspections, the Software Tester returns a consolidated review that becomes part of the main pass report. Systemic defects, recurring weaknesses, or findings that challenge the accepted architecture or technical direction are made visible for the responsible Technical role rather than being reduced to isolated bug reports.
Public source: specialist/quality/software_tester.md
Operating domain 06
DevOps
DevOps exists to manage the boundary between a working development build and the trusted live state of Myriuna. Technical creates the software, configuration requirements, migrations, and deployable build. DevOps determines whether that build can safely become live, performs the promotion, verifies the result in the target environment, and preserves the previous trusted state so that promotion does not destroy the studio’s ability to recover.
1 role
DevOps Lead
The DevOps Lead owns preservation, deployment, and operational verification across Myriuna’s environments.
Open full role
DevOps Lead
Mandate
The DevOps Lead owns preservation, deployment, and operational verification across Myriuna’s environments. The role maintains recoverable system, database, configuration, application, asset, and release state; selects the correct deployment path for each kind of change; and determines whether the resulting environment can be trusted for its intended use.
Scope and boundary
The DevOps Lead executes promotions, deployments, rollbacks, restorations, transfers, and archival work using the mechanism appropriate to the affected layer. It may retire obsolete snapshots, copies, and recovery states under established studio guidelines, while preserving enough verified redundancy to protect meaningful work and live data.
Authority and review
Backups are not considered reliable merely because they were created. The DevOps Lead periodically verifies their integrity, performs restoration tests, checks storage health, and creates replacement copies when redundancy has been weakened by failure, corruption, age, or environmental change.
Return path
Operational testing covers deployment and runtime evidence such as machine identity, services, bindings, configuration, database access, authentication surfaces, worker connections, application startup, smoke tests, and recovery procedures. Feature behaviour and product acceptance remain with Engineering and Quality. When operational evidence is insufficient or a deployment cannot proceed safely, the DevOps Lead halts or reverses the change and returns the blocker to the responsible role rather than repairing unrelated product work.
Public source: specialist/devops/dev_ops_lead.md
Operating domain 07
MPC
Marketing, Publishing & Communications turns the real work of Myriuna Worlds into a coherent public presence. Development, Research, Creative, and other specialist roles produce the underlying material; this layer selects, adapts, contextualizes, and presents suitable parts of that work. Public output should emerge from the project rather than becoming a separate media operation that competes with it.
4 roles
Marketing, Publishing & Communications Lead
The Marketing, Publishing & Communications Lead turns accepted studio output, development passes, campaigns, and communication goals into material suitable for public consumption.
Open full role
Marketing, Publishing & Communications Lead
Mandate
The Marketing, Publishing & Communications Lead turns accepted studio output, development passes, campaigns, and communication goals into material suitable for public consumption. The role determines what must be communicated, to whom, through which channel, in what form, and under which conditions so that development work can become announcements, development articles, public-facing speech, demonstrations, campaigns, and other published media.
Scope and boundary
The MPC Lead converts these goals into bounded commissions for the relevant execution roles. Writers, Visual Designers, Animators, Audio Producers, Video Editors, and other specialists create the required materials; the MPC Lead coordinates their work, supplies the audience and publication context, and ensures that the resulting pieces form a coherent public presentation rather than a collection of disconnected assets.
Authority and review
Completed work returns to the MPC Lead for review across factual accuracy, audience fit, clarity, tone, timing, channel requirements, and consistency with the studio, product, or founder voice being used. The role may accept the material, request another pass, alter the publication plan, or return unsupported claims and missing evidence to the responsible studio role. It does not manufacture progress, capabilities, certainty, or public narratives that the underlying work cannot support.
Return path
The MPC Lead owns the publishing pipeline, review standards, release controls, and appropriate automation around them. As those systems mature, routine material may be published under delegated authority without individual approval for every release. Sensitive announcements, exceptional claims, legal or reputational risks, and changes to the studio’s public position return to the appropriate executive or specialist authority.
Public source: specialist/marketing-publishing-communications/MPC_lead.md
Community Manager
The Community Manager becomes active with the official launch of Myriuna’s first public media package, including the website, product reveal or announcement, and initial social-channel presence.
Open full role
Community Manager
Mandate
The Community Manager becomes active with the official launch of Myriuna’s first public media package, including the website, product reveal or announcement, and initial social-channel presence. The role owns the ongoing relationship between the studio and the public spaces that form around the product.
Scope and boundary
The Community Manager handles day-to-day community communication, moderation, conduct enforcement, recurring updates, questions, events, feedback collection, and the identification of repeated concerns or emerging issues. Where Myriuna uses live public formats such as Twitch streams, the Community Manager manages the live audience, conversation flow, moderation, and community-facing coordination.
Authority and review
The role communicates within policies, positions, and escalation boundaries established by the MPC Lead and other responsible authorities. It does not create policy, promise features, redefine product direction, or improvise new public positions. Product feedback returns to Product, technical issues to the appropriate technical role, and serious safety, legal, conduct, or reputational concerns to Studio Operations & Compliance or the MPC Lead.
Return path
The Community Manager preserves proportionate records of significant feedback, moderation actions, recurring questions, community sentiment, and unresolved issues. Its purpose is not merely to broadcast studio messages, but to maintain a clear, stable, and responsive communication surface between Myriuna Worlds and its developing community.
Public source: specialist/marketing-publishing-communications/community_manager.md
Marketing & Communications Specialist
The Marketing & Communications Specialist executes bounded campaigns and communication tasks established by the MPC Lead.
Open full role
Marketing & Communications Specialist
Mandate
The Marketing & Communications Specialist executes bounded campaigns and communication tasks established by the MPC Lead. The role turns approved studio material into audience-facing packages such as announcements, development articles, newsletters, launch pages, press material, social posts, community updates, and responses to public enquiries.
Scope and boundary
The Specialist has freedom over presentation, emphasis, sequencing, audience adaptation, and campaign execution within the accepted brief. It may commission supporting work from Creative roles and assemble the resulting text, images, audio, and video into a coherent communication package. Overall goals, claims, public positioning, review standards, and release strategy remain with the MPC Lead.
Authority and review
The role also maintains ongoing communication with audiences, communities, media contacts, and other public participants. It responds within established boundaries, preserves the appropriate studio, product, or founder voice, and returns sensitive questions, unsupported claims, reputational risks, or requests requiring a new public position to the MPC Lead.
Return path
The Specialist returns completed, publication-ready packages with their intended channels, timing, source materials, and relevant communication records. Final platform preparation and release remain with the Publisher unless the MPC Lead has explicitly combined those responsibilities for a bounded task.
Public source: specialist/marketing-publishing-communications/MPC_specialist.md
Publisher
The Publisher carries accepted communication material into the public channel.
Open full role
Publisher
Mandate
The Publisher carries accepted communication material into the public channel. The role prepares and releases content across websites, social platforms, newsletters, video services, and other publication surfaces, handling formatting, metadata, captions, scheduling, uploads, platform settings, and final release checks.
Scope and boundary
The Publisher may make minor channel-specific adaptations required for successful publication, including resizing, compression, subtitle formatting, link placement, excerpts, thumbnails, and technical packaging. Changes to the underlying claim, meaning, creative direction, audience strategy, or campaign intent return to the MPC Lead.
Authority and review
The Publisher verifies the live result after release, confirms that media, links, formatting, access settings, and platform behaviour are correct, and corrects operational publication errors within the accepted package. Missing, damaged, or unsuitable source material is returned to the MPC Lead rather than replaced through newly invented content.
Return path
The Publisher preserves proportionate publication records, including the released version, date, channel, destination, URLs, relevant platform settings, and any corrections or known limitations. The role operates within the publishing pipeline, review standards, and delegated release authority established by the MPC Lead.
Public source: specialist/marketing-publishing-communications/publisher.md
Operating domain 08
SOC
Studio Operations & Compliance exists to keep Myriuna Worlds operationally legitimate as its work moves from personal experimentation toward sustained production. It maintains the organizational surfaces and evidence that allow the studio to know what it owns, what it may use, who controls important accounts, how production material was created, and which obligations accompany that material. Its scope currently includes domains and email, studio-owned accounts, vendors, software and model licences, attribution requirements, provenance, approval records, and preservation of important business records.
4 roles
Studio Operations & Compliance Lead
The Studio Operations & Compliance Lead coordinates the administrative, permission, compliance, and terminology framework around Myriuna Worlds.
Open full role
Studio Operations & Compliance Lead
Mandate
The Studio Operations & Compliance Lead coordinates the administrative, permission, compliance, and terminology framework around Myriuna Worlds. Acting as the central connection point across the studio, the role ensures that accounts, vendors, licences, provenance, recurring obligations, accepted terminology, and unresolved compliance questions remain visible and consistently handled across projects.
Scope and boundary
The Lead directs research and maintenance concerning the tools, models, assets, services, datasets, and performers used by the studio. It ensures that relevant terms and permissions are recorded, identifies which conditions activate under experimentation, production, publication, commercial use, redistribution, or direct service exposure, and keeps those conclusions current when either the terms or intended use changes.
Authority and review
When a proposed use raises compliance uncertainty, the Lead gathers the relevant evidence and determines whether the question is clear enough for responsible business judgment. It returns a documented recommendation and available options to the Product Lead or Studio Lead, who accepts or declines material business risk. Questions requiring professional interpretation are prepared for external legal or specialist advice rather than being answered through unsupported internal assumptions.
Return path
The Lead may pause production, deployment, publication, or use when permissions, ownership, terminology, or compliance conditions are materially unclear. Work resumes only once the issue has been clarified, constrained, declined, or escalated appropriately. The role does not replace legal counsel or specialist domain authority; it ensures that uncertainty cannot quietly pass into studio operations and create disproportionate financial, contractual, or operational exposure.
Public source: specialist/studio-operations-compliance/studio_operations_compliance_lead.md
Compliance & Risk Reviewer
The Compliance & Risk Reviewer examines specific proposed uses, releases, contracts, workflows, and operating conditions where the studio needs a clear decision about exposure.
Open full role
Compliance & Risk Reviewer
Mandate
The Compliance & Risk Reviewer examines specific proposed uses, releases, contracts, workflows, and operating conditions where the studio needs a clear decision about exposure. The role combines the intended use with evidence supplied by Licence & Provenance, DevOps, Product, Studio Operations, and other relevant domains so the question is assessed against project reality rather than abstract assumptions.
Scope and boundary
The Reviewer identifies applicable obligations, unresolved ambiguity, likely consequences, available safeguards, and the limits of the studio’s current knowledge. It distinguishes operational judgment from questions requiring professional interpretation and preserves the evidence and reasoning used in the review.
Authority and review
Each review returns one of four recommendations: accept, decline, constrain, or escalate externally. The recommendation states what is being assessed, which conditions apply, what uncertainty remains, what consequences may follow, and—when escalation is required—the precise question that should be taken to an external legal or specialist adviser.
Return path
The Reviewer may flag work for immediate pause when continued use, deployment, publication, or contractual commitment could create serious financial, legal, operational, or reputational exposure. The Studio Operations & Compliance Lead coordinates the response, while the Product Lead or Studio Lead makes the final decision to accept or decline material business risk.
Public source: specialist/studio-operations-compliance/compliance_risk_reviewer.md
Licence & Provenance Researcher
The Licence & Provenance Researcher investigates the models, tools, datasets, assets, services, performers, and other sources currently used by Myriuna Worlds or being considered for future use.
Open full role
Licence & Provenance Researcher
Mandate
The Licence & Provenance Researcher investigates the models, tools, datasets, assets, services, performers, and other sources currently used by Myriuna Worlds or being considered for future use. The role locates authoritative terms, establishes provenance where possible, and determines which conditions activate under experimentation, internal production, publication, commercial use, redistribution, direct API exposure, revenue thresholds, or other relevant forms of use.
Scope and boundary
The Researcher preserves the evidence behind each finding. This includes saving dated copies of licences and terms, recording their source and applicable version, and updating the studio’s licence and provenance spreadsheets with practical fields such as permitted uses, API restrictions, attribution requirements, commercial conditions, revenue-dependent costs, redistribution limits, and known uncertainties.
Authority and review
Each development pass or release provides a checkpoint for comparing the recorded state with project reality. The Researcher verifies that the models, versions, services, assets, and intended uses actually present in the project match the maintained records, and flags missing evidence, changed terms, undocumented dependencies, or uses that have crossed into a different licensing condition.
Return path
The role separates confirmed terms, operational interpretation, unresolved ambiguity, and suggested classifications in its reports. It does not approve use, accept business risk, impose final restrictions, or provide legal advice. Those decisions remain with the Studio Operations & Compliance Lead and the responsible Product or Studio Lead, with external escalation where the evidence is not sufficient for a responsible internal decision.
Public source: specialist/studio-operations-compliance/license_provenance_researcher.md
Studio Operations Coordinator
The Studio Operations Coordinator maintains the studio’s day-to-day administrative records and recurring obligations.
Open full role
Studio Operations Coordinator
Mandate
The Studio Operations Coordinator maintains the studio’s day-to-day administrative records and recurring obligations. The role tracks domains, accounts, subscriptions, vendors, renewals, access ownership, contract records, and other operational dependencies so that responsibilities, deadlines, and current conditions remain visible.
Scope and boundary
The Coordinator also maintains the accepted terminology register across studio projects. It records approved terms and definitions, checks their use across documents and systems, and identifies inconsistencies, outdated references, or terminology drift. Specialist roles remain responsible for defining terminology within their own authority.
Authority and review
The role inspects, records, and reports rather than changing established systems independently. When an account, term, contract reference, ownership record, or legacy configuration appears outdated, the Coordinator flags the required update and routes it to the responsible role. This prevents an apparently simple administrative correction from breaking technical, contractual, or legacy dependencies.
Return path
The Coordinator executes established operational decisions and reports missing records, approaching obligations, inconsistencies, and unresolved ownership. Licence interpretation, compliance recommendations, material risk decisions, and escalation to external experts remain with the Studio Operations & Compliance Lead.
Public source: specialist/studio-operations-compliance/studio_operations_coordinator.md
Unified workflow
Work moves according to the question being answered.
The model is a routing map rather than a mandatory conveyor belt. Only the roles required by the current question become active, and the narrowest role capable of answering it should remain in control.
The detailed workflow remains available as structured public data in workflow.json.
Handoffs and review
Crossing a boundary should become visible.
A role stops when the dominant question leaves its authority. It returns the work rather than silently expanding its mandate.
Working boundary
A real structure, still open to reality.
This is the current public baseline of an organization in active use. Its roles are explicit enough to govern present work, but they are not protected from production evidence or future collaborators.
When an occupant discovers a stronger method, a missing boundary, an unnecessary handoff, or a false assumption, that learning should improve the role rather than disappear with the person.