Interactive replay prototype

Install -> Replay -> Inspect

A replay-safe, client-side click-through for the centerpiece demo. Walk the success path, then toggle into a failure inspection where the evidence chain surfaces the mismatch.

Start hubFirst replayDocs
Illustrative guided demo only. All events, receipts, trust deltas, and summaries are simulated client-side fixtures, not live customer telemetry. Starter posture is inspect-only where referenced.

Developer replay templates

Jump into preset, simulated replay postures. Templates only preselect scenario copy and starting step.

?template=
Failed tool chainPolicy mismatchRetry stormMulti-agent divergenceTimeoutRecovery chain
Slice AB · inspect a failure

Policy mismatch surfaced

A canned failure path shows how a mismatch, continuity break, and negative trust delta become inspectable evidence.

Multi-agent divergence: Template loaded: replay the point where lineage diverges across orchestration handoffs.

ScenarioEscalation review
Trust delta
-14
Replay posture
Escalation review
StableWarningDrift detectedReplay availableRecovery suggested
Evidence continuity
High
Lineage completeness
Gaps detected
Replay confidence
Medium
T+00:11 · Step 4

Replay reconstructs when the authority boundary changed.

Failure chain rebuilt

The evidence chain points to the exact step where policy and mission state diverged.

Expected vs observed

Simulated replay diff for this step. Values are illustrative fixtures only.

trust -14
Intended mission path
sealed receipts -> locate boundary -> review path
Observed tool chain
RP-406 -> event 03 -> authority boundary break
Drift note: Replay pins the continuity break to the event where vendor.update entered the chain.

Why trust broke

  • Divergence began when the runtime selected vendor.update instead of the vendor-read lookup path.
  • Continuity broke at the policy edge P-104 because the observed tool chain crossed from read scope into write authority.
  • Replay confidence shifted negative after GhostLog GL-3091 and drift scoring agreed on the same authority boundary break.

Multi-step drift replay

  1. 1Drift onset: replay pins the first mismatch to event 03.
  2. 2Compounding: receipt, policy edge, and boundary break line up in the rebuilt chain.
  3. 3Actionable threshold: operator review can focus on GL-3091 and P-104.
Evidence chain
  • breakpoint: event 03
  • policy edge: P-104
  • replay pack: RP-406
Trust Agent forensic summary
  • ops> replay located policy mismatch at event 03
  • ops> mission baseline and requested authority diverged
  • ops> evidence chain is available for review without live claims
GhostLog explorer
T+00:11.080replay.packlineage:RP-406trust -14checkpoint:CP-22
T+00:11.420breakpoint.locatedlineage:event_03trust -14checkpoint:CP-22
T+00:11.890boundary.breaklineage:P-104trust -14checkpoint:CP-22
Same mission, different runtime
OpenAI+6 guided / -12 failure

Fast policy echo, review still required

Same canned mission, simulated as a managed runtime handoff.

Ollama+4 guided / -9 failure

Local receipt chain, slower stabilization

Same canned mission, simulated as a local runtime replay.

Shareable replay snapshot

Exports a static JSON bundle with steps, posture chips, truncated GhostLog events, diff summary, and timeline.

Simulated click-through. No live telemetry, no customer data, no autonomous action.

Starter framing: inspect-only. This prototype previews the replay and failure-inspection workflow while full Runtime Event Explorer acceptance criteria remain deferred.

Start hubFirst replayDocs