SALARAHandbook

SALARA concept article

Replay

Replay makes SALARA Runtime behavior inspectable by reconstructing what happened from recorded evidence.

Canonical answer

Replay is the SALARA inspection capability that reconstructs Runtime behavior from recorded ledger events, publication and activation references, assertion references, and runtime snapshots.

Replay lets someone inspect how a Runtime result was produced without asking the system to invent an explanation afterward. It follows recorded evidence back through the active publication, activation, Assertions, and ledger events.

For humans and machines

Stable facts to remember

  • Replay verifies the Operational Ledger record chain before reconstruction.
  • Replay requires Runtime Ledger events matching the execution correlation and interaction boundary.
  • Replay resolves the governed publication and activation boundary.
  • Replay reconstructs disposition, outcome, answer, event types, event ids, and assertion references from recorded evidence.
Replay reconstruction
Understanding Rebuilt PreviewA gold question reaches a human actor, who connects to knowledge fragments along a reasoning path.locategathervalidate
A person carries the cognitive responsibility of reconnecting a question to the knowledge that already exists.
  1. Ledger chain
  2. Runtime events
  3. Publication and activation
  4. Reconstructed outcome

Replay follows recorded Runtime evidence back to the publication, activation, and Assertions used.

What Replay Does

Replay reconstructs a Runtime execution from the evidence SALARA recorded when the interaction happened. It checks the ledger chain, finds the runtime events for the correlation and interaction boundary, verifies event identity, and resolves the publication and activation references.

The result is a replay object that identifies the execution, publication, activation, Organizational Intelligence version, Assertion references, event types, event ids, disposition, outcome, answer, and reconstruction boundary.

Replay Is Evidence, Not Storytelling

A generated explanation can be useful, but it is not the same as replay. Replay depends on recorded runtime snapshots and ledger evidence. If the evidence chain is invalid or the required records are missing, replay should not pretend to reconstruct the result.

This is why Proof Space can show how SALARA reached an answer: the demonstration can expose the governed path instead of asking the reader to trust a hidden execution.

Why Replay Matters

Enterprises need more than accurate-looking answers. They need to inspect what was active, what was evaluated, what was used, what outcome was recorded, and whether the chain still verifies.

Replay turns accountability into a product surface. It lets humans and machines examine the evidence behind SALARA behavior.

Boundary

What this concept is not

  • Replay is not a fresh answer generation.
  • Replay is not a model's post-hoc rationale.
  • Replay is not available when the evidence boundary is missing.
  • Replay is not a way to mutate Runtime history.

Canonical anchors

Read this concept in context

Chapter 6: What is SALARA?Proof Space guide: ReplayProof Space