GameARC is the planned specialist-agent platform for coordinating reviewable game-development work inside Majestic Helios.
Loading page
Loading page content
ALTERED BRILLIANCE IS LIVE.ALTERED BRILLIANCE IS LIVE ON GOOGLE PLAY.Read the product story →
A control panel for specialized game-development agents that can work standalone or connect directly to Majestic Engine through Kri Zek’s first-party bridge.
GameARC is the agent-native environment within the Majestic Helios product family. It turns a development objective into a persistent working session with a specialist role, project context, approvals, tools, evidence, and lifecycle controls.
It is designed to operate as a focused agent platform on its own. Its deeper advantage appears when a project uses Majestic Engine: the first-party bridge can connect planning and code changes to engine-aware builds, diagnostics, runtime state, validation, and play controls.
The current implementation defines durable session state rather than a disposable chat thread.
Launch multiple goal-driven sessions, inspect their state, and return to their timelines.
Pause, stop, retry, clear, and continue a session with follow-up instructions.
Plans, tools, terminal actions, network access, engine commands, and patches can require review.
Files read, citations, patches, checkpoints, commands, builds, tests, previews, diagnostics, usage, and cost live with the session.
Each profile narrows the context, tools, and validation expected for a different game-production discipline.
Gameplay code, tests, and runtime logs.
Engine APIs, modules, builds, and validation.
Materials, shaders, assets, and visual pipelines.
Shader code, materials, and render diagnostics.
Scenes, prefabs, resources, and level validation.
Build profiles, packaging, CI, and smoke tests.
Tests, diagnostics, regressions, and runtime evidence.
Frame timing, profiling artifacts, and runtime logs.
Networking, services, tests, and security boundaries.
Diffs, diagnostics, tests, and review reports.
This is the target workflow for the beta. It describes product direction, not a claim that every stage is already runtime-proven.
Describe the game, feature, bug, or production outcome in one working session.
GameARC indexes the approved workspace and gathers cited project, code, build, and engine context.
A specialized agent produces a reviewable plan instead of silently editing the project.
Approved tools inspect files, propose patches, run commands, and preserve checkpoints.
The first-party bridge exchanges project, build, diagnostic, and runtime context with Majestic Engine.
Builds, tests, previews, engine acknowledgements, and repair cycles become recorded evidence.
The target is a playable Majestic Engine build with a report that says what passed, failed, and remains.
A generic coding agent can inspect a repository and run commands. GameARC is being built to understand the full Majestic workflow: project identity, engine capabilities, scenes, build profiles, diagnostics, tests, runtime logs, play state, and validation evidence.
The bridge remains versioned and bounded. Majestic Engine stays authoritative for game execution, authoring contracts, assets, packaging, and runtime state. GameARC coordinates work through Majestic Helios rather than pretending to replace the engine.
CodenameDeacon contains the specialized profiles, versioned session schema, lifecycle APIs, control-panel UI, working-session timelines, follow-up messaging, background tasks, checkpoints, approval states, evidence fields, Majestic bridge foundations, and automated session tests.
The native Helios extension already connects to the shared AgentRuntime, but the GameARC-branded control experience and complete model-tool-engine loop still require packaged Windows acceptance. The beta is planned alongside Majestic Helios IDE after those gates pass.
Turn Majestic Helios agent foundations into a packaged control plane that can carry a game from intent to verified play.
Reviewed August 2026 · no fixed release dates
View portfolio roadmapPublicly shipped or part of the current product foundation.
Versioned sessions, ten specialist profiles, lifecycle control, approvals, evidence fields, checkpoints, and test coverage exist in CodenameDeacon.
First-party engine project, state, command, diagnostic, build, and validation contracts provide the integration path.
Source exists, but runtime, packaged, or release acceptance is incomplete.
Move the complete branded workflow beyond the deprecated browser harness and prove it inside packaged Majestic Helios.
Prove planning, approvals, tools, patches, builds, tests, previews, engine acknowledgements, repair, and final evidence with a real provider.
Approved work is actively being built or hardened.
Complete working-session orchestration, timelines, follow-up messaging, artifacts, parallel background work, and operator controls in the native product.
Connect game ideation, implementation, verification, engine execution, and playable-build reporting through one persistent session.
Intended direction, subject to validation, sequencing, and change.
Offer GameARC as a focused agent command center while preserving its deeper Majestic Helios and Engine integration.
Open controlled Windows beta access after packaged acceptance, bridge reliability, and evidence gates pass.
Register interest in the upcoming GameARC and Majestic Helios beta, or explore the first-party engine bridge it is designed around.
How the agent platform fits Majestic Helios, Majestic Engine, and human review.