01 / environment
The environment.
An agent does not act in a spreadsheet. It acts inside a stateful environment. Nodes, paths, objects and constraints give each action a consequence.
environment_id · environment_version
01 / environments & trajectories
Windway GameOps
A failure is only useful if you can replay it.
GameOps connects an initial state, an action sequence, an observed failure, a recovery and a deterministic outcome. The episode is more than an example: it is something you can execute again.
The current verified production set contains 100 unique GOLD episodes. Its scope is navigation recovery, joint-plan recovery and joint-gate recovery. These are data-quality results, not claims about an agent’s performance.
Sample access and buyer documentation are reviewed subject to applicable rights and recipient approval. Request access rather than downloading internal production files.
ENVIRONMENT TO DELIVERYFULL STRUCTURE
PASS · DIAGRAM FIXTUREfixture hash d3e71bd311b6
How to read this scene
The layout is an original deterministic diagram fixture. The blocked move is rejected; a valid detour reaches its goal. PASS/FAIL here describe that fixture only. Production quality evidence is shown separately. Field names come from the admitted GameOps contract; no private task values or episode IDs are copied.
02 / state
One scenario. A clear goal.
Zoom into the initial state. A goal, permitted actions and explicit constraints define what counts as a valid result.
initial_state · objective · available_actions
03 / action
An action changes the state.
The diagram moves from state A to state B. Its transition is checked against the illustrative environment rules; this is a schematic, not gameplay footage.
action_schema · reference_trajectory
04 / failure
Failure is data too.
A route that looks plausible can lead into a blocked cell. The diagram verifier rejects the action and retains the unchanged failure state.
failure_step · failure_state
05 / recovery
Recover the goal.
A detour uses permitted transitions to reach the goal. Failure, recovery and verification remain separate parts of the evidence trail.
recovery_trajectory · final_state
06 / verification
Every result must survive replay.
Reset the initial state, replay the trajectory and check the outcome. Environment hashes, snapshot hashes and provenance connect a result to the conditions that produced it.
verifier_result · environment_hash · snapshot_hash · provenance
07 / provenance
Keep the result traceable.
Record the environment version, controlled inputs and generator provenance. A verified result should remain connected to the conditions that produced it.
provenance · generator_version · environment_hash
08 / delivery
Build around your acceptance gate.
Bring your schema, environment, mechanics, failure modes and evaluation criteria. Windway packages agreed verified episodes, a verifier, provenance and an evaluation report.
Client inputs → agreed delivery contract
CLIENT INPUT
Schema · environment · mechanics · failure modes · evaluation criteria
AGREED PACKAGE
Verified episodes · verifier · provenance · evaluation report
PRODUCTION / AUDITED SCOPE
100 unique verified
GOLD episodes.
Schema100 / 100
Reset100 / 100
Replay100 / 100
Verifier100 / 100
Provenance100 / 100
Independent executable audit: PASS. No independent human-review or agent-performance claim.
BLENDER MVP / FACTORY ILLUSTRATIONS
Worlds with structure.
Separate from production GOLD: 100 deterministic layouts, 900 derived task designs, 700 resettable/replayable tasks. 1,200 incorrect results and 300 invalid actions rejected in controlled factory tests. These figures do not certify 900 or 700 GOLD episodes. The 1K production expansion remains HOLD.
Original annotated renders. Routes are presentation overlays, not simulated agent traces.
Request a sample or buyer materials ↗WHAT AN ENGAGEMENT LOOKS LIKE
GameOps Pilot
- Problem
- Game agents recover in ways a transcript alone cannot verify.
- What we produce
- Versioned state/action/failure/recovery episodes with executable checks.
- What you provide
- Your task family, engine interface, permitted inputs and acceptance criteria.
- What you receive
- An agreed episode package, replay interfaces, QA evidence and provenance.