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.

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=
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.

Policy mismatch: Template loaded: start where the policy baseline and observed tool authority diverge.

ScenarioEscalation review
Trust delta
-14
Replay posture
Escalation review
StableWarningDrift detectedReplay availableRecovery suggested
Evidence continuity
Partial
Lineage completeness
Gaps detected
Replay confidence
Low
T+00:07 · Step 3

Mission continuity breaks after the tool-scope mismatch.

Trust delta negative

The canned detector marks a negative trust delta because the requested action no longer matches the baseline.

Expected vs observed

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

trust -14
Intended mission path
vendor-read baseline -> drift check -> within authority
Observed tool chain
baseline.compare -> vendor-write -> drift.flag
Drift note: Observed write authority breaks continuity with the vendor-read baseline.

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: vendor.update appears where the baseline expected vendor-read lookup.
  2. 2Compounding: policy mismatch and negative trust delta now point to the same authority break.
  3. 3Actionable threshold: escalation review is recommended once trust delta reaches -14.
Evidence chain
  • baseline: vendor-read
  • observed: vendor-write
  • trust delta: -14
Trust Agent forensic summary
  • ops> drift detector flagged mission continuity break
  • ops> trust delta moved negative against baseline
  • ops> escalation review recommended for human operator
GhostLog explorer
T+00:07.030baseline.comparelineage:vendor-readtrust -8checkpoint:CP-22
T+00:07.260drift.flaglineage:vendor-writetrust -14checkpoint:CP-22
T+00:07.810review.recommendlineage:ESC-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.