HANDOVER / OWNERSHIP / UPKEEP

THE MACHINE PASSPORT™

A machine that stays behind needs clear responsibilities. Record them before purchase and confirm them at handover.

Working draft. These are your notes, not agreed contract terms. Do not enter credentials or confidential client details. No automatic saving or submission.

Machine / versionWhich tool and version does this passport describe?Job and limitsWhat it does, who uses it, and what it should not be relied on for.Owner and rightsWho owns the code, accounts and data? What rights are transferred?Where it runsLive address, hosting provider and account holder. Never enter passwords or keys.Running costs and payerHosting, model/API usage, licences, spending limits and who pays each bill.DependenciesServices, models, libraries and licences needed to keep it working.Data and accessWhat is stored, where, who can access it, retention and how to export or delete it.Repair route and support termsWho fixes it, how to reach them, what support is included and when it ends.Stop, export and restartHow to stop operation and billing, preserve required data and restart safely.Handover evidenceSource and account transfer, documentation, acceptance check and agreed date.

10 fields still need an answer: Machine / version, Job and limits, Owner and rights, Where it runs, Running costs and payer, Dependencies, Data and access, Repair route and support terms, Stop, export and restart, Handover evidence.

Your handover draft

ctrl+love / THE MACHINE PASSPORT™
WORKING DRAFT — confirm all terms with the people responsible.

MACHINE / VERSION
TO AGREE

JOB AND LIMITS
TO AGREE

OWNER AND RIGHTS
TO AGREE

WHERE IT RUNS
TO AGREE

RUNNING COSTS AND PAYER
TO AGREE

DEPENDENCIES
TO AGREE

DATA AND ACCESS
TO AGREE

REPAIR ROUTE AND SUPPORT TERMS
TO AGREE

STOP, EXPORT AND RESTART
TO AGREE

HANDOVER EVIDENCE
TO AGREE

Unfilled fields remain unresolved. Filled fields are notes, not proof of agreement.