MonyDragon Projects

Building systems that adapt, create, and stay accountable

Our flagship projects explore two connected ideas: software should respond responsibly to the people using it, and creators should have tools that make ambitious work safer to build.

Work in progress

Two evolving platforms, presented with clear status and scope.

These pages describe active direction and implementation evidence without presenting roadmap capabilities as already shipped.

Flagship systems

Designed around human control and durable foundations

Vision in developmentLed by Stormi Hamilton

Adaptive software ecosystem

C.O.R.G.I. Systems

Software that adapts to the person—within boundaries people control.

C.O.R.G.I. is a modular architecture for building more responsive games, education, training, accessibility, and enterprise experiences. Its direction centers on permitted interaction data, transparent adaptation, developer-defined limits, privacy, consent, and meaningful human override.

Focus areas

  • Adaptive experiences guided by developer and administrator rules
  • Accessibility and multiple ways to learn or interact
  • Observable decisions through logs, research, and visualization
  • Modular deployment with proportional data collection and consent

Current boundary

The supplied overview defines the ecosystem, principles, modules, and research direction. Individual capabilities remain planned or implementation-dependent unless separately evidenced; this showcase does not claim a finished commercial release.

Implementation in progressLed by Mony Dragon

Cross-platform game engine and visual editor

Dragon Pixel Engine

A creator-focused 2D and 3D workflow over code-first game frameworks.

Dragon Pixel Engine is a standalone editor and engine architecture for Windows, macOS, and Linux. It combines a portable authoring core, component-based C++ and C# workflows, isolated preview and play processes, and runtime adapters for MonoGame and the still-experimental KNI path.

Focus areas

  • Familiar scene, hierarchy, Inspector, asset, and dockable-panel workflows
  • Portable project data with explicit ownership and versioned boundaries
  • Crash-isolated preview and play runtimes that preserve authoring state
  • Reversible project operations and evidence-driven cross-platform gates

Current boundary

The accepted 1.0 architecture is being implemented and tested. Windows and Ubuntu evidence covers substantial editor/runtime foundations, while macOS, packaging, accessibility, complete slice acceptance, and broad KNI conformance remain open gates.

Project principles

01

Human-controlled

Automation and adaptation operate inside visible limits, with meaningful override and reset paths.

02

Modular

Capabilities stay composable so projects can adopt what they need without inheriting an entire monolith.

03

Observable

Claims are tied to logs, tests, diagnostics, and clearly stated evidence instead of hidden behavior.

04

Built to evolve

Versioned contracts, reversible changes, and explicit boundaries leave room for responsible growth.

Follow the work

Interested in adaptive systems, game technology, or a future collaboration?

Tell us what you are building, the people it needs to serve, and where responsible adaptation or stronger creator tooling could help.

Start a conversationMeet the team