Which of Cade's three event layers — hardware, signals, or event handlers — to reach for, for each class of problem.

Score on patterns of events — bursts, cross-device coincidences, and spinner rate tiers — with the burst, coincidence, and rate primitives.

The three things an actions { } block can do — emit an event, activate a signal, or award points — and why they aren't interchangeable.

Every mode belongs to a module that owns its variables, handlers, and scoring — top-level mode blocks are no longer parsed.

Attract, tilt, and initials-entry modes, plus the target/select/apply primitives for declarative device inhibition.

The system.ball.* / system.play.* lifecycle events, and choosing eject_ball vs kick_ball to drive multiball correctly.

How Cade keeps a game running through scoring faults using fallback points and automatic safety mode.

The shared layer behind coils, motors, servos, and targets — identity, events, state bindings, and input-driven reactions.

Fire a ball already held by a kicker without changing the ball-in-play count — the counterpart to eject_ball.

Define oscillator-based synth patches with ADSR envelopes and trigger them from events — no audio files required.

Keep lights and other variable-driven outputs in sync across game end, player switch, and player restore.

Cade's reserved identifiers, and how cade validate and cade migrate catch and rename conflicts.

Verify exact scoring, variable, and event outcomes with .cade.test files run against the real engine in CI.