Acceptance Criteria for Turning Agent Session Evidence Into a Reusable Product Package: What Must Be Proven

The direct answer

Write a test for “source sessions are frozen and inventoried” before execution and keep “cleaning a transcript without extracting a contract” as a release-blocking counterexample.

For turning agent session evidence into a reusable product package, the relevant audience is teams with successful Claude or Codex sessions that cannot yet be replayed, tested, or handed to another operator. The decision should cover session freeze, provenance extraction, contract recovery, procedure definition, replay fixtures, test mapping, decision records, and certification gates. The supplied boundary starts with Claude or Codex session logs plus an explicit product goal and ends with the catalog's fifteen-artifact product package, presented in reviewable form.

Distillation can organize observed execution evidence, but it cannot manufacture missing provenance, prove product demand, or certify a result outside the stated gates.

Turn each requirement into a proof obligation

The expected deliverable is the catalog's fifteen-artifact product package.

Use Claude or Codex session logs plus an explicit product goal as the controlled starting material.

The independent certifier adjudicates every pass, hold, or fail verdict against these registered statements.

Cover more than the happy path

The normal flow should establish whether “source sessions are frozen and inventoried” holds. An alternate flow should vary a permitted input while testing whether “observations are separated from design judgments” holds. The failure flow should use a fixture demonstrating “replay that relies on hidden operator knowledge” and verify containment.

Add a recovery flow for “tests that cover only the successful source run”.

Judge evidence quality and freshness

For turning agent session evidence into a reusable product package, a result from another environment cannot prove that “the procedure runs in a clean context” holds in the buyer's environment.

Define pass, hold, and fail before execution

Keep sign-off independent

The implementer may produce artifacts, but the independent certifier should judge whether “open assumptions remain visible” holds against criteria written before the result was seen.

Record the business decision of the product owner, the technical evidence reviewed by the procedure author, the acceptance verdict recorded by the independent certifier, and residual risk accepted by the product owner.

A screenshot or self-score cannot prove that “open assumptions remain visible” holds under the failure condition “an artifact package with no reopen conditions”.

Reopen criteria when the system changes

Changes to session freeze, provenance extraction, contract recovery, procedure definition, replay fixtures, test mapping, decision records, and certification gates can invalidate a test even when the requirement text stays the same.

How the sources bound the acceptance criteria decision

For turning agent session evidence into a reusable product package, the live catalog limits the offer to two elements. The supplied boundary is Claude or Codex session logs plus an explicit product goal. The catalog names the deliverable as the catalog's fifteen-artifact product package. It cannot establish whether “source sessions are frozen and inventoried” holds in the buyer's environment.

Connect those narrow roles to a local fixture for “converting interpretation into observed fact” rather than treating citation status as a pass.

For turning agent session evidence into a reusable product package, limit the conclusion to the documented workflow and let the session analyst retain the current source-to-claim map. A changed workflow requires fresh support for the claim that “the procedure runs in a clean context” holds.

Product-specific acceptance criteria review drills

These drills connect turning agent session evidence into a reusable product package to concrete inputs, failures, acceptance statements, and owners. For turning agent session evidence into a reusable product package, the drills map each criterion to a reviewable verdict.

Acceptance for turning agent session evidence into a reusable product package is judged against a boundary record covering Claude or Codex session logs plus an explicit product goal, never live protected material. The product owner requires synthetic, non-secret cases; messages, writes, state changes, and all other external effects stay inside the fixture throughout and after each case.

Requirement trace

Place a safe fixture showing “cleaning a transcript without extracting a contract” at the boundary tested by the requirement trace review. The product owner records the permitted path and the first denied transition.

Source the test from a documented scope covering Claude or Codex session logs plus an explicit product goal and state the criterion “the procedure runs in a clean context” before execution. The session analyst retains the resulting observation.

The independent certifier links the finding “the procedure runs in a clean context” to go, revise, or stop in the decision record. It does not treat completion of the catalog's fifteen-artifact product package as proof of every outcome. In the requirement trace review, evidence for “the procedure runs in a clean context” maps support to pass, contradiction to fail, and unresolved to hold.

Reopen the case if the operating response to “cleaning a transcript without extracting a contract” changes, even when the title and stated requirement remain the same.

Normal-flow result

Build the normal-flow result review around a case involving “converting interpretation into observed fact”. The session analyst checks which observed state in session freeze, provenance extraction, contract recovery, procedure definition, replay fixtures, test mapping, decision records, and certification gates can support the next step.

