DRAKIMACORE // ENGINEERING HANDBOOK

The technology behind Drakima

Website, databases, media, local AI and the boundary between software and physical embodiment.

Reviewed 2026-11-07 · Public chapters

Ask Akari about this chapter
Source: docs/current/technology-stack.md Download Markdown

Sora reviews separate website, conversation and compute modules in a Gynara laboratory.

Drakima connects the Gynara Legend's characters, stories, music, videos and conversations through one modular website. The artwork illustrates that universe; it is not evidence of a completed physical Gynoid. This chapter describes the implementation reviewed on October 29, 2026.

Website and authoring

Technology Current responsibility
C# / .NET 10 / ASP.NET Core PublicWeb, StudioWeb and background Workers; separate executable boundaries
MVC and Razor Server-rendered pages, account journeys, public catalogs and staff editors
JavaScript modules and CSS Room lifecycle, resizable chat, media playback, visual editors and responsive presentation
ASP.NET Core Identity and Data Protection Accounts, roles, protected cookies and the configured shared-login boundary
Entity Framework Core 10 and Npgsql PostgreSQL persistence and separately versioned Core/Cognition models
Markdig Markdown presentation for approved content and the packaged handbook
SkiaSharp and portable media libraries Image preparation, sprite editing and tooling; WPF adapters stay in Windows tools

The website is not a separate JavaScript SPA. Public and staff Web libraries share presentation where appropriate. Domain rules and Application contracts sit below Infrastructure and host composition. Runtime remains an active compatibility library; modular ownership does not mean every older service has already moved. See architecture and the feature map.

Records, files and inference

Core owns accounts, editorial content, releases, credits and settlement. Cognition owns private Gynoid conversations, operations and personal memory. Site-assistant and authored-story records still have Core owners. The former member video-generation database is retired.

Large image, music, video and protected release files have explicit media owners and manifests. They are not database blobs or disposable build output. Public assets and private authored/runtime stores have different delivery rules. Content hashes and retained releases let an existing story or game keep using the bytes against which it was admitted.

LM Studio supplies configured local language-model inference. ChatterBox supplies character speech. Pinokio manages the separately installed ChatterBox app and its Python environment; PyTorch and the GPU driver determine whether synthesis can use the device. Read local AI hosting with Pinokio and ChatterBox for the verified Blackwell compatibility repair and its limits. Their model, voice and capacity settings are deployment choices, not a fixed website-wide model name. NodeGuardian coordinates configured node readiness; it does not replace those providers. Optional Hermes integrations and research admission remain separate capabilities. Gynoid Creation Core is an independent creator-PC artwork tool, with deliberate exports rather than a dependency of public chat. Creation Core uses the creator's ComfyUI/Qwen Image 2.1 installation. VN Art Studio has separately configured Forge Neo/ComfyUI profiles and review owners; importing artwork in the Gynoid Wizard does not itself invoke generation. Model weights and provider processes remain separate prerequisites.

Accounts, purchases and participation

The credit ledger uses stable operation identities so retries can settle once. Owning content, using hosted AI, generating speech and buying an Arcade campaign are separate decisions. SMTP and PayPal are optional integrations: their implementation does not establish that email or checkout is enabled in a particular installation. The website exposes unavailable states when a required dependency is off.

Members can return to conversations and reading from their profile, control notifications, participate in public discussions and contact support. Private room history does not become public comment context. Staff authoring, moderation and operational tools require their existing role and assignment checks.

From fictional characters toward physical embodiment

The current product supplies software identities, conversation, voice, presentation and creative tools. The separate embodiment dossier is experimental research, not a deployed robot controller. Moving toward a physical chassis will require measured hardware interfaces, deterministic motion control, independent stop authority, simulation and hardware acceptance. Website or language-model test results cannot substitute for those engineering stages.

Implementation evidence: hosts/, src/DrakimaCore.Runtime/DrakimaCore.Runtime.csproj, src/DrakimaCore.Infrastructure/DrakimaCore.Infrastructure.csproj, Libraries/, Composition/, Services/Engineering/EngineeringSolutionManifest.cs. Package patch versions belong to the project files and package audit; this page describes responsibilities rather than promising a permanently fixed bill of materials.

The Gynara game platform

The custom game platform adds a WPF authoring editor, portable fixed-step C# engine and simulation, Raylib desktop presentation and a WebAssembly browser player. ASP.NET Core owns protected Arcade admission and verified releases. Read the platform guide, Maker, art/audio and browser delivery. WPF is the Windows editor technology; it is not the browser rendering layer.