Evaluation Model

triode supports two live-coding evaluation modes through liveMode:

• "continuous" (default unless legacy: true)
• "restart"

Continuous mode

• A single runtime instance stays alive across evals.
• New code is evaluated into existing runtime state.
• Scene/object identity can be stabilized with explicit key values.

Use when you want fluid iterative livecoding without full runtime reset.

Restart mode

• Runtime state is reset on each eval(...) cycle by default.
• Closest to older restart-every-run workflows.

Use when you prefer strict rerun determinism and can tolerate full reset cost.

Per-call override:

• triode.eval(code, { mode: "continuous" | "restart" | "auto", reset?: boolean, hush?: boolean })

Identity guidance

In continuous mode:

• key on scene/group/object is the strongest identity anchor.
• name is descriptive unless reuse: true is set.
• triode can assign source-based auto identities, but explicit keys are recommended for major refactors.

See Live-Key Migration.

Error routing

Runtime errors from update, afterUpdate, and tick are forwarded to onError(error, context) when provided.

Use this hook in host applications for centralized diagnostics.