Replay

Purpose

Replay retrieves baseline runtime evidence by replay_reference.

Replay is used after a successful Governed Execution when a customer needs to verify or reuse the baseline runtime outcome.

When To Use It

Use Replay when:

• Governed Execution returned a replay_reference.
• The customer needs baseline evidence for review, audit, simulation, comparison, or later traceability.
• The runtime process and replay material remain available according to runtime-authoritative behavior.

Request Boundary

Replay requires a non-empty replay_reference.

The customer should treat the replay reference as the customer-visible lookup reference for runtime replay material. Do not depend on internal replay material, generated contract bodies, filesystem paths, storage layout, logs, tracebacks, or runtime internals.

Response Evidence

A successful replay response may include:

• Runtime response API version.
• Status.
• Replay status.
• replay_reference.
• execution_id.
• contract_reference.
• Replay outcome.
• Bounded errors.

Replay Records remain the atomic evidence object for later evaluation.

Customer Responsibilities

Customers should:

• Store the replay_reference in customer-controlled systems of record.
• Preserve the relationship between replay evidence and the original governed material.
• Decide how replay evidence supports customer review, audit, experiment, release, or approval workflows.

Boundary

Replay evidence does not become customer governance source truth. Replay depends on runtime-authoritative replay availability and current runtime behavior.

Next Step

Use Simulation when evaluating candidate policy setup against replay-derived baseline material.