Awards and recognition
A validated winner event can earn one focused room state without exposing scoring or private judging data.
Meetings + live events
One event in. The whole room moves together.
VIBEnet gives production systems one governed state to render across sound, lighting, projection, and screens. The creative team authors the look. The local operator controls the room. The receipt preserves what caused each change.
Authorized eventGoverned signalSound · light · screen
The problem
Show systems can move together without sharing a trustworthy cause.
Sound, lighting, projection, and screens often receive separate cues or depend on a person translating state at the desk. VIBEnet keeps one authorized event intact while each renderer expresses it in its own medium.
Plain-English walkthrough
What goes in, what VIBEnet does, and what comes out.
VIBEnet sits between a trusted source and the production system. It does not decide who won, design a lighting look, or address a fixture. It carries one approved change across that boundary without losing its meaning or history.
- 01 · INPUTA source reports a change
For example, an approved awards system reports a winner, or an authorized operator presses GO. The browser proof uses three local scheduled cues so you can inspect the pattern without a real event system.
- 02 · CHECKVIBEnet validates the event
The event must match an accepted shape. When it fires, VIBEnet creates a unique event ID and records the actual time. A stale or duplicate cue does not become a new room change.
- 03 · DESCRIBESignal Contract carries meaning
A small JSON object says what happened, which entity it concerns, and how urgent it is. Renderer values such as channel, hue, intensity, and pulse describe the state without containing fixture addresses.
- 04 · RENDEREach system expresses the same state
On the proof page, the browser changes the table field and reference audio. In a real pilot, the lighting designer maps the same semantic values to approved console looks and the local operator retains GO and fallback.
- 05 · PROVEThe receipt preserves the crossing
The receipt links the source event, scheduled and actual cue times, trigger source, emitted Signal Contract event, and declared boundaries. It never claims that hardware moved when no hardware was connected.
Into VIBEnetEvent facts
Event type, entity, source authority, and source time.
Out of VIBEnetSemantic controls
Channel, hue, intensity, pulse, cue identity, and a receipt.
Outside VIBEnetRoom behavior
Console looks, fixture mapping, safety, GO, neutral, and fallback remain production decisions.
Three-state proof
Room. Focus. Return.
- ROOMNominal
The full room shares one authored ambient state.
- FOCUSOpportunity
One validated event earns the foreground while the room yields.
- RETURNRecovery
A fresh event returns the environment to the agreed room state.
Where it applies
The event changes. The governed crossing stays the same.
Executive meetings
A governed operating transition can move the shared environment while the underlying evidence remains inspectable.
Brand activations
An approved campaign or audience event can drive coordinated renderer expression without becoming fixture logic.
Museums and venues
Environmental or visitor state can become a bounded perceptual cue while local operators retain control.
Operating boundary
VIBEnet supplies cue genesis and evidence. Production keeps control.
- VIBEnet owns
- Event validation, semantic values, timing lineage, and the run receipt.
- Production owns
- Creative direction, cue looks, console programming, fixture mapping, safety, GO, neutral, and fallback.
- The browser proof owns
- An illustrative local room field. It sends no transport and controls no hardware.
Bounded next step
Live Event Signal Pilot
Start with one source event, three agreed room states, one offline rehearsal path, and one receipt. A technical bind is considered only after the production team supplies the actual console input and control sheet.