Skip to content
Evidence Lab
English
EnglishРусский
Esc
↑↓navigate↵open⌘Jpreview
On this page

Handover package

What to preserve after configuration and training.

Result

The client receives an accepted, self-contained package that identifies the working configuration, owned and external components, verified scenarios, evidence, limitations, update rules, recovery path, and support boundary. Old chats and private consultation records are not required to operate it.

Handover manifest

For each component, record its name, purpose, version, owner, account or licence dependency, permissions, configuration location, verification result, update rule, removal procedure, and recovery path. Link the accepted guide and scenario evidence by version.

Actions

  1. Freeze the accepted project instructions, folder structure, configuration, and guide version.
  2. Inventory skills, plugins, connectors, models, scripts, and other dependencies with tested versions and ownership.
  3. Include the task brief, guide, accepted output, and evidence package for every verified scenario.
  4. Add the acceptance protocol, independent-use summary, known limitations, and unresolved manual steps.
  5. Record update, removal, rollback, account recovery, and support-escalation procedures.
  6. Identify who owns each account, licence, credential, configuration, scientific decision, and maintenance action without exposing secret values.
  7. Remove raw diagnostic notes, rejected alternatives, internal consultant instructions, credentials, and unnecessary personal data.
  8. Review the package with the client from its final delivery location and record the readback.

Check

From a clean session and the client-visible location, the client can find the accepted version, start the core workflow, verify a result, locate ownership, recover the last working configuration, and request support. Every link and account boundary is valid for the client, and no internal-only or secret material is present.

If it fails

Keep the handover open if a required step depends on memory, consultant access, an unresolved account, or an unverified version. Document the missing step, assign ownership, and repeat the clean-session readback after correction. Do not use handover to close an incomplete independent-use test.

Next: Support and changes.