XOSC — Ideas & planning notes

This folder is primarily a design archive. Most v0.5 and DMX proposals shipped
in v0.5–v0.7; use the root HANDOFF.md and CHANGELOG.md for current state.
These files preserve rationale and future ideas. Three rules:

1. Cite real code when you make a claim about current behaviour. If a doc says "the router does X," it must reference the file/line that does it. Memory rots faster than code.
2. Treat old backlogs historically. The numbered v0.5 backlog records the
order that milestone was built; it is no longer the current to-do list.
3. Don't grow scope silently. If a feature reveals a new feature mid-build, add it to the backlog with a one-line cost estimate. Don't fold it into the in-flight task.

Index

Current engineering handoff — Public summary

of current state and recommended next milestone.

Architecture limits & loop protection — How long can a chain be before things break? What stops an infinite loop? Where the current code has unguarded re-entry.
Dispatch semantics: fan-out, ordering, parallel vs. sequential — Does one input fire many outputs at once? Can we say "wait for the DMX frame to flush before firing the OSC packet"? Today's answer + the proposed dispatch-mode model.
v0.5 backlog (ordered) — Historical milestone plan

and shipped-feature record.

Competitor gap analysis — Chataigne / Companion / OSCulator / TouchDesigner: what they do well, what they miss, where XOSC wins or loses by default.
Math & logic nodes (proposal) — Clamp, scale, invert, hold-timer, double-tap, expression. Sketches the type system + UI.
OSC inbound + Resolume feedback loop — Listen on a UDP port for OSC from anything (not just Resolume's WS) and pipe it onto the input bus. Closes the "physical LED on user's prop tracks Resolume state" loop.
mDNS / network discovery — Auto-find Resolume + other OSC peers on the LAN.
DMX integration feasibility — Can we add DMX nodes? Mapping TagTable's "beat pad / sequence / priority" model into the XOSC graph. Last on the priority list — see file for why.

How to read these as a fresh agent

1. Read the root HANDOFF.md and the top of CHANGELOG.md first.
2. Use this directory only for the design topic relevant to the selected task.
3. Verify every historical claim against current code before acting on it.