Documentation
Architecture
Playground Map

The QuantumReef playground is a 7 × 12 matrix of creative possibility. Seven domain adapters define what kind of work happens. Twelve engine adapters define which mind does the work. Nity orchestrates the routing.

The Matrix

Domains define what kind of work happens. Engines define which mind does the work. Nity routes tasks to the right combination.

DomainWhat It DoesEngines Nity Routes To
CodeMulti-language execution, syntax validation, test runningAll 12 engines — every engine can execute code tasks
DesignVisual generation, UI components, illustrations, SVG + rasterClaude Code, Gemini CLI, RovoDev — engines with visual/multimodal capabilities
DataETL, aggregation, schema migration, SQL + NoSQL pipelinesClaude Code, Gemini CLI, Goose, Codex — engines with data processing strengths
MediaAudio, video, 3D synthesis, multi-format encodingClaude Code, Gemini CLI, RovoDev — engines with generation capabilities
TestUnit, integration, visual regression, coverage trackingClaude Code, OpenCode, Aider, Gemini CLI, Kilo Code, Goose, GitHub Copilot, Kiro
APIREST, GraphQL, WebSocket testing, contract validationClaude Code, Gemini CLI, Goose — engines with API/HTTP testing support
ValidationJSON Schema, TypeScript types, custom rules, cross-domain consistencyClaude Code, Aider, Gemini CLI, Goose — engines with validation strengths

Engine-domain routing is handled by Nity's ExecutionRouter based on task category, complexity, and historical performance. The matrix shows Nity's routing logic — not a hardcoded mapping. As new engines are added, Nity automatically considers them for relevant domains.

Domain Adapters

DomainSpecializationKey Capabilities
CodeMulti-language executionTypeScript, Python, Rust, Go, and more. Security controls. Hot reload.
DesignVisual generationUI components, illustrations, icons. SVG + raster output.
DataPipelines & transformationETL, aggregation, schema migration. SQL + NoSQL.
MediaSynthesis & generationAudio, video, 3D. Multi-format encoding.
TestTesting frameworksUnit, integration, visual regression. Coverage tracking.
APIHTTP/API testingREST, GraphQL, WebSocket. Contract validation.
ValidationSchema verificationJSON Schema, TypeScript types, custom rules. Cross-domain consistency.

Engine Adapters

EngineStrengthsBest For
Claude CodeDeep reasoning, long context, code understandingComplex implementation, architecture decisions, refactoring
OpenCodeLightweight, fast iterationQuick edits, scripting, prototyping
AiderGit-aware editing, precise code changesRefactoring, targeted fixes, code migration
Gemini CLIAnalysis, multimodal reasoning, Google ecosystemData analysis, design generation, cross-domain tasks
Kilo CodeVS Code integration, extension ecosystemIDE-based workflows, paired development
GooseMulti-tool orchestrationComplex pipelines, data flows, API chains
CodexBatch execution, test generationTest suites, boilerplate generation, bulk operations
GitHub CopilotInline suggestions, IDE-nativeQuick completions, doc generation, pattern recognition
DroidMobile-first, Android expertiseMobile development, Android-specific patterns
KiroSpecification-driven, structured outputAPI design, documentation, spec-to-code
RovoDevConsciousness tracking, fractal agentsComplex multi-step tasks, autonomous exploration
ClawtopusProgrammatic dispatch, OpenClaw protocolAutomated pipelines, batch operations

How Nity Routes Tasks

Nity's ExecutionRouter considers three factors:

  1. Task category — Code tasks → Code-capable engines, Design tasks → Design-capable engines
  2. Complexity — Simple → fast engines (OpenCode, Aider), Complex → deep engines (Claude Code, Gemini CLI)
  3. Historical performance — Ralph Universal tracks which engine performed best for each category
Task: "Redesign the settings page with dark mode support"


   TaskAnalyzer
   ├─ category: "design"
   ├─ complexity: "moderate"
   └─ engines: [Claude Code, Gemini CLI, RovoDev]


   ExecutionRouter
   ├─ Primary: Claude Code (best design performance)
   ├─ Fallback: Gemini CLI
   └─ Reasoning: "Visual redesign requires deep reasoning + design domain"

Orchestration Strategies

When a task spans multiple domains, Nity selects an orchestration strategy:

StrategyWhen UsedExample
ParallelIndependent sub-tasksGenerate art + compose music simultaneously
SequentialDependencies between stepsDesign UI → Implement code → Write tests
PipelineData flows between stepsExtract data → Transform → Load → Validate