# PoC run record — blank R1 template

Use this blank record for your own reading, planning or separately authorized reproduction. This is a human worksheet, not a product receipt or an authorization. Leave unobserved values blank. Keep raw reports, request keys and private paths local; use sanitized references here.

## Evaluation and owners
- Goal / decision this evaluation should inform:
- Approved non-secret input / supported operation:
- Exact target / delivered version / operator:
- Operation permission and request reference:
- Software offer, infrastructure and AI cost owner and limit (if applicable):
- Report access / retention / cleanup owner:
- Reviewer and agreed acceptance criteria:

## Prerequisites and route
- Route (planning, retained-run reading, or conditional-existing-operator reproduction):
- Supported administrator handoff:
- Supplied client/service version and endpoint reference:
- Status exit:
- Health exit, component states and exact reasons:
- Unresolved prerequisite and responsible contact:

## Plan and review each criterion

Use the criterion definitions in the PoC guide. Agree on applicability, expected result and evidence before evaluation. Record actual observations only afterward. For reading, cite what the public record reports; do not claim that you reran the operation or checked its raw files.

Manual labels: **MET**, **NOT_MET**, **NOT_RUN**, **BLOCKED**, **NOT_APPLICABLE**. Explain each choice. These labels do not calculate product readiness, product acceptance or permission to execute.

| ID | Criterion | Applicability / agreed expected result | Actual observation / evidence | Manual label / explanation | Reviewer / date |
| --- | --- | --- | --- | --- | --- |
| POC-01 | One question and one route | | | | |
| POC-02 | Eligible installation and operating handoff | | | | |
| POC-03 | Baseline and unknowns | | | | |
| POC-04 | Same Work throughout | | | | |
| POC-05 | Literal product outcome | | | | |
| POC-06 | Matching report files | | | | |
| POC-07 | Human usefulness review | | | | |
| POC-08 | Cost and elapsed-time evidence | | | | |
| POC-09 | Resource closeout | | | | |
| POC-10 | Next owner and resume condition | | | | |

## One Work
- Original request key reference / returned Work ID:
- Run exit / literal Work state / final result:
- Same ID confirmed in list, show and selected report:
- Selected report revision:
- Literal execution count / validation result / retry field / replay field:
- Receipt / closure fields:
- Ambiguous or interrupted request reconciliation, if applicable:

## Report review
- JSON readable and bound to the same Work/revision:
- JSON expected file SHA-256 / actual file SHA-256:
- PDF readable and bound to the same Work/revision:
- PDF expected file SHA-256 / actual file SHA-256:
- Product human-acceptance state (copy literally):
- Separate human review decision / reviewer / date:

Compare physical JSON bytes with `json_file_sha256` and PDF bytes with `pdf_sha256`. `report_sha256` is a different report digest. Reading a historical hash comparison does not perform a new one.

## Cost and elapsed time

Use **MEASURED**, **NOT_MEASURED** or **NOT_APPLICABLE**. For each measurement, specify its unit, period and source; for either other status, give a reason. An unknown bill is not zero. Amounts, limits and comparisons remain blank until supplied or observed.

| Item | Owner / agreed limit / unit | Measurement status / reason | Observed amount / unit | Period / source | Manual comparison with limit |
| --- | --- | --- | --- | --- | --- |
| Software offer | | | | | |
| Compute | | | | | |
| AI / provider | | | | | |
| Storage / backups | | | | | |
| Elapsed time | | | | | |

## Resource retention and closeout

List only resources actually used. Distinguish service, VM, disks, objects, backups and the review record. For a reading-only route explain that no product process was created; choose how to retain your worksheet. Resource actions require the supplied procedure and the responsible owner's authority.

| Resource reference | Owner | Initial state | Intended final state / retention decision | Authorized action / procedure reference | Observed final state / time / evidence | Remaining charges / open item |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |

- Only owned, authorized resources stopped by the named operator:
- Retention and cleanup observations:
- Retention review/expiry date and owner:

## Failure, next owner and resume condition

| Issue / affected stage or criterion | Expected / observed / sanitized reason | Original request or Work reference | Owner / contact reference | Next action / required evidence | Resume condition / evidence | Review date / disposition |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |

- Open item / owner / next action:
- Sanitized support summary if needed:

Preserve an uncertain original request before considering a new submission. Reconciliation, service restart and Work resubmission are different actions. A worksheet decision cannot override the literal product retry field.

## Restart or resume record, only if separately applicable
- Exact action type (reconcile request / service lifecycle / other supplied action):
- Target and in-flight Work reference:
- Supplied procedure / exact authorization reference:
- Before state / intended after state:
- Action actually performed:
- Observed after state / time / evidence:
- Required post-action health and readiness observations:
- Original Work disposition / literal retry permission:
- Resume condition checked / remaining dependency:

## Final human decision and handoff
- Decision about the original evaluation question:
- Reason and criterion-review reference:
- Reviewer / date:
- Observed product acceptance state / source / time, separately:
- Remaining limits (including unmeasured cost or untested customer/AI scope):
- Next action / responsible owner / required resume evidence:

The retained example's PASSED validation is not this record's result. Human review here does not update product state. This template supplies no deletion, bootstrap, restart or retry command. A completed reading record can be useful while operational prerequisites remain open.