Skip to main content

STAGE Game Engineering

Choose the operation before the agent acts.

One canonical project. Four bounded Codex workflows. Human authority over product intent, taste, and acceptance.

Start with the owner guideInspect the project map

Workflow Router

What are you trying to do?

01Default

Deliver a change

stage-deliver-change

Implement, diagnose, tune, refactor, or polish one authorized outcome in the real game project.

May mutate only the accepted scope
02Explicit

Orient safely

$stage-game-engineering:stage-orient

Recover repository and task context in a fresh Codex task without touching protected state.

Read-only
03Explicit

Verify a claim

$stage-game-engineering:stage-verify

Check an existing delta or revision through the production consumers material to its claim.

Check-only; never fixes
04Explicit

Map a project

$stage-game-engineering:stage-map-project

Adopt, refresh, or externally audit a deliberate STAGE project map when the project earns one.

Map scope only
A project-native Lanternworks game frame used during STAGE dogfood

Project-Native Evidence

Rehearse the real consumer.

STAGE does not replace the engine, game, middleware, or human player with a detached review product. Evidence stays matched to the claim and the production path that owns it.

Match a claim to its evidence route

Reading Paths

Go directly to the source you need.

I want to use STAGE

Start with invocation, authority, task continuity, and the normal delivery path.

Open the owner guide

I maintain the package

Use the repository gates, release records, compatibility policy, and source map.

Open maintainer guidance