Miyu creates a neon city scene on a drawing tablet surrounded by visual authoring workspaces.
Engineering / Knowledgebase

TECHNICAL NOTE

Authoring // authoring.scene-editor

How Drakima VN Maker organizes authoring

VN Maker connects project identity, story, scenes, presentation, playtesting and publication while preserving exact retained releases.

Production Practitioner Updated 2026-10-30

01 / WHAT

What it does

Staff use dedicated Maker workspaces for story structure, scene layout, dialogue, choices, character resources, combat where authored, media and release preparation. Copilot assistance and artwork tools have their own provider and review boundaries.

02 / WHY

Why it works this way

Creative iteration should not modify a member's active release. Keeping drafts, candidates, playtests and publication distinct lets authors review exactly what they intend to deliver.

03 / HOW

How it works

Save work in the owning editor, validate the graph and assets, then preview the exact candidate. Review and publish through the existing release workflow. A later draft is not automatically included in an earlier approved candidate.

Character resources, sprite placement, voices and music stay with their existing asset owners. Copilot output is an authoring aid, not authority to publish or mutate arbitrary files. Shared speech synthesis keeps the selected voice and language across bounded passages.

Valkyrie's story and active-time battle tooling, the separate Legend Maker publication flow and Arcade campaign runtime have different owners. Their availability and manual acceptance must not be inferred from the presence of the VN Maker editor.

Further reading: Engineering handbook.

SYSTEM SCHEMATICS

View the diagram and flow
How the parts connect Conceptual flow of the current ownership boundary; not a live status display.
  1. 01
    Project and story

    Define identity, route and choices

  2. 02
    Scenes and media

    Compose presentation with owned assets

  3. 03
    Candidate

    Validate exact saved content

  4. 04
    Private playtest

    Review the intended experience

  5. 05
    Release

    Publish a retained reviewed version

IMPLEMENTATION SAMPLES

Inspect the code examples
Contract at a glancetext
Draft -> exact candidate -> private playtest -> review -> release
A newer draft does not rewrite a retained release.

Illustrative contract summary. This is not an executable script or a record of a live operation.

AkariLoreKeeper

AKARI-LK // ASK ABOUT THIS TOPIC

Ask a why or how question about this article.

Ask about this system