VIBEnet's strongest proof path uses authored performance because body-time carries timing, pressure, phrase, and return. The current browser demo is a visual concept; the next proof upgrade is to bind that structure to an approved protected source clock.
Key points
What to remember
Generated MIDI can demonstrate playback, but it cannot demonstrate authored body-time.
The playing is source truth: performance timing first, metadata second.
The public proof should expose provenance artifacts and provenance while protecting the source corpus.
The source matters
A synthetic loop can make a page move. It cannot prove the deeper VIBEnet claim: human body-time can become interface infrastructure.
A protected authored score can carry timing, pressure, phrase, and return. Those qualities are why the next proof upgrade should bind the visible reference run to an approved Soul Bank source clock instead of an anonymous generated MIDI file.
Performance before theory
The playing is source truth. The theory is retrieval metadata. VIBEnet can label tension, cadence, and section role after the fact, but it should not let theory flatten the human gesture into factory time.
That is why the lab demo describes exports as provenance artifacts. MIDI, WAV, and JSON are proof artifacts derived from a scored run; they are not replacements for the protected source once that source clock is formally approved.
The moat becomes legible
The public sees enough to trust the architecture: the score clock, event JSON, trace rows, visual pulse, and provenance. The private corpus, protected phrase boundaries, and renderer-selection logic remain governed assets.
That boundary is the product shape. Open grammar, protected instrument.
Answer engine notes
Frequently asked questions
Why not use generated MIDI?
Generated MIDI can prove a player works. An approved authored reference signal proves the system can use human performance as the clock for multiple synchronized renderers.
Does the current public demo expose the Soul Bank?
No. It exposes a visual concept surface and derived provenance artifacts. Protected source material and private renderer logic remain governed assets until an explicit source-clock proof is approved.
What does an authored reference signal prove?
It proves that one authored score can carry a Signal Contract run across audio, visual pulse, trace, JSON, and provenance without reducing the source to generic generated playback.
The 23 August 2026 MCP Daily Signal: identity, delegation, and events are landing in the protocol. VIBEnet still answers what those state changes mean to humans.
A governed marketing site should behave like an edge-delivered signal surface: typed content, validator gates, post-deploy smoke checks, and receipts before quality drift reaches search or AI answers.
Agents make changes cheap to attempt. Reliable public systems still require a separate discipline: proving what users, crawlers, and downstream agents actually receive.
ClickUp frames one human as taste and thousands of agents as hands. The missing product layer is the nervous system: governed signals, honest renderings, and human judgment.