Direction without fake certainty.

Windows-native IDE foundation

Code OSS workbench, local context, Git, persistent sessions, and reviewable AI changes.

First-party Majestic workflow

Direct Majestic Engine project and bridge foundations keep code, diagnostics, and engine state in one development loop.

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.

Evidence-backed Agent loop

Prove plan, approval, tool use, repair, build, test, preview, and final reporting with real runtime evidence.

Majestic Engine bridge hardening

Add authenticated connection state, heartbeat, version and capability negotiation, acknowledgements, diagnostics, and reliable build/run control.

Majestic Account completion

Validate native sign-in, refresh, restart persistence, device registration, entitlements, and hosted usage.

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.

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.

C++20 engine and editor foundation

Windows-first runtime, native editor, manifest-driven projects, reflection metadata, command-based undo, and a supported 2D path.

Helios bridge foundation

First-party project and editor integration connects the engine to Majestic Helios without merging product boundaries.

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.

Galactic Vanguard vertical slice

Use one shipping-quality arena and boss encounter to drive engine priorities from real game requirements.

Production gaps

Add sprite-sheet animation, animation events, frame hitboxes, runtime UI, multi-voice audio, and stronger camera behavior.

Broader production systems

Harden packaging, physics, asset pipelines, and versioned release operations after the first game loop is proven.

Mature 3D and additional platforms

Advance experimental 3D and evaluate macOS and Linux only after Windows production evidence is stable.

Two-product foundation

Majestic Engine owns authoring and runtime; Majestic Helios owns code, AI assistance, source control, and debugging workflows.

Shared Majestic Account

One portal and identity backend covers plans, entitlements, devices, quotas, and usage across both products.

End-to-end first-party workflow

Create, open, author, build, run, debug, repair, and package a Majestic project without manual path wiring.

Versioned integration contract

Complete manifest discovery, CLI contracts, diagnostics, IntelliSense, tasks, templates, DAP debugging, and explicit version negotiation.

Native identity acceptance

Prove secure desktop sessions, device registration, entitlement enforcement, and usage reporting in Engine and Helios.

External engine adapters

Extend the proven suite workflow to Unity and Unreal Engine through isolated, versioned bridges.

Broader delivery coverage

Expand platforms, collaboration, and deployment only after the Windows-first suite reaches repeatable acceptance.

Level 1 research workspace

Dataset, training, adapter, manifest, deterministic evaluation scripts, and raw-output foundations exist.

Current product proxy

GamePilot uses authenticated allow-listed cloud model routing today; TGX-1 is not represented as its current production model.

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.

Repair and rerun

Fix structured-output adherence, dataset lineage, privacy, evaluation boundaries, and explicit release criteria before further promotion.

Training contribution standard

Prepare consent-first, minimized, reviewed gameplay evidence without treating raw collection as automatically trainable.

Specialized variants

Evaluate player, developer, enterprise, education, and esports variants only after the shared foundation qualifies.

Device and suite deployment

Explore edge execution and native GamePilot or Majestic integration after quality, privacy, and benchmark gates pass.

AgentRuntime foundation

Versioned sessions, ten specialist profiles, lifecycle control, approvals, evidence fields, checkpoints, and test coverage exist in CodenameDeacon.

Majestic bridge foundation

First-party engine project, state, command, diagnostic, build, and validation contracts provide the integration path.

Native GameARC control experience

Move the complete branded workflow beyond the deprecated browser harness and prove it inside packaged Majestic Helios.

Model-tool-engine loop

Prove planning, approvals, tools, patches, builds, tests, previews, engine acknowledgements, repair, and final evidence with a real provider.

Agent control panel

Complete working-session orchestration, timelines, follow-up messaging, artifacts, parallel background work, and operator controls in the native product.

Idea-to-playable workflow

Connect game ideation, implementation, verification, engine execution, and playable-build reporting through one persistent session.

Standalone agent platform

Offer GameARC as a focused agent command center while preserving its deeper Majestic Helios and Engine integration.

Beta alongside Majestic Helios

Open controlled Windows beta access after packaged acceptance, bridge reliability, and evidence gates pass.

TGI and tGiX foundation

The Gamer Index and its deterministic telemetry framework already have product surfaces inside Altered Brilliance.

Identity model and boundaries

Validate source connections, consent, visibility, history, missing-data behavior, and the distinction between private evidence and public identity.

Six-part identity portal

Unify games played, genre preference, playtime, achievements, gaming tenure, and readable fun facts.

Player controls

Make connected sources, visibility, corrections, and profile state understandable and reversible.

Validated global rollout

Open the portal to gamers worldwide after source quality, controls, privacy, and presentation pass review.

Broader identity signals

Add new signals only when they clarify the gamer’s story rather than inflate the profile.