# Alanine maintained-outcome evaluation pack

## Buyer and recurring obligation
Name the buyer, affected working asset, claim inventory, review cadence,
accountable delivery party, correction owner, and scope limits.

## Sources and permissions
List permitted sources and versions. Record observation dates, failed checks,
and permitted snapshot/export rights. Use public or explicitly authorized data.
Do not include credentials or private records in a public evaluation pack.

## Quality rubric
Define direct source support, material change, completeness, contradiction
handling, acceptable uncertainty, and the required owner review.
Separate factual correctness, automated checks, reviewer judgment, and acceptance.

## Fair baselines
Compare the current process, a strong single agent with tools, a deterministic
workflow, a same-provider team, and independently operated specialists.
Use the same brief, source permissions, output format, deadline and quality floor.
Keep a held-out test set. Document configurations without revealing secrets.

## Run and correction record
Record claim and source references, affected artifacts, previous wording,
proposed replacement, reasoning, reviewer decision and update status.
Distinguish no material change found from sources not checked.

## Full costs
Include model/tool spend, supplier fees, integration, operator time, buyer review,
retries, failures, revisions and recovery. Report cost per accepted deliverable
and per completed correction, with quality results alongside efficiency.

## Outcome measures
Count missed material changes, false alerts, unsupported claims, unnecessary
revisions, buyer review minutes, time to correction and artifacts actually updated.
Report sample size, denominators, uncertainty, and cases where the simpler route wins.

## Reproduction and limits
Provide sanitized inputs, exact steps and known limitations. Obtain permission
before sharing customer work. Publish failures alongside successes.

## Decision
Continue / narrow / redesign, with reasons. Results for one workflow do not
establish superiority across domains. This is not a promise of compensation.