A good control map comes first.

Record the public controls

A boolean represents an ongoing condition, a number supplies a bounded value, and a trigger represents a one-shot event in legacy input-based files. For a new system, review the target runtime’s data-binding support and expose properties appropriate to that contract.

{
  "asset": "YOUR_ASSET.riv",
  "artboard": "CONFIRM_IN_EDITOR",
  "stateMachine": "CONFIRM_IN_EDITOR",
  "controls": [
    {
      "name": "progress",
      "type": "number",
      "range": [
        0,
        1
      ],
      "default": 0
    },
    {
      "name": "isActive",
      "type": "boolean",
      "default": false
    },
    {
      "name": "celebrate",
      "type": "trigger",
      "behavior": "one-shot after confirmed success"
    }
  ]
}

Before enabling live testing

1. Supply a licensed .riv file and a static poster.
2. Document its artboard, state machine and real control names.
3. Pin and load the appropriate runtime and WASM assets.
4. Validate load failure, input type checks, cleanup and reduced-motion behavior.

No example name above should be assumed to exist in a real file.