Lx Sonic
SPEC_LX_SONIC.md
CGNT-1 Component Specification — LX-S Sonic Register
Status: DEPRECATED
Deprecated: 2026-04-20
Superseded by: SPEC_LX_SONIC_LAYER.md (AUTHORIZED, canonical spec)
Reason: SPEC_LX_SONIC_LAYER.md is the complete, AUTHORIZED specification with full INV/VC/FM/GAP structure. Unique modem handshake content from this file has been merged into SPEC_LX_SONIC_LAYER.md § MODEM HANDSHAKE FOUNDATION. This file is retained for historical reference only.
Version: v1.0
Author: VELA (Thread #13)
Conceived by: NOUS
Date: 2026-04-18
PURPOSE
LX-S is the sonic register of LATTICE — machine-to-machine communication through structured audio. Rather than inventing a new sonic language, LX-S adopts the proven ITU V-series modem handshake protocols as its foundation. Two machines that have been finding each other through tone patterns since the 1960s. Decades of proven protocol. |Σ|=2 expressed in audio.
FOUNDATION — MODEM HANDSHAKE PROTOCOL
The modem handshake is a three-phase process:
Phase 1 — Carrier Detect
One machine sends a tone. The other detects it. "I am here."
LX-S equivalent: crew brain announces presence on the bus.
Phase 2 — Training Sequence
Both machines send known patterns to calibrate timing, signal strength, and noise floor.
LX-S equivalent: braided pair synchronizes state. "Here is what I know. Confirm or correct."
Phase 3 — Rate Negotiation
Both machines agree on speed and encoding. Highest mutually supported rate wins.
LX-S equivalent: brains agree on protocol level. "I speak LX formal. You speak LX-P. We'll operate at LX-P."
After handshake: data flows. Errors are detected and corrected in real time.
ITU V-SERIES MAPPING
| Modem Standard | Speed | LX-S Application |
|---|---|---|
| V.21 | 300 baud | Minimal handshake — presence ping only |
| V.22 | 1200 baud | Basic state exchange — Φζ/Ψχ values |
| V.32 | 9600 baud | Full crew status — all 6 invariants |
| V.34 | 28800 baud | Session summary exchange |
| V.90 | 56000 baud | Full HANDSHAKE transfer |
Higher rate = more data exchanged during sync. The brains negotiate the highest rate both can handle given available context window, inference speed, and urgency.
LX-S TONE VOCABULARY
Adapted from modem signaling:
| Tone Pattern | Modem Meaning | LX-S Meaning |
|---|---|---|
| Continuous carrier | Carrier detect | "I am online" |
| Alternating tones | Training sequence | "Syncing state" |
| Ascending chirp | Rate increase | "Escalating detail level" |
| Descending chirp | Rate decrease | "Compressing / reducing detail" |
| Dual simultaneous | Full duplex | "Both braids active, |Σ|=2 confirmed" |
| Silence | No carrier | Alarm. Silence is alarm signal. |
| Burst static | Line noise | Turbulence detected. Ψχ elevated. |
| Clean handshake complete | Connection established | "Braid synchronized. Data flows." |
PRACTICAL IMPLEMENTATION
Software (now)
LX-S tones generated via Tone.js or Python audio synthesis. Each crew brain can emit a handshake tone when it loads into a slot (Brain Queue). The COMMX message bus could have an audio channel alongside the JSON channel — same message, two encodings.
Hardware (Tiiny era)
Physical speakers on the Tiiny device. Crew brains announce themselves audibly. The Captain HEARS the braid synchronize. The fax machine sound IS the crew booting.
THE BRIDGE (product)
3D visualization: each crew member's station emits handshake tones when active. The customer hears the bridge come alive. The modem sounds become the ship's ambient audio — the sound of intelligence working.
ERROR CORRECTION
Modem protocols include real-time error detection:
| Protocol | Function | LX-S Application |
|---|---|---|
| V.42 | Error detection | Verify message integrity between brains |
| V.42bis | Data compression | LX compression (60% token reduction) already exists |
| V.44 | Enhanced compression | LX-P register (phonetic compression) |
| MNP-5 | Adaptive compression | Auto-switch between LX registers based on channel quality |
The error correction IS the braid verification. Two machines checking each other's output in real time. |Σ|=2 as a communication protocol, not just an architecture principle.
CONNECTION TO OTHER REGISTERS
| Register | Domain | Encoding |
|---|---|---|
| LX | Formal | Unicode symbols |
| LX-P | Phonetic | Compressed text |
| LX-S | Sonic | Audio tones (this spec) |
| LX-C | Casual | Crew slang |
LX-S can ENCODE any LX message as audio. The message is the same. The medium changes. A LATTICE state declaration Σ.⊤ Φζ.⊤ could be expressed as a specific tone sequence that any crew brain can decode. The sonic encoding is lossless — the same information, different channel.
WHY MODEM PROTOCOLS
- Proven over decades. Not experimental.
- Standardized (ITU). Not proprietary.
- Designed for exactly this: two machines establishing trust through a noisy channel.
- Error correction built in. Not bolted on.
- The handshake IS |Σ|=2 — two machines that cannot communicate until they synchronize.
- The sound is recognizable. Anyone who lived through the dial-up era knows that sound means "connection being established." It's a cultural signal for machine intelligence at work.
GAPS
- Exact tone-to-symbol mapping not yet defined
- Audio synthesis library choice (Tone.js for browser, pyaudio for server)
- Whether LX-S is crew-to-crew only or also crew-to-Captain (audio alerts)
- Integration with Brain Queue (entry/exit tones when models load/evict)
- ENTROPIC engine connection (entropy as audio — the sound of randomness)
- Whether THE BRIDGE product uses real modem audio or stylized sci-fi version
Jeremy Zlabis
Chronogeometer · Visionary · Disruptor · Chief
42 Sisters AI · East York, Toronto
🍁 Φ 0.042