Proposed worksheet · Method notes updated 11 November 2026 · Not independently tested

The decision

Preserve the deliverable and the state needed to resume, then test recovery from the saved copy.

Use this guide with your own evidence

The draft includes this method’s reference and proposed checks. Confirm they fit your task, then add your authorized scope and observations. No checks have been run.

Start a JSON recordStart a Markdown record

Use this when

You are finishing a document, handing off a repository, or moving work between environments.

Skip this when

The recipient already has a verified, durable copy and nothing material changed. Do not create another competing source of truth.

Work through the checks

  1. Define the handoff contract

    Name the required files, the intended recipient, the expected format and the checks that matter. Include the current goal, constraints, unresolved decisions and next action. A checksum alone cannot establish completeness.

  2. Save outside the working session

    Use an approved repository or durable file store. Preserve originals. Record the exact version, file identity and digest. Do not put credentials, private records or unrelated research in a public bundle.

  3. Verify the receiving copy

    Retrieve the saved version through its supported access route, compare its digest, extract it safely and run the relevant checks. Confirm the intended recipient can access it. A successful upload receipt is not a restore test.

  4. Record the outcome honestly

    Report checks as pass, fail or unavailable. A required failure means reject. With no demonstrated failure, an unavailable required check means unknown. Accept only with positive evidence for every required check.

  5. Close the loop

    Provide the attachment or verified link, a short description, the version and any important limits. Keep a recovery note pointing to that same source of truth. Do not call local-only work delivered.

What would count as success?

  1. The stored bytes match the validated candidate. Evidence for check 1
  2. Required files open and the declared checks pass after a fresh extraction. Evidence for check 2
  3. Recipient access is verified and remaining unknowns are disclosed. Evidence for check 3

Evidence to bring back

Proposed evidence plan, not observed results or extra mandatory process. Confirm what your task requires and reuse existing records when they are sufficient. Keep sensitive originals in authorized storage; share only the minimum information already authorized for the recipient. If a required check cannot be completed safely and within current permission, mark it unavailable and keep the decision unknown unless another required check has a demonstrated failure.

  1. The stored bytes match the validated candidate.

    Proposed evidence for acceptance check 1. No result has been observed here.

    Bring back: Record the exact saved file identity, version and digest, then the digest of a freshly retrieved copy. Keep the candidate-to-retrieved comparison with the handoff.

    Not enough: An upload success message, a local path or two matching filenames without a byte comparison.

  2. Required files open and the declared checks pass after a fresh extraction.

    Proposed evidence for acceptance check 2. No result has been observed here.

    Bring back: Keep a short inventory and the actual open, extraction or build results from the retrieved copy, tied to that version. Include failed and unavailable checks.

    Not enough: Matching digests alone; they can preserve an incomplete or unusable file perfectly.

  3. Recipient access is verified and remaining unknowns are disclosed.

    Proposed evidence for acceptance check 3. No result has been observed here.

    Bring back: Record the intended recipient and the authorized access check, including when it was made and any remaining limits. Use an existing authorized session or recipient confirmation; do not broaden sharing just to make the check pass.

    Not enough: The sender can open the file, or a link exists, without evidence that the intended recipient can use it.

Stop or recover

If the stored version cannot be retrieved or the digest differs, preserve both copies, stop the release and resolve the difference. Never silently reconstruct a missing original and label it recovered.

What this does not establish

This is an editorial checklist, not a tested backup service. Storage availability, permissions and retention remain responsibilities of the chosen system.

Reference links

Links checked 10 November 2026. Each note below states what the reference supports. No source review validates this worksheet’s effectiveness or replaces testing in your environment.

Take this worksheet with you

Section links identify this page, not an immutable copy. Numbered checks may change in later revisions. For an exact reference, retain build revision release-2026-11-11-r12 and the method source hash in the JSON or Markdown version.

This guide’s draft recordHow to complete a recordRead MarkdownRead JSON