Clearing the machine and starting the count are one act.
A machine is cleared to run under a named way of working. That clearance is a signed row, and that row is the meter. The invoice a licensee receives and the hours the hand is paid for both come off it. Neither can be adjusted without the other, because there is no other.
Five things, signed in one row.
A count line is not a log entry, and it is not a timesheet reconstructed at the end of a month. It is one row, made at the machine, naming what ran, whose way of working it was, who cleared it, and where the hours start and stop.
- The machine
- One machine, identified the way its owner identifies it.Not a fleet, not a site, not a job number.
- A named skill
- One named way of working, chosen by name before the work starts.No default and no last-used.
- The person who cleared it
- Whoever authorized that machine to run under that name, signing under their own.A person on the crew, at the machine.
- A start
- The moment the clearance took effect.Not the moment a system noticed.
- A stop
- The moment it ended.A row with no stop is an open row, and an open row is not invoiced.
Nothing else is in it. A count line carries no recording and no part of one. It does not describe the work, does not score it, and says nothing about the person who did it beyond the name the licence runs under. That restriction is a rule rather than an omission: a record is never supplied to assess a person, to an insurer or to anyone else.
The rate is not in the row either. The licence sets the rate; the row sets the hours. Keeping the two apart is deliberate. One of them is a term negotiated between companies. The other is signed at a machine by somebody who is not negotiating anything, and it has to stay that way to be worth reading.
At the machine, by the person who cleared it.
The ordinary way to produce a count is to collect what machines reported, reconcile it later, and issue an invoice from the reconciliation. That count is a reconstruction. Everything that can go wrong with it goes wrong after the fact, in a place nobody who was there can see.
The ordinary way
Machines report. A system collects. A person reconciles. An invoice comes out of the far end. Each step is a chance to correct the one before it, and a correction made a week later carries nobody's name and no record of what it replaced.
The hand whose hours are being counted was present at none of it.
How it is done here
The person clearing the machine signs the row as they clear it, under their own name, in front of the machine. There is nothing to reconcile afterwards, because there is nothing to reconcile it against.
A later correction is a separate signed act that says what it corrects. The row it corrects stays where it is.
This is why clearance and count are one act rather than two systems kept in step. Two systems kept in step drift, and when they drift somebody decides which of them was right. Making them one row removes the decision, and the person who would have made it.
It also removes the ordinary way of adjusting a count quietly. A change to what is invoiced is a change to what is owed for the hand's hours, in the same object, at the same moment, visible from both ends. There is no version of this in which a licensee is billed for an hour the hand is not paid for, or the hand is paid for an hour no licensee was billed. The row does not have two faces.
The act that clears a machine to run is the act that starts the count. There is no second step, and no room for one.
The hours a machine ran, and no other hours.
Not a seat, not a subscription, not a site fee. One named way of working, on one machine, cleared by one person, for the time it was in use.
The invoice and the payment are the same row, read from opposite ends.
What goes out to a licensee and what comes back for the hand's hours are not two records reconciled against each other. They are one record read twice. The dashed rules below mark the places a second record would have to sit, and does not.
Fig. 1 — One signed row, two readings. Dashed rules mark where a second record would have to be, and is not.
Reconciliation is work that exists because there are two records. Remove the second record and the work goes with it, along with every argument about which version was correct.
A licensee reads the row for what they are charged. Even Steven reads the same row for what is owed to the person it names. Both readings run over one signed object, and neither party has to take the other's word for what it says.
A count is a record of custody. It is not a claim about truth.
That distinction is the honest one, and most of what is sold as auditable counting depends on the two being quietly confused.
A mechanism can make an already-recorded fact hard to alter afterwards. That is a real property and a useful one, and it is what sealing does. It says nothing whatever about whether the fact was recorded correctly in the first place. A record kept perfectly around a wrong number is a wrong number, kept perfectly.
Making the original recording trustworthy is a different problem, and the same tools do not touch it. It is solved by where the signature sits. Ours sits at the moment and the place the thing happened, in the hand of a named person who is there — the person on the crew who clears the machine, in front of the machine, at the instant they clear it. Not a system reporting on itself an hour later. Not a reconciliation run over somebody's books at the end of a month. Not a party with an interest in the answer, signing in bulk, afterwards.
So the claim a count line makes is a claim about custody: this row was made here, then, by this named person, and has not changed since. That is a smaller claim than this is true. It is also a claim somebody who does not trust us can check, which the larger one never is. We make the smaller claim and we make it exactly.
We stand behind the money owed, the count and the deletion. We do not stand behind the machine, the job or the output, and no part of any safety case rests on anything we supply.
Being paid is not the same as being paid correctly.
There is one deployed scheme that pays named contributors per use. It is worth reading closely, because it demonstrates the rule this company is built on, and because its own stated limit is the reason our audit page exists.
In that scheme a person contributes under their own name, is paid each time their contribution is used, and is paid on a weekly cycle. What it shows is narrow and important. Per-use payment to an identified person works exactly where that person's contribution stays a selectable, addressable artefact: select it by name, count the uses, pay the name. Once a contribution is one of millions dissolved into a general model's parameters, the configuration that made it selectable is gone, and the counting goes with it.
The limit follows from where the count is made. A contributor can see that they were paid. They cannot see whether they were paid correctly.
That is not an arithmetic failure. It follows from where the count is made. Where the sole record of use is the payer's own record, a contributor's check reaches the payment and stops there. They can confirm that money arrived. They cannot reach past it to the event the money was supposed to be for.
Our audit page exists because of that limit. The row is signed at the machine by somebody who is not us, and it is readable from both ends — by the licensee invoiced on it, and on behalf of the person whose hours it names. Checking runs to the row, not to our books.
And the reason it can run that far is that we dissolve nothing. A skill is chosen by name and metered by the hour it runs. That is a counting problem, not an attribution problem, and counting problems have answers a second party can check.
How the count is checkedOne row, three readings.
What a licensee is charged for
Which named way of working ran, on which machine, cleared by whom, for how long. The invoice is that row. It carries nothing the row does not carry, and it is checkable against the machine it came off and the person on the licensee's own crew who signed it.
What the hours are worth
The person in the seat never contracts with us. They sign with Even Steven, which holds their consent and licenses the corpus to Tacit Source. What is owed for their hours is measured on the row the licensee is invoiced on. The same row, not a copy of it.
What we hold
We are the commercial licensor of Even Steven skills, under licence from Even Steven. We hold the count, we invoice on it, and we stand behind it. We are not a party to the person's agreement and we do not hold it.
No rate appears anywhere on this site. A rate is a term of a licence, and the licence sets it. The row sets the hours, and the hours are the part that is signed at a machine.
Metering a machine against this?
Tell us what your machines already report, and what they would have to sign.