WINDWAY DATA

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. Each episode is built to be reset, replayed and checked.

The current verified production set contains 100 unique GOLD episodes across navigation recovery, joint-plan recovery and joint-gate recovery. These are data-quality results, not agent performance scores.

Our public work demonstrates the production and verification pipeline. Commercial engagements are private and adapted to your environment, action schema, failure modes and evaluation requirements. Private samples are available to authorized B2B prospects under agreed delivery terms.

Try Explorer ↗

TASK → FAILURE → VERIFIED RECOVERYFULL STRUCTURE
Illustrative environment, failed action, recovery and verificationStructural explanation, not a live agent, production episode or performance score. All narrative text remains available below.BLOCKEDSTATE AGOALSTATE Breplay · verifier_result · provenance
PASS · DIAGRAM FIXTUREfixture hash d3e71bd311b6
Original teaching fixture. Separate from production GOLD.
How to read this scene

This original deterministic fixture rejects a blocked move, then verifies a valid detour. It contains no production episode or private task values.

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

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

From a task to a checked result.

  1. Environment
  2. Task
  3. Observation
  4. Action
  5. State transition
  6. Failure
  7. Recovery
  8. Verifier
  9. Result
Environment & task
A versioned world, controlled initial state, objective and permitted actions.
Observations & action schema
The agent sees an observation and submits a typed action. The environment checks its arguments and constraints.
Trajectory & transition
Each step records the before-state, action, resulting state and tool outcome.
Failure & recovery
An invalid action retains an explicit failure state. A recovery is replayed under the same rules.
Verifier & provenance
A deterministic predicate checks the result. Versions, input hashes and generator provenance connect it to its origin.

STATE → ACTION → TRANSITION → FAIL → RECOVERY → VERIFIER → PASS

Explore a verified episode.

Original deterministic teaching fixture. Separate from production GOLD.

ENVIRONMENT / GRID[7 × 5] · DETERMINISTIC
BLOCKTARGET

State 01 · NOT RUN

Observation
Position, obstacle and goal
State
[1, 2]
Action
Observe the target.
Constraint
Adjacent moves only.
Provenance
Original grid fixture · d3e71bd311b6
Inspect the teaching fixture contract
{
  "scope": "DIAGRAM_FIXTURE_ONLY",
  "environment": {
    "grid": [
      7,
      5
    ],
    "blocked": [
      [
        3,
        2
      ]
    ],
    "start": [
      1,
      2
    ],
    "goal": [
      5,
      2
    ]
  },
  "action_schema": {
    "action": "move",
    "arguments": {
      "next": "adjacent [x,y] cell"
    }
  },
  "success_condition": "valid recovery reaches [5,2]",
  "provenance": "original deterministic website fixture"
}

This original example explains the schema. It is not a canonical GOLD record or a customer dataset.

Built around your mechanics.

Commercial work adapts task families, observation format, action schema, failure modes, environment constraints and evaluation criteria to an agreed private brief.

You provide the authorized interface and acceptance criteria. Windway scopes environments, verified trajectories, replay interfaces and delivery evidence around them.

Request a GameOps pilot ↗

CANONICAL GAMEOPS GOLD / 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.

Read the sanitized evidence summary ↗

BLENDER VERIFIED MVP / SEPARATE FACTORY SCOPE

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 Blender factory illustration: room navigation
room navigation / factory illustration, not production GOLD observations
Original Blender factory illustration: maze navigation
maze navigation / factory illustration, not production GOLD observations
Original Blender factory illustration: multi agent coordination
multi agent coordination / factory illustration, not production GOLD observations
Original Blender factory illustration: visibility occlusion
visibility occlusion / factory illustration, not production GOLD observations

Original annotated renders. Routes are presentation overlays, not simulated agent traces.

Request a sample or buyer materials ↗

Inspect the three offers ↗ · WFRB v0 methodology & results ↗ · Explore the design partner program ↗