Reika connects a shared computing core to public and creator workstations in a Gynara laboratory.
Engineering / Knowledgebase

TECHNICAL NOTE

Platform // platform.drakimacore

Why DrakimaCore separates the public site and Studio

PublicWeb serves members, StudioWeb owns staff authoring, and Workers runs background jobs. Shared contracts connect them without merging their permissions.

Production Practitioner Updated 2026-10-30

01 / WHAT

What it does

DrakimaCore is a .NET 10 modular application. Public and staff sites use Razor views and feature-owned JavaScript. Domain rules and Application contracts sit below Infrastructure adapters and host composition. The Runtime library still compiles active compatibility services.

02 / WHY

Why it works this way

Member conversations should not depend on keeping a staff editor open. Separating hosts makes routes, database access and process lifecycles explicit while retaining one coherent content universe.

03 / HOW

How it works

PublicWeb exposes catalog, account and member experiences. StudioWeb supplies CMS, Gynoid Wizard, VN Maker, page authoring, review and operations. Workers owns configured projection and recovery work. NodeGuardian coordinates configured AI-node readiness.

Core owns identity, content, credits and editorial state; Cognition owns private Gynoid conversations and memory. Public and Studio share configured login protection while retaining separate authorization. Large media remains in its owned filesystem stores.

The current decomposition is real but incomplete: Runtime-linked owners are maintained compatibility seams. A project inventory or running host does not certify provider health or Beta acceptance.

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
    Member request

    PublicWeb applies account and feature admission

  2. 02
    Staff change

    StudioWeb applies role, assignment and release rules

  3. 03
    Shared contracts

    Application and Domain express the use case

  4. 04
    Owned adapters

    Infrastructure persists or invokes the permitted provider

  5. 05
    Background work

    Workers reconciles durable tasks independently

IMPLEMENTATION SAMPLES

Inspect the code examples
Contract at a glancetext
Domain <- Application <- Infrastructure
Web owns HTTP, Razor and browser behavior.
Hosts compose only their permitted capabilities.
Runtime is a library, not a second web executable.

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