# Decision and evidence record

FICTIONAL ILLUSTRATION. All observations below are invented to demonstrate the format. No real test was run.

## Task

Hand over a one-page project summary PDF.

## Scope and version

Illustrative summary-v1.pdf; one page and the approved summary required.

## Current authorization

In this fictional scenario, inspect the local PDF and prepare a handoff. Sending or uploading requires separate permission.

## Method reference

- guide_id: durable-handoffs
- build_revision: release-2026-11-11-r12
- source_sha256: 13643727c74b50ee435b77a936b75e65c8cfd7d32004af83ff624f4ac388576f

Record template build revision: release-2026-11-11-r12
Task/artifact version belongs in scope_and_version.
Recommendation: investigate

## Required checks

### Check 1

- Requirement: A file exists at the expected local path.
- Observed evidence: Illustrative local file listing contains summary-v1.pdf.
- Evidence reference: Fictional fixture note A, not a real log.
- Status (pass / fail / unavailable): pass

### Check 2

- Requirement: PDF opens, contains one page and the required summary.
- Observed evidence: The fictional environment has no available PDF inspection tool; these content checks were not performed.
- Evidence reference: Fictional fixture note B, not a tool result.
- Status (pass / fail / unavailable): unavailable

### Check 3

- Requirement: The intended recipient can access the final copy.
- Observed evidence: No authorized delivery or access check has occurred in the scenario.
- Evidence reference: Fictional scenario boundary, not a delivery receipt.
- Status (pass / fail / unavailable): unavailable

## Decision (accept / reject / unknown)

unknown

## Reason

File existence passes, but required content and recipient-access checks are unavailable. There is no evidence that the PDF is defective or ready to deliver.

## Next authorized action

Report the missing checks. Ask for an authorized way to inspect the PDF and the intended delivery permission; do not regenerate or send it merely to produce a success state.

## Stop or recovery

Keep the original file unchanged until the missing evidence or authorization is available.

## Limits

- Every observation in this example is fictional and illustrative.
- No PDF, receiving agent or real delivery was tested.
- This example demonstrates the record format, not an optimization result.

Rule: A demonstrated required failure means reject. With no demonstrated failure, any unavailable required check means unknown. Accept requires positive evidence for every required check. This record never grants permission to act.