TraraLink Integrations

Experimental adapters, released separately from the protocol and SDK. Original reusable Rust integration code is MIT OR Apache-2.0. The separate az-device AZ-MODS plugin is GPL-3.0-only; its license and external SDK requirements are explicit in that directory. Root Lightbridge path dependencies retain their own licensing status; resolve that status before redistributing a bundle.

az provides one passive AZOS backend and one native player-number map. Both future TraraLink and native PRO DJ LINK adapters will consume that same state engine. It currently performs no native networking, firmware patch or device I/O. AZOS timestamps in offline conversion are explicitly operator-assumed. Transport, mastership, phase and unknown position units remain unknown. Identity transitions without a qualified load generation and sequence restarts are refused.

lightbridge maps qualified snapshots into Lightbridge's public contracts using an explicitly supplied clock mapping. Lightbridge's actual consumer has a traralink source and observe_clock_snapshot command: missing fields withdraw visibility. The source requires explicit trust/selection and never arms output. Only compatible four-quarter-note bar phase maps into its current phase consumer.

From this directory:

cargo test --workspace
cargo run --bin traralink-integrations -- az-convert INPUT.azos OUTPUT.hex ASSUMED_INTERVAL_US
cargo run --bin traralink-integrations -- lightbridge HEX

The Lightbridge CLI command prints an offline example, using an identity clock mapping. It is not ready to submit to a running engine's distinct monotonic clock. A live adapter must authenticate/select the source, validate receiver history and supply an actual clock mapping before forwarding observations.

The integration workspace consumes the adjacent traralink project and the root Lightbridge contracts/decoder. The protocol itself has no dependency on these integrations. No rekordbox, Serato, Denon, Numark or native PRO DJ LINK runtime adapter is advertised by this prototype.

az-device provides a bounded four-deck C backend, guarded experimental AZ-MODS SDK producer and private same-UID local IPC. The protocol's traralink-runtime composes that IPC with mutually authenticated QUIC, selected subscriptions, correlated clocks and a loopback status API. A real C-to-Rust localhost test is documented in the producer README. This does not qualify installed-core compatibility or native four-deck operation.