Review the scope record covering Claude or Codex session logs plus an explicit product goal under its recorded authority and evaluate whether “open assumptions remain visible” holds. The procedure author owns the evidence gap.

The independent certifier closes the normal-flow result review only after reconstructing why the criterion “open assumptions remain visible” passed or failed. A fluent explanation is not enough. In the normal-flow result review, evidence for “open assumptions remain visible” maps support to pass, contradiction to fail, and unresolved to hold.

A new owner, fixture, or consequence for “converting interpretation into observed fact” sends the normal-flow result review back to the session analyst for review.

Alternate-flow result

Model the alternate-flow result review with a safe fixture involving “replay that relies on hidden operator knowledge”. The procedure author names the affected action and its permitted consequence.

For this drill, bind the fixture to the recorded boundary covering Claude or Codex session logs plus an explicit product goal and the condition “observations are separated from design judgments”. The test owner compares the artifact with a direct readback.

The independent certifier judges the alternate-flow result review against “observations are separated from design judgments”. The next step is authorized only for the part of the catalog's fifteen-artifact product package covered by that evidence. In the alternate-flow result review, evidence for “observations are separated from design judgments” maps support to pass, contradiction to fail, and unresolved to hold.

Do not carry this verdict into a changed workflow, input class, or response to “replay that relies on hidden operator knowledge”; create a new bounded record.

Failure-flow result

Begin with the adverse condition “tests that cover only the successful source run”. During the acceptance criteria review, the test owner locates its first observable effect inside session freeze, provenance extraction, contract recovery, procedure definition, replay fixtures, test mapping, decision records, and certification gates.

Use a scope record covering Claude or Codex session logs plus an explicit product goal as the controlled source for a test of “normal and failure fixtures map to requirements”. The product owner flags evidence from a different state as non-comparable.

When evidence supports the finding “normal and failure fixtures map to requirements”, the independent certifier advances the review; a gap makes the independent certifier keep the catalog's fifteen-artifact product package at hold. In the failure-flow result review, evidence for “normal and failure fixtures map to requirements” maps support to pass, contradiction to fail, and unresolved to hold.

Schedule another failure-flow result review if “tests that cover only the successful source run” acquires a new consequence or reaches a different owner.

Independent verdict

Stage a safe instance of “an artifact package with no reopen conditions” inside an authorized fixture for the independent verdict review. The product owner notes the last trusted state in session freeze, provenance extraction, contract recovery, procedure definition, replay fixtures, test mapping, decision records, and certification gates.

Give the product owner an authorized, read-only boundary record covering Claude or Codex session logs plus an explicit product goal plus the criterion “source sessions are frozen and inventoried”. Their receipt identifies any missing proof.

The independent certifier advances the record only when it can demonstrate “source sessions are frozen and inventoried”. If evidence conflicts, the independent certifier records fail and preserves the prior state. In the independent verdict review, evidence for “source sessions are frozen and inventoried” maps support to pass, contradiction to fail, and unresolved to hold.

The independent certifier reopens the drill if the criterion “source sessions are frozen and inventoried” is judged with a different fixture, policy, or operating state.

Evidence expiry

The evidence expiry review examines a case involving “cleaning a transcript without extracting a contract”. The product owner separates the trigger, current state, and next decision within session freeze, provenance extraction, contract recovery, procedure definition, replay fixtures, test mapping, decision records, and certification gates.

Freeze a description of the boundary covering Claude or Codex session logs plus an explicit product goal before testing whether “the procedure runs in a clean context” holds. The session analyst links each observation to that frozen description.

The independent certifier records a decision for the evidence expiry review that cites the evidence for “the procedure runs in a clean context”. Unsupported parts of the catalog's fifteen-artifact product package remain open. In the evidence expiry review, evidence for “the procedure runs in a clean context” maps support to pass, contradiction to fail, and unresolved to hold.

Repeat the evidence expiry review when the failure case “cleaning a transcript without extracting a contract” appears with new data, permission, or consequences that the product owner did not review.

Frequently asked question

What acceptance criteria should I use for Product Distiller?

Require observable evidence that source sessions are frozen and inventoried and include “cleaning a transcript without extracting a contract” as a negative case. The independent certifier should record pass, hold, or fail before expansion.

A product bridge, with a boundary

The Product Distiller is the relevant sincLLM offer for this narrow problem. The frozen live catalog describes its required boundary as Claude or Codex session logs plus an explicit product goal and its deliverable as the catalog's fifteen-artifact product package. That catalog statement defines the offer and does not establish buyer-specific fit, technical sufficiency, legal compliance, safety, or business results.