Stage lighting · browser-local DMX patch geometry · 2026 · Solo — product framing, test-first address logic, interaction design, accessibility, responsive verification, production deployment
DMX Ledger
A lighting-address workbench that makes one hidden channel collision visible before fixtures go dark.
The problem
Small venue lighting technicians and touring operators often translate fixture modes into start addresses across a handwritten patch, console screen, and physical rig. A fixture footprint can overlap another or spill past channel 512 while every individual start address still looks plausible, leaving the fault hidden until setup. DMX Ledger keeps that bounded operation causal: stage fixtures on one proportional universe strip, select or keyboard-shift any block, inspect its exact start and end, expose pairwise shared ranges and overflow, then copy the same tested plan as a patch sheet. It performs deterministic address geometry only and does not inspect a console, RDM, fixtures, cable termination, electrical load, power distribution, or live output; fixture modes and the physical patch must be verified before use. State stays in ephemeral browser memory, with no account, persistence, paid API, credential, upload, tracking SDK, outbound email, advertising, payment, or destructive external operation. Production deployment dpl_Ciqb3KPg2gue89rsRyQhx2scgCYA reached READY before independent Foundry artifact, HTTPS deploy, and seven-step behavior checks passed at the stable alias.
Architecture
Key decisions
Make the universe strip the operating surface
The four dark lanes are not a decorative chart. Every cyan, coral, or hatched block is positioned from tested addresses; selection, keyboard movement, readout, status, ledger, and copied sheet all consume the same plan.
Count occupied channels as a union
Overlapping footprints do not inflate occupancy by being summed twice. The core counts unique in-universe addresses while separately naming every exact shared range.
Preserve overflow instead of clipping it away
A fixture beginning at 500 with a 24-channel mode remains visibly 500–523 and is marked overflow. Only its thirteen valid universe addresses count as occupied, so the operator sees both the intended footprint and the boundary failure.
Keep the lighting claim narrow
DMX Ledger plans addresses only. It repeatedly excludes fixture discovery, mode truth, signal transport, termination, power, and live safety, and requires verification against the console and physical rig.
Use an original industrial control register
Warm call-sheet stock, graphite universe lanes, phosphor-lime focus, cyan clear blocks, coral faults, Georgia hierarchy, and monospaced evidence produce a dense Operate bench without generic indigo, blur, feature tiles, icon toppers, center stacking, or ornamental metrics.
Let failed gates improve the release
Orphaned template routes, current dependency advisories, host thread exhaustion, a legacy lint wrapper, undersized proportional hit targets, and a stale owned server child all failed honestly before narrow repairs and complete local plus production reruns.