VIBENETAgents work. You hear it.

Signal Demo

Proof of Concept: Systems you can sense.

Watch the cybernetic loop in action. A signal enters, the modulation layer shapes the transition over a shared clock, and multiple renderers let you perceive the state without reading a dashboard.

Read the protocol

1. Signal event

What entered?

A schema-valid fixture enters as a renderer-facing Signal Contract event.

eventcontractclockrenderersreceipt
event demo.receipt.renderedchannel advisoryVET 0.62 / 0.78 / 0.44
View raw payload
{
  "schema_version": "1.0",
  "id": "receipt_vibenet-reference-run-signal-demo-v1",
  "event": "demo.receipt.rendered",
  "channel": "advisory",
  "valence": 0.62,
  "energy": 0.78,
  "tension": 0.44,
  "intensity": 0.66,
  "pulse": 0.62
}

2. Shared demo clock

00:00Ready
Signal eventShared demo clockRenderer responseReceipt

3. Audio

Scored reference audioReady for user-started playback

Visual

Pulse renderernominal channel, 0% through the fixture.

4. Receipt

Receipt availableStatic fixture selection. Schema-aligned receipt stays inspectable.
event: demo.receipt.renderedtrack: frontier_suite_movement_iselection: static_fixture
Schema validSignal Contract v1.0 event shape.
Scored reference audioPublic browser playback asset.
Static fixtureDeterministic fixture only.
Receipt availableReceipt names what rendered.

Technical detail

Inspect the trace, contract, exports, and adapter path.

These panels keep the evidence available without making raw JSON the first thing a buyer has to parse.

Demo clock

Reference run00:00 / 00:37
event enterscontract updatesrenderers respond

Current state

Opening cellnominal

Browser surface

SSR shell is live. Browser playback and exports wake up after hydration.

State

What changed?Signal Contract carries the renderer-facing event.
nominaladvisorywarninghandoffrecovery

Browser capability checks and export controls activate after hydration.

Protocol specPlain English GuideCybernetic ManifestoGovernance boundary

Time

When does it move?The shared demo clock keeps the trace, audio, and visual field together.

Live trace

  1. 0.00sMIDI 50Opening cell, nominal channel, velocity 0.53
  2. 3.66sMIDI 57Statement, advisory channel, velocity 0.59
  3. 7.33sMIDI 62Main riff rise, advisory channel, velocity 0.65
  4. 14.66sMIDI 65Frontier drive, warning channel, velocity 0.74
  5. 21.98sMIDI 69Suspension hold, handoff channel, velocity 0.77
  6. 29.31sMIDI 74Final chorus, recovery channel, velocity 0.68
  7. 36.63sMIDI 76Cadence, recovery channel, velocity 0.56

Renderer

Which sense receives it?The same event can become sound, pulse, trace, JSON, and export artifacts.
Audioready for user-started playback
Visual pulsechannel nominal; progress 0%
Contract paneprovenance and schema-aligned receipts stay inspectable.

Receipt JSON

{
  "schema_version": "1.0",
  "id": "receipt_vibenet-reference-run-signal-demo-v1",
  "occurred_at": "2026-05-06T00:00:00Z",
  "producer": "vibenet.signal-demo",
  "entity": "demo.reference_run",
  "event": "demo.receipt.rendered",
  "channel": "advisory",
  "valence": 0.62,
  "energy": 0.78,
  "tension": 0.44,
  "intensity": 0.66,
  "hue": 210,
  "pulse": 0.62,
  "metadata": {
    "receipt": {
      "demo_id": "vibenet-reference-run-signal-demo-v1",
      "mapping_seed": "reference_run:evt_demo_001",
      "source_route": "/demo",
      "timestamp": "2026-05-06T00:00:00Z",
      "lufs_target": -16,
      "brand": "vibenet",
      "signal_contract_version": "1.0",
      "vet": {
        "valence": 0.62,
        "energy": 0.78,
        "tension": 0.44
      }
    },
    "audio_source": {
      "kind": "reference_audio",
      "asset": "/audio/vibenet/frontier-overture-hero-loop.m4a",
      "track_id": "frontier_suite_movement_i",
      "selection": "static_fixture"
    }
  }
}

Fixture

Truth Layer -> Render Layer

This is a second-order cybernetic loop. The state is derived, compressed into a contract, modulated over time, and rendered for human perception.

1. Truth Layer
Reference fixture selected
2. Signal Layer
Contract emitted
3. VET Coordinates
Valence, Energy, Tension
4. Modulation Layer
Shared clock transition
5. Render Layer
Pulse, audio, traces

Mapping legend

One signal, one sequence

1. Truth LayerBefore anything becomes sound, the system identifies the state. A public-safe fixture enters the proof as an authorized truth.
2. Signal LayerThe state is compressed into a Signal Contract containing semantic channel, VET coordinates, and provenance.
3. VET CoordinatesThe signal defines the emotional shape of the state. Is it good or bad? How intense? How unresolved?
4. Modulation LayerState is where the system is. Modulation is how it moves. The shared clock advances the state contour safely.
5. Render LayerThe human perceives the change. The browser renders the same sequence across visual and audio paths.

Deterministic contract

Shared demo clock across audio, trace, MIDI, and WAV

Clock length
37.7s
Source clock
Reference run
Playback source
Reference audio
Audio asset
frontier-overture-hero-loop.m4a
Selection
Static public fixture
Derived tempo
131 BPM
Control events
7
MIDI export root
50

This route is prerendered and indexable. It demonstrates the public contract shape; protected source material and renderer internals remain outside the page.

Direct answer

What does the VIBEnet demo prove?

It proves that you do not need to stare at a dashboard to understand what an autonomous system is doing. One Signal Contract event drives audio, visual pulse, trace rows, and a downloadable receipt from the same shared demo clock. The event validates against the public schema, so anything you hear or see here can be reproduced by emitting the same shape from your own system.

The audio is a scored, human-performed reference recording selected by a static public fixture — the receipt names the asset and the selection mode. State-driven riff selection is a separate proof layer with honest status on the Research Lab.

Next step

Build an adapter against the same shape.

The proof is intentionally small. Production adapters do the same thing with real system state: normalize the event, validate it, and let governed renderers decide how it becomes perceptible.

Emit your first signalOpen adapter galleryRead adapter rules