Replay Manifests
A replay manifest says whether the captured, versioned evidence is sufficient for a safe replay attempt. It does not run a replay.
What eligibility answers
replay-manifest/v1 is an immutable assessment carried by a frozen replay configuration. It binds the source execution, durable evidence references, runtime capability, opaque replay reference, adapter identity/version, and declared isolation guarantee. Its hash is a consistency binding, not proof that a runtime snapshot or an external mutation is true.
Eligible and ineligible
An execution is eligible only when the required evidence, capability, tool-call identity, dependencies, and isolation declaration are present. An ineligible manifest records stable, privacy-bounded reasons such as missing capability or missing durable evidence.
A failed execution can be replay-eligible if its frozen evidence is complete. Conversely, a SUCCEEDED receipt alone does not establish eligibility: a receipt reports an outcome, while a manifest assesses replay-specific evidence and isolation.
Adapter availability is separate
Eligibility is historical evidence. Adapter discovery is an operational condition. A manifest can be eligible even when the current worker does not have the required adapter; that replay fails explicitly as unavailable rather than changing the historical classification.
Replay boundaries
Not every replay is a workflow reconstruction
AIGP supports historical execution reconstruction and adapter-owned controlled counterfactual execution through separate contracts. Neither promise means that every framework workflow, checkpoint, private prompt, or external side effect can be reconstructed.Read Replay Management for the lifecycle and Controlled Replay for isolated counterfactual investigation.