# One Custom Execution task — blank R1 record

Choose one documented case. Fill this record with supplied facts and actual observations; leave unperformed checks blank. Keep raw reports, credentials and private paths local. A completed worksheet does not change product status or authorize another action.

## Task and scope
- Selected case (helper-preparation / headless-observation / report-verification / admin-configuration / ai-planning):
- Goal and intended deliverable:
- Actual mode (preparation / retained reading / permitted query or file check / separately authorized change / planning):
- Task owner / reviewer:
- Permitted scope / operation approval reference:
- Approved non-secret input / provenance:
- Outside this task:

## Version-specific handoff
- Exact delivery release / client or tool build / supported platform:
- Target and operator reference:
- Source document kind / revision / reference:
- Supported schema and procedure references:
- Target contract / adapter references and revisions:
- Complete supplier request package reference, if required:
- Supplied endpoint or connection-profile reference, kept private:
- Service identity owner / administrator or grant reference, if required:
- Established access / permitted query or operation:
- Report-file access or approved-copy handoff:
- Missing item / responsible owner / next action:

A source document may belong in `draft.source`; it is not the complete R2 request. An Admin Requested change payload is also only one part of a supported request. Obtain the exact missing standard deliverable rather than manufacturing the surrounding fields.

## Before state and intended change

| Observation | Value / state | Revision, where applicable | Source / time | Missing or limited evidence |
| --- | --- | --- | --- | --- |
| Prior retained state | | | | |
| Current observed baseline | | | | |
| Current appliance state revision | | | | |
| Current configuration revision | | | | |
| Intended reported result | | | | |
| Intended stored state | | | | |
| Intended effective behavior | | | | |

- Exact action or command/UI reference:
- Expected revision used for the action:
- Required stop condition:
- Supported method for checking stored/effective state:

## Action and literal result
- Action actually performed / time / target:
- Process exit:
- Status query exit / health query exit, separately if used:
- Original request reference:
- Returned operation / request_id / correlation_id / Work ID:
- Literal status / reason / error.code / reason_code:
- Reached lifecycle_stage / integration revision, if returned:
- Appliance state revision / configuration revision, separately:
- Mutation flag / audit reference:
- Same original request/target/Work comparison:
- Execution count / validation_results / final_result, if returned:
- Receipt / closure / retry/replay fields, if returned:
- Product human-acceptance state, if observed:

R2 semantic denial may accompany process exit 0. Preserve the structured result. A displayed APPLIED response or newer configuration revision records an action; the general Admin projection withholds configuration values.

## Reported, stored and effective state

| Observation | Actual value / state | Supported observation source / time | Evidence reference | Still unknown |
| --- | --- | --- | --- | --- |
| Reported action result | | | | |
| Current state after action | | | | |
| Stored configuration value, if observable | | | | |
| Effective runtime behavior, if observable | | | | |

A retained fixture receipt about stored WARN does not establish the effective runtime value on your installation. Use only the supported observation supplied for your actual target; otherwise leave the field unobserved.

## Existing report-file verification, only if applicable
- Selected Work ID and report revision:
- Authorized JSON/PDF file or handoff references:
- Same Work/revision correspondence:
- JSON readability / expected `json_file_sha256` / observed file hash / comparison:
- PDF readability / expected `pdf_sha256` / observed file hash / comparison:
- PDF versus JSON content comparison:
- `report_sha256`, if retained, recorded separately:
- Verification time / source / limitation:

Use actual returned paths or approved copies. `report_sha256` is not a physical JSON/PDF checksum. Reading a published file comparison is a reading observation, not a new file check.

## Manual review checks

Use **MET**, **NOT_MET**, **NOT_RUN**, **BLOCKED** or **NOT_APPLICABLE** with a reason. These are human worksheet labels. A label cannot grant execution permission, resolve product readiness or update human acceptance in the product.

| ID | Check | Applicability / agreed expected result | Actual observation / evidence | Manual label / explanation | Reviewer / date |
| --- | --- | --- | --- | --- | --- |
| CX-01 | One task and its claim boundary | | | | |
| CX-02 | Exact handoff and missing dependencies | | | | |
| CX-03 | Before state and exact action | | | | |
| CX-04 | Literal result and request correspondence | | | | |
| CX-05 | Matching deliverable and file checks | | | | |
| CX-06 | Reported, stored and effective state | | | | |
| CX-07 | Retained state, recovery and resources | | | | |
| CX-08 | Human review and next owner | | | | |

## Retention and supported recovery disposition
- Intended final state / observed final state:
- Change retained, recovery pending, or another owner-supplied disposition:
- Supported rollback/recovery procedure reference, if applicable:
- Exact recovery authority reference, if applicable:
- Required prior-state reference and expected recovery result:
- Recovery action actually performed, if any:
- Post-recovery observation / readiness / evidence:
- Required history preservation and retained input/result copies:
- Data owner / retention decision / review or expiry date:
- Unresolved effect or recovery question:

Do not invent a rollback command, inverse configuration change, restart or data deletion. A historical backup or prior value does not authorize restore. Disconnecting Admin and stopping a service are different actions; record only the action actually performed.

## Used resources and remaining costs

| Resource reference | Owner | Initial state | Intended final state / retention decision | Authorized action and supplied procedure | Observed final state / evidence | Remaining charge or open item |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |

Use **MEASURED**, **NOT_MEASURED** or **NOT_APPLICABLE** for cost/time items. Include a unit, period and source for measurements; otherwise give the reason. Missing billing is not zero.

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

## Failure and resume handoff

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

For uncertain Admin requests, reconcile the existing pending request. For uncertain Work, preserve the original context and resolve the existing Work before another submission. For missing Helper package/target, request the exact supported standard deliverable. Keep each failed attempt attached to its original record.

## Closeout and final human review
- Task result decision and reason:
- Check-review reference:
- Reviewer / review date:
- Literal product acceptance/state and its source, separately:
- Last completed step / retained or fresh observation:
- Final connection or service state, only if observed:
- Retained files/resources and remaining costs or unmeasured items:
- Remaining limits:
- Next owner / next action / required resume evidence:

For preparation or reading, completing the useful record may be the intended finish even when a later product step remains blocked. Do not substitute the completed teaching example for your own observations.