Trace / Replay

DEMO DATA
orbitweb00@gmail.com
Governance[02/04]

Trace / Replay

Memory explainability — replay the full pipeline. A write replays raw → extraction (exact prompt + raw output, kept facts & dropped-with-reason) → fact; a read replays query → candidates → ranking → injected/dropped, with the visible miss-signal.

🏰 MOAT
WRITE
  1. raw
  2. extraction
  3. fact
READ
  1. query
  2. candidates
  3. injection
  • kept / injected
  • dropped + reason
  • no miss
EXTRACT LATENCY412ms
FACTS KEPT / DROPPED1 / 2
RETRIEVE LATENCY38ms
INJECTED / CANDIDATES1 / 3
MISS-SIGNALNO
Select a trace to replay
Write replay — raw → extraction → fact

  1. I always want dark mode — it's easier on my eyes. Apply it everywhere.

    source: user · 00000000…0001source_trust: 1.00
Capture & sampling

Traces are sampled out in high-volume production to bound overhead. Full-capture is on for debug tenants and is auto-triggered on a miss-signal, so a regression is always replayable. // TODO live-wiring: tenant sampling rate + enable-full-capture toggle