VIBENET · REFERENCE RUN · DOCUMENTED REPLAY

Hear truth drift before the dashboard explains it.

The Drift Recovery Run replays a documented SERPRadio production defect as a static fixture: source truth says book now while the rendered surface says monitor. The production correction was implemented and verified separately; this page demonstrates how the mismatch becomes perceptible.

NORMALThe agent is working.0:00 into the run · task.received

ACT I · Start · nominal

State is derived, not decided.

The agent starts normally.

The run arrives with a stable task and no attention required.

state: nominal · event: task.received

Modulation layer

State is where the system is. Modulation is how it moves.

Surface Fabrication Detected

Source truthaction = book_now

Rendered surfaceaction = monitor

SURFACE_FABRICATIONThe surface looks calm, but the source binding broke. VIBEnet makes that truth drift perceptible before the page becomes the postmortem.

ContractSchema validfollowing clock

ClockShared runfollowing clock

AudioScored reference audiostanding by

PulseVisual fieldstanding by

TraceReadable rowstanding by

ReceiptReceipt availablestanding by

nominal — Expected operating state. Nothing requires attention.

What you're hearing

Scored reference audio · 37.7s static fixture. The receipt holds at resolution; replay is explicit.

00:00 - 00:14Calm bedThe run opens restrained while evidence gathers.
00:14 - 00:21Pressure loopThe motif tightens as motion rises without progress.
00:21 - 00:29Held handoffThe score holds instead of pretending the answer is resolved.
00:29 - 00:37Recovery / resolveThe melody opens back up after the repair path is preserved.

Chapter rail

StartThe run opens cleanly and gathers evidence.

SpinActivity rises while progress thins out.

Confidence SplitThe page says monitor while source truth says book now.

HandoffThe system asks for review instead of pretending it is done.

RecoveryThe claim is retracted and the run lands with uncertainty preserved.

Inspect all 13 fixture events

1. task.received · nominal · The agent starts normally.
2. planning.decomposed · advisory · The agent decomposes the work.
3. tool_call.issued · advisory · The agent asks another system for evidence.
4. retrieval.sources_returned · advisory · Sources return, but trust still has to be earned.
5. tool_call.reissued · warning · The run starts spinning.
6. retrieval.low_yield · warning · More motion, less evidence.
7. tool_call.reissued · warning · The run circles.
8. budget.elevated · warning · The run spends more attention.
9. surface.fabrication_detected · critical · The surface fabricates a calm answer.
10. grounding.check_failed · critical · The guard refuses the false finish.
11. handoff.requested · handoff · The system asks for human attention.
12. claim.retracted · recovery · The unsupported claim is pulled back.
13. task.completed · recovery · The run recovers with evidence.

Receipt: the page contradicted its source.

What happened: A search-facing surface contradicted its source claim. VIBEnet did not ask the renderer to invent truth; it carried the mismatch as state, changed the signal, and preserved the evidence. Audio source: scored reference audio. Selection: static fixture.

Make my system audibleUse the same grammar on an agent run, crawl event, deploy, queue, or workflow.

Source truth: action = book_now
Rendered claim: action = monitor
Defect: SURFACE_FABRICATION
System response: warning signal emitted; repair brief queued; human review recommended.
Proof: The same Signal Contract event drove the pulse, state cue, trace, and receipt.

What kind of proof is this?

Every example names its evidence boundary. A replay is not a live feed, and an illustrative pattern is not presented as an operating integration.

Drift RecoveryDocumented replayA documented production defect replayed as a static scored fixture.

Agent traceBrowser-local previewSample data is mapped locally in the browser; nothing is uploaded.

Enterprise workflowIllustrative patternA governed translation pattern, not a connected enterprise feed.

Live public sourcesChecking public feedWaiting for typed source health; no activity count is inferred.

Five principles you just heard

The Drift Recovery Run is not only a story. It is five first principles of human attention at machine scale—each act sentence names the operator decision.

State is derived, not decided. Renderers express governed state; they do not invent source truth.
Motion is not progress. Rising activity without evidence is a warning, not a success.
A calm surface can hide a broken truth. Source book_now vs surface monitor is a fabrication—open the receipt above.
When grounding fails, the system asks. Handoff is a feature; silent certainty is a defect.
Recovery is retraction, then re-grounding. Confidence returns only with evidence, not vibes.

Next: see unobserved vs idle (zombie principle), then preview a Listening Receipt without uploading secrets.

You heard the proof. Now choose what to make audible.

The same governed pattern can translate an agent trace, a fleet doorway, an AI-search truth break, or an operational handoff. Each path names the source, the failure shape, the decision, and its current proof status.

Browser-local preview

Agent Observability

How do teams monitor AI agents without watching every trace?

Source: A browser-local sample trace with tool calls, retries, handoff, and completion.
Failure shape: The run stays busy while useful progress thins out.
Rendered transition: nominal -> advisory -> warning -> handoff -> recovery
Decision supported: Know when to inspect, intervene, or let the run continue.

Try the agent trace

Documented replay

AI Search / Content Truth

How do teams detect AI-search content drift before it reaches users?

Source: A documented SERPRadio production defect: source action book_now, rendered action monitor.
Failure shape: A search-facing surface contradicts its governed source state.
Rendered transition: nominal -> warning -> critical -> handoff -> recovery
Decision supported: Queue a repair brief and human review before the wrong claim becomes canonical.

See the content-truth proof

Illustrative pattern

Enterprise Operations

How do operations teams supervise autonomous workflows without another dashboard?

Source: A governed workflow pattern for incidents, approvals, queues, and launches.
Failure shape: A consequential state change is buried inside ordinary operational motion.
Rendered transition: nominal -> advisory -> warning -> handoff -> recovery
Decision supported: Direct human attention to the transition that changes the operating decision.

Map an operations workflow

Illustrative pattern

Agent Fleet Control

How does one human supervise thousands of agents without 3,000 chat windows?

Source: An illustrative fleet pattern plus executable PerceptualMixer01 lab: many lifecycle events compressed into governed attention slots with drill-down.
Failure shape: Green dots and chat walls collapse observer health, job success, and authority into one misleading signal.
Rendered transition: nominal -> advisory -> warning -> critical -> recovery -> opportunity -> handoff
Decision supported: Know which agents need human taste now, which crossed a boundary, and which evidence is incomplete.

Run the attention mixer

Show technical receipt (Signal Contract v1)

{
  "schema_version": "1.0",
  "id": "receipt_vibenet-drift-recovery-run-demo-v1",
  "occurred_at": "2026-05-06T00:00:00Z",
  "producer": "vibenet.signal-demo",
  "entity": "serpradio.demo.best_time_to_book",
  "event": "demo.receipt.rendered",
  "channel": "warning",
  "valence": 0.5,
  "energy": 0.72,
  "tension": 0.64,
  "intensity": 0.68,
  "hue": 32,
  "pulse": 0.66,
  "metadata": {
    "receipt": {
      "demo_id": "vibenet-drift-recovery-run-demo-v1",
      "mapping_seed": "drift_recovery_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.5,
        "energy": 0.72,
        "tension": 0.64
      }
    },
    "audio_source": {
      "kind": "reference_audio",
      "asset": "/audio/vibenet/frontier-overture-hero-loop.m4a",
      "track_id": "frontier_suite_movement_i",
      "selection": "static_fixture"
    }
  }
}