Direction without fake certainty.
What exists, what still needs proof, what we are implementing, and where the products can go after their current gates pass.
A roadmap is not a release promise.
Available now
Publicly shipped or part of the current product foundation.
In validation
Source exists, but runtime, packaged, or release acceptance is incomplete.
In implementation
Approved work is actively being built or hardened.
Future direction
Intended direction, subject to validation, sequencing, and change.
Direction, with the uncertainty left intact.
Prove the first-party Majestic workflow, then extend the IDE through deliberate engine adapters.
Reviewed August 2026 · no fixed release dates
View portfolio roadmapPublicly shipped or part of the current product foundation.
- 01
Windows-native IDE foundation
Code OSS workbench, local context, Git, persistent sessions, and reviewable AI changes.
- 02
First-party Majestic workflow
Direct Majestic Engine project and bridge foundations keep code, diagnostics, and engine state in one development loop.
Source exists, but runtime, packaged, or release acceptance is incomplete.
- 01
Luna 4.9 packaged acceptance
Restore green CI, then prove the native build, browser verification, account persistence, and packaged Windows workflow.
Dependency: Blocked until the current npm installation failure is resolved.
- 02
Evidence-backed Agent loop
Prove plan, approval, tool use, repair, build, test, preview, and final reporting with real runtime evidence.
Approved work is actively being built or hardened.
- 01
Majestic Engine bridge hardening
Add authenticated connection state, heartbeat, version and capability negotiation, acknowledgements, diagnostics, and reliable build/run control.
- 02
Majestic Account completion
Validate native sign-in, refresh, restart persistence, device registration, entitlements, and hosted usage.
Intended direction, subject to validation, sequencing, and change.
- 01
Unity connection bridge
Bring engine-aware project context, build results, logs, play controls, and reviewable AI workflows to Unity projects.
Dependency: Begins after the first-party Majestic bridge is runtime-proven.
- 02
Unreal Engine connection bridge
Connect C++ modules, build tooling, editor logs, automation tests, and runtime context through a versioned adapter.
Dependency: Begins after the adapter contract is validated with Unity and Majestic Engine.
Direction, with the uncertainty left intact.
Turn substantial source foundations into a build-proven engine capable of shipping the first complete game.
Reviewed August 2026 · no fixed release dates
View portfolio roadmapPublicly shipped or part of the current product foundation.
- 01
C++20 engine and editor foundation
Windows-first runtime, native editor, manifest-driven projects, reflection metadata, command-based undo, and a supported 2D path.
- 02
Helios bridge foundation
First-party project and editor integration connects the engine to Majestic Helios without merging product boundaries.
Source exists, but runtime, packaged, or release acceptance is incomplete.
- 01
Clean build and launch gate
Compile, test, launch, and package the recent v0.4.0 source on a clean Windows machine.
Dependency: No recent capability is promoted as runtime-proven until this gate passes.
Approved work is actively being built or hardened.
- 01
Galactic Vanguard vertical slice
Use one shipping-quality arena and boss encounter to drive engine priorities from real game requirements.
- 02
Production gaps
Add sprite-sheet animation, animation events, frame hitboxes, runtime UI, multi-voice audio, and stronger camera behavior.
Intended direction, subject to validation, sequencing, and change.
- 01
Broader production systems
Harden packaging, physics, asset pipelines, and versioned release operations after the first game loop is proven.
- 02
Mature 3D and additional platforms
Advance experimental 3D and evaluate macOS and Linux only after Windows production evidence is stable.
Direction, with the uncertainty left intact.
Make the Engine and Helios feel like one workflow while keeping each product independently usable.
Reviewed August 2026 · no fixed release dates
View portfolio roadmapPublicly shipped or part of the current product foundation.
- 01
Two-product foundation
Majestic Engine owns authoring and runtime; Majestic Helios owns code, AI assistance, source control, and debugging workflows.
- 02
Shared Majestic Account
One portal and identity backend covers plans, entitlements, devices, quotas, and usage across both products.
Source exists, but runtime, packaged, or release acceptance is incomplete.
- 01
End-to-end first-party workflow
Create, open, author, build, run, debug, repair, and package a Majestic project without manual path wiring.
Approved work is actively being built or hardened.
- 01
Versioned integration contract
Complete manifest discovery, CLI contracts, diagnostics, IntelliSense, tasks, templates, DAP debugging, and explicit version negotiation.
- 02
Native identity acceptance
Prove secure desktop sessions, device registration, entitlement enforcement, and usage reporting in Engine and Helios.
Intended direction, subject to validation, sequencing, and change.
- 01
External engine adapters
Extend the proven suite workflow to Unity and Unreal Engine through isolated, versioned bridges.
- 02
Broader delivery coverage
Expand platforms, collaboration, and deployment only after the Windows-first suite reaches repeatable acceptance.
Direction, with the uncertainty left intact.
Keep promotion closed until the model produces valid, evidence-bounded outputs under frozen evaluation.
Reviewed August 2026 · no fixed release dates
View portfolio roadmapPublicly shipped or part of the current product foundation.
- 01
Level 1 research workspace
Dataset, training, adapter, manifest, deterministic evaluation scripts, and raw-output foundations exist.
- 02
Current product proxy
GamePilot uses authenticated allow-listed cloud model routing today; TGX-1 is not represented as its current production model.
Source exists, but runtime, packaged, or release acceptance is incomplete.
- 01
Promotion gate remains closed
The latest base and adapter evaluation produced zero valid structured outputs across 30 frozen cases.
Dependency: No candidate advances until schema and evidence adherence pass the frozen evaluation.
Approved work is actively being built or hardened.
- 01
Repair and rerun
Fix structured-output adherence, dataset lineage, privacy, evaluation boundaries, and explicit release criteria before further promotion.
- 02
Training contribution standard
Prepare consent-first, minimized, reviewed gameplay evidence without treating raw collection as automatically trainable.
Intended direction, subject to validation, sequencing, and change.
- 01
Specialized variants
Evaluate player, developer, enterprise, education, and esports variants only after the shared foundation qualifies.
- 02
Device and suite deployment
Explore edge execution and native GamePilot or Majestic integration after quality, privacy, and benchmark gates pass.
Direction, with the uncertainty left intact.
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.
- 01
AgentRuntime foundation
Versioned sessions, ten specialist profiles, lifecycle control, approvals, evidence fields, checkpoints, and test coverage exist in CodenameDeacon.
- 02
Majestic bridge foundation
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.
- 01
Native GameARC control experience
Move the complete branded workflow beyond the deprecated browser harness and prove it inside packaged Majestic Helios.
- 02
Model-tool-engine loop
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.
- 01
Agent control panel
Complete working-session orchestration, timelines, follow-up messaging, artifacts, parallel background work, and operator controls in the native product.
- 02
Idea-to-playable workflow
Connect game ideation, implementation, verification, engine execution, and playable-build reporting through one persistent session.
Intended direction, subject to validation, sequencing, and change.
- 01
Standalone agent platform
Offer GameARC as a focused agent command center while preserving its deeper Majestic Helios and Engine integration.
- 02
Beta alongside Majestic Helios
Open controlled Windows beta access after packaged acceptance, bridge reliability, and evidence gates pass.
Direction, with the uncertainty left intact.
Build a player-controlled identity portal from verified gaming history, preferences, milestones, and TGI context.
Reviewed August 2026 · no fixed release dates
View portfolio roadmapPublicly shipped or part of the current product foundation.
- 01
TGI and tGiX foundation
The Gamer Index and its deterministic telemetry framework already have product surfaces inside Altered Brilliance.
Source exists, but runtime, packaged, or release acceptance is incomplete.
- 01
Identity model and boundaries
Validate source connections, consent, visibility, history, missing-data behavior, and the distinction between private evidence and public identity.
Approved work is actively being built or hardened.
- 01
Six-part identity portal
Unify games played, genre preference, playtime, achievements, gaming tenure, and readable fun facts.
- 02
Player controls
Make connected sources, visibility, corrections, and profile state understandable and reversible.
Intended direction, subject to validation, sequencing, and change.
- 01
Validated global rollout
Open the portal to gamers worldwide after source quality, controls, privacy, and presentation pass review.
- 02
Broader identity signals
Add new signals only when they clarify the gamer’s story rather than inflate the profile.