No new job starts under it from the day your withdrawal arrives.
You own your skill, always and forever, and the way out is yours with it: on your own say, for nothing, without asking anybody. A job already underway finishes, because stopping a machine mid-pass is its own hazard. That is the one delay in it. Deleting every copy takes longer again, because backups run to a horizon. You are told every one of those dates and we do not let a short one stand in for a long one.
What becomes of a way of working over the years, and what ending it looks like on the day you decide to.
Over the yearsFind it, stop it, delete it, and tell you the true date.
- 01Find everything that saw your workEvery session, and everything built from one that a machine actually runs. If we cannot find them all, we cannot honour a withdrawal, so the record of what went into what is kept from the first day rather than assembled when somebody asks.
- 02Stop it starting anywhere new, the day it arrivesNot at the end of a term, not at the next release, and not when it is convenient. A job already running finishes, because stopping a machine mid-pass is its own hazard, and nothing else starts under it from that day.
- 03Delete every copy we hold, raw and derived alikeThe recording and what was made from it. Rebuild what can be rebuilt without you, and withdraw what cannot. Where material went into a model under a learning or a derivative licence, it comes out at that model's next revision, on the date you were told before you agreed, and nobody here will tell you a model has forgotten you.
- 04Confirm to you, with the true completion dateIncluding backups. The real date, not the convenient one.
The withdrawal itself stays on file, because a record that deletes its own withdrawals cannot show it honoured one.
From your notice to the last copy gone, in the order it happens.
You do not have to argue for it or wait for us to be ready, and nothing in it is left to be settled when the day comes. This is what happens between your notice arriving and the last copy being gone.
Your notice arrives.
You give notice. The permission under the session is yours, given and withdrawn at will, so it needs nobody's agreement but yours, your employer's included. The day your notice arrives is the day everything below is counted from.
Nothing new starts under it.
A way of working is the name here for how a named person runs a machine once it has been recorded, admitted and built. From that day no crew can choose your way of working for a job. It stops being on offer, and a way of working that is not on offer cannot be chosen, so it does not run. Nothing waits for a term to end or a release to come round.
The running job finishes.
A job already underway finishes, because stopping a machine mid-pass is its own hazard. Its hours are counted and paid like any other, and they are the last hours counted under it.
It is out of service.
When that job is done, nothing runs it anywhere. It is the first of the two dates you are told.
Every copy goes.
Every copy we hold is deleted, raw and derived alike, backups included. Where material went into a model under a learning or a derivative licence, it comes out at that model's next revision, on the date you were told before you agreed, and nobody here will tell you a model has forgotten you. Backups run to a horizon, so this takes longer than taking it out of service, and the day the last copy is gone is the second date.
You are told.
You are told both dates, and the shorter one is never allowed to stand in for the longer one. When the second has passed we confirm it to you, with the true completion date, and the withdrawal itself stays on file.
Ending a licence never means a machine stops where it stands. It means the next one does not start.
Out of service is one date. Every copy gone is another, and it is later.
Taking a way of working out of service and deleting every copy of the record are two different jobs, and they finish on two different days. Anyone who gives you one date is giving you the short one and letting it stand for both. We give you both, and we say which is which.
The first date: out of service.
Nothing new starts under it from the day the withdrawal arrives, the job already underway finishes, and then it comes out of service. The count under it closes where the running job finished, and the accounting you are owed runs to that day.
The second date: every copy gone.
Deleting every copy takes longer than taking it out of service, because backups run to a horizon. Every copy we hold is deleted, raw and derived alike, and the date we give you for that is the day the last copy is gone, backups included, and not the day the first one was. Where material went into a model under a learning or a derivative licence, it comes out at that model's next revision, on the date you were told before you agreed, and nobody here will tell you a model has forgotten you.
You are told both dates, and the shorter one is never allowed to stand in for the longer one.
The covenant, clause five
A model cannot be un-trained.
A model is the thing people mean when they say AI, and most of what is called AI learned from people who were never asked and never paid. You are right not to trust it. Here, nothing of yours goes into one because you were recorded. It goes in only if you say yes to that on its own, and nobody is asked for that yes before what it pays goes on the covenant.
A model learns from many people's records at once. If yours goes in, it goes in with everybody else's, and there is no part of it that can be lifted out and handed back to you, any more than you could take one load of gravel back out of a pad that is already built.
Taking a way of working out of service is straightforward: it stops being available and nothing new runs it. If a record has been used to train a model, that is a different problem, and the weights cannot be unpicked.
So what we can promise is only what is possible: no new deployments from the day the withdrawal lands, and the material removed at the next revision of that model, with the date stated before you ever agree to it. That is a real limit and you are entitled to know it before you decide, rather than after.
A record used to train a model is a different thing from a record used to run a machine, and it gets a different yes. No agreement to anything else ever covers it.
The owner hears first, so nobody is left short.
An owner who planned a job around your name should not find out on the morning. So the owner whose crew is running your way of working is told the day your withdrawal arrives, and told the day it comes out of service, so the next job can be planned around it.
The running job finishes, and the next one goes back to their own operator's way or the basics.
The job already underway finishes, and its hours are counted and paid like any other. The next job begins with a fresh choice, made by a person on their crew, and your name is no longer among the choices. The machine works as it always has, running the way their own operator taught it or the basics it came with, with a person on the crew saying go.
They see the count under your name close where the last job finished, on the same record you see, and that is what they are charged for. A withdrawal changes what is on offer to choose from, and nothing else about their day.
Give notice, and nothing new starts under it.
The job already running finishes, and nothing else waits on it.
The true date, what was deleted, and the accounting to the day it stopped.
A withdrawal you cannot check is a promise you are taking on trust. These are the things you can ask us for, and each of them comes from the record rather than from anybody's memory.
The day every copy is gone.
Backups included. The real date, not the convenient one, and never the shorter date standing in for it. Where a record has gone into a model, the date the material is removed at the next revision is stated before you ever agree to that use.
Every session, and everything built from one.
Session by session, because each session carries its own identifier and signature. The record of what went into what is kept from the first day rather than assembled when somebody asks. So the list of what saw your work exists before you ask for it, and what was rebuilt without you is on it too.
The hours to the day it stopped.
Session by session, up to the last job that finished under it, checked against the record that shows who cleared the work. The count is kept in one record that both sides read, so you get an accounting and a right to audit it, and a withdrawal does not shorten either.
All of it is on your own record, which is yours to open and not your employer's.
It is not a penalty, not a clawback, and not a reason to treat you differently.
A right that costs money to use is not a right, and a right that costs you standing is not one either. Withdrawal is written so that using it changes the licence and nothing else.
No penalty.
Nothing is charged for leaving, and there is no term to see out. The one delay in it is the job already underway, and that delay is a hazard being avoided rather than a fee being charged.
No clawback.
Nothing already paid is clawed back. The hours your way of working worked were worked, and they stay paid. The accounting runs to the day it stopped and closes there.
No different treatment.
Withdrawing is a right you were given on the day you said yes, and using it is not held against you. Your employer wanting it for discipline or a dismissal is a use you did not say yes to, and a withdrawal does not change that: it is not one we supply it for. If you ever want to be recorded again, that is a fresh yes, given on its own, and nothing about the withdrawal counts against it.
And nothing here stops you working, teaching, bringing on apprentices, or going somewhere else tomorrow. We never ask for that and we would not take it.
It belongs to the person in the seat.
A recording of you working is information about you, so it is yours to allow and yours to withdraw. Privacy law attaches consent and withdrawal rights to that directly. The entitlement to be paid is created by the agreement itself, and the right to end it is written into the same agreement, against its counterpart on our side, so that neither depends on anybody's goodwill.
The way out is yours for as long as the licence runs, and it does not end with you. After you, the right to end it passes to your estate with the licence and the money. That position is ruled, and counsel is writing the clause.
It does not need your employer's yes.
You gave the consent, so you can take it back, and it does not require your employer's agreement or anybody else's. The right to withdraw, the true deletion date, and the right to know what is recorded belong to the person in the seat, and not to the person who arranged the recording.
It comes apart.
Consent is separate agreements, each given on its own and withdrawn on its own, so you can say yes to one and no to another and the no is honoured without emptying anything else. A withdrawal can be all of it or one part of it, and what it does to each of the three things, the technique, the recording and what we build from it, is set out on whose it is.
It stays on file.
The withdrawal itself stays on file, because a record that deletes its own withdrawals cannot show it honoured one. It is the record that the dates were given and met, and it is kept so that you, or somebody asking on your behalf years later, can see that they were.
A second signature does not take it from you.
A body's signature is asked for before a recording. It is not asked for to end one. A withdrawal is still yours to give on your own, and nobody's second signature is needed to end what your own yes began.
You gave the consent, so you can take it back.
It does not require your employer's agreement or anybody else's, and no second signature is needed to end what your own yes began.
A change of ownership should be a reason to withdraw, on its own.
You agreed to terms offered by particular people. If this company changes hands, that is a fair moment to decide whether you still want to be in it. The right to walk at that moment, on your own say, is one of the points the agreement is being built around, so that it does not depend on whoever ends up holding it.
What happens to it over the yearsFor the owner, the operator and the people who can say no.
You are told the day it arrives. The job your crew is running finishes, and its hours are counted and paid like any other. The next job goes back to your own operator's way or the basics the machine came with, and the count under the withdrawn name closes where the last job finished, on the same record you already see.
Your skill stays yours whatever you decide here, because it was never on the table. Give notice and nothing new starts under it. The job already running finishes, and that is the one delay in it. No penalty, no clawback, no fee for walking away. You are told the day it comes out of service and the day every copy is gone, and the shorter one is never allowed to stand in for the longer one.
A withdrawal never stops a machine where it stands. A job already underway finishes, because stopping a machine mid-pass is its own hazard, and the same order of authority holds through a withdrawal as through any other day. The way of working that is being withdrawn has no more say in how the job ends than it had in how it started.
The right to withdraw belongs to the person in the seat, and it does not require their employer's agreement. What a withdrawal does to each of the three things is on whose it is, and the covenant carries the clause.
Ask before you begin.
If you want to know what ending it would look like before you begin it, ask.