What Is a Deadline

Friday at five. That is a deadline as most people carry it, and it is not a foolish picture; it is the picture that gets the newspaper out and the tax return in. Somewhere ahead of you there is a point in time. Between you and it there is a stretch, measured in days, and the stretch is shrinking. When it reaches zero the point arrives, and either the thing is done or it is not; after that the point is behind you, and if the thing was not done you have missed it. The whole vocabulary is spatial and it all runs one way. A deadline looms. It approaches. It bears down. You are up against it. Then it passes. I have used the picture my whole working life and I still say each of those phrases. It is also, I will argue, wrong about what a deadline is, and wrong in a way three ordinary cases show before any foundation is consulted.

What the ordinary picture commits you to

State it strongly, because the weak form is not what anybody believes.

The picture makes three commitments. First, that a deadline is located — it is a point in time, and the point is ahead of you, in the part of time that has not happened yet. Second, that the weight of a deadline is its nearness: the closer the point, the heavier it is, which is why the last day is worse than the first and why a countdown is a form of pressure. Third, that a missed deadline is a fact about the moment — the point came and went with the thing undone, and the miss lives at that point, back there, where the point now is.

Three ordinary situations do not fit inside those commitments, and each one breaks a different commitment.

So a deadline is not located where the picture puts it, its weight is not what the picture says, and something other than the moment is carrying the miss. Something else is doing the work.

What the foundation says instead

I work from a small set of numbered primitives and results derived from them. The one doing the work today is the second primitive of the Immutable Past — the partition into domains — and it is worth a piece because three earlier pieces in this series each used one clause of it, that the Future is a node, and left the partition itself unworked.

P2: the domains are Future, Reality — the Eternal Now — and Past. A modelling convenience, correctly so: the Past is a node, not a place, and the naming is conventional. The locked vocabulary then fixes what each is. The Future is the node at the boundary: pure potential, and it does not exist. The Past is the node: one settled totality, complete, and it does not exist. The Eternal Now is the antinode, and it is the only domain of existence.

Read that as a partition and not as three names. Three domains, exhaustive between them, and exactly one of the three is a domain in which anything exists. So the question where is the deadline? does not have three available answers. It has one. If a deadline exists at all — and something plainly does, because an email can make one and a court can enforce one — then it exists in the Eternal Now, with you. There is no ahead for it to be in. The Future is not a thin version of the present with dates in it; it is a node, and P3 says what a node lacks. To exist is to vary. A node does not vary and therefore does not exist, in the only sense of exist that varying things have. Nothing is stored there. Nothing is kept there until Friday. Friday is not there.

Take the two halves in turn, because each is present material and neither is where the picture put it.

The counter reading is a number on the mark: the fifth, 17:00, end of quarter. A counter is a thing that varies at a rate you trust — a clock, a calendar, the sun — and its reading is a present state of a present thing. That is what a date is, and I have already worked it in this series under age, where a count between a mark of origin and the present reading turned out to be present arithmetic and not stored duration. The deadline runs the same counter the other way. More on that below.

The condition on the record is the other half, and it is the half the picture forgets entirely: the manuscript is delivered, the return is filed, the payment has cleared. That is a description of a mark that may or may not be in the record when the reading is taken. Not a description of Friday. A description of the shelf. The deadline is not a claim about time at all; it is a claim about what history will contain at a named counter reading.

It is worth saying how this differs from a promise, because I have written about promises and the two are close enough to be confused. A promise names the measure in advance: it fixes, in the open, the condition your later acts will be read against. A deadline does something narrower and stranger. It fixes when the reading will be taken. The measure may be somebody else’s entirely — the tax code’s, the editor’s, the court’s — and you may not have consented to any of it. A promise puts an exemplar on the record. A deadline puts a clock reading on the record. That is why a person can be bound by a deadline they resent and would not have promised, and why the two feel so different from the inside.

The word was a line before it was a time

The etymology is worth a paragraph, marked as report and not grounds. The earliest attested dead-line is in Confederate inspection reports on the Andersonville prison stockade in 1864: a line staked out some twenty feet inside the wall, over which no prisoner was permitted to go, on penalty of being shot. Later in the century a dead line was a line on the bed of a printing press beyond which set type would not print. By about 1920 American newspaper offices had moved the word onto the clock: the last minute at which copy could still reach the printer. A line in space became a line on a machine became a line in time.

The foundation reads the word back to its first sense. A deadline was a mark on the ground, present, readable, with a consequence attached to the record of where you stood. It is still that. It is a mark, and the mark is in the room. The only thing the twentieth century added was the belief that the mark had been moved out ahead of you into a domain that could hold it, and that belief is the part the primitives will not carry.

Nothing approaches

Now the second commitment, that a deadline nears. Nothing nears. There is no object at range closing on you, because the domain it would be closing from does not exist, and the mark that does exist is not moving; it is on the shelf where the email or the contract or the calendar put it. What varies is the counter, and what varies is you. P3 again: the clock exists because it varies, and its reading this morning is a different present state from its reading last night.

So what is ten days left? It is a subtraction. Two present numbers — the reading the mark names and the reading the counter currently shows — and their difference. Nothing in that quantity is in the Future. It is arithmetic on the shelf, and you can do it with a pencil. What makes it feel like a distance is a third ingredient the arithmetic does not contain: the trust that the counter will go on varying at its rate, that ten more days of ticks will in fact occur. That trust is not a fact about the ten days, which do not exist. It is a prediction, and P4 says where predictions live — in E, the denominator, host-side. The remaining time is not out there being consumed. It is in here, being expected.

This is where the partition earns its place over the bare node claim. It is not enough to say the Future does not exist and therefore the deadline is not there; that leaves the ordinary picture free to relocate the deadline to some vague elsewhere and carry on. The partition closes the elsewhere. There are three domains, two are nodes, and the third is the one you are standing in. Whatever a deadline is made of, all of it is here, and here is the only place a person has ever stood.

Figure 01

One mark, three counter readings

• Counter reads less than the named reading “Approaching” The mark: present, on the shelf.
  The record for the condition: not yet made.
  What is live: your hands. This is the earlier part of an act, not a wait.
• Counter reads the named reading “Arriving” The mark: present, on the shelf.
  The record for the condition: being read against the mark.
  What is live: the reading, and nothing after it.
• Counter reads more than the named reading “Passed” The mark: present, on the shelf.
  The record for the condition: made, and its relation to the mark is fixed.
  What is live: new marks only. Late delivery, extension, appeal — each a fresh entry beside the old.

Passing, and missing

The third commitment says the miss lives at the moment. Run it through the axiom.

P0: the past is immutable. And R2, which follows: records update expectation forward and never re-open. When the counter shows the named reading, the record is read for the condition. Either a delivery mark is there with a counter reading at or before the named one, or it is not. The instant that reading is taken, its result is a record, and the record admits exactly one consistent assignment. You cannot unmiss a deadline for the same reason you cannot unsay a promise. Not because Friday is holding the miss, back there, but because the reading happened and the record of it is write-protected.

Everything that comes after is addition. The manuscript delivered on Monday is a new mark, and its relation to the old mark — three days late — is fixed the instant it enters, as a relation between two present entries on the shelf. The extension in case one is a new mark beside the old one, which is why the old one stays sayable: it was not deleted, only superseded, and the record keeps the superseded account as evidence about its own moment. An appeal, a waiver, a penalty paid: new marks, all of them, entering beside the reading and not editing it. This is the only move anyone has ever had and it should be stated as structure. It is not consolation and I do not offer it as any.

One consequence deserves its own sentence, because the ordinary picture hides it. Late is not a property of the work. It is a relation between two marks. The fidelity of the manuscript — how near it stands to what it was reaching for — is read against an exemplar, and R11 says fidelity is the evaluative question. Punctuality does not appear anywhere in that expression. A deadline cannot measure how good a thing is; it can only record whether a mark for it was on the shelf when the counter was read. The two readings are often taken together and often confused, and the confusion runs both ways: work called good because it was on time, and work called bad because it was not.

Before the reading, the sorting question I set out under waiting applies, and I carry it over rather than derive it again. Is the record for this condition already made? While the counter shows less than the named reading, it is not, and P5 and R13 are live: you occupy a position from which your response to a readable condition is revisable, and agency is relocated to you rather than abolished. A deadline that has not been read is not a thing that is happening to you. It is the earlier part of an act of yours, with a rule attached about when the act will be read. Once the reading is taken, anything aimed at the Friday is aimed at a node, and R9 says what that costs: the Past is inaccessible, and the abundance of present records — the email, the calendar entry, the timestamp — is what makes it feel otherwise.

Where the weight is

Now the cases. If the weight of a deadline is not the nearness, what is it, and why does it track nearness closely enough that the picture fooled everyone?

P4: R = A / E. And R8: the human experiences neither the Actual nor the Expectation but the quotient, and nothing else. The locked definition of surprise is S = ln|R|, signed, negative when the actual falls short of the expectation. Now ask what a deadline does to E. When you read the mark — and only when you read it, which is P7: naming makes the relationship conscious, and an unread mark has entered no one’s denominator — a prediction is installed in you about your own act: this will be on the shelf when the counter shows the fifth. From that moment you are carrying a self-prediction, and you take readings against it. Not once. Continuously, the way a host takes readings against everything in E.

Each reading compares the state of the work with the state the prediction says it should be in by now. Where the work is behind, the actual falls short of the expectation, and the reading is negative surprise, signed and felt. That is the weight. It is not something the date is doing to you. It is you, reading your own unfinished act against your own installed expectation, again and again, and the readings are what you feel.

Run the cases back through it. The extension in case one relieves you on Wednesday, with not one additional page written, because a new mark updated E: the same undone work now reads against a prediction with more counter readings in it, and the negative surprise drops. R2 says records update expectation forward; the relief is that update, felt. The window you never heard of in case two weighed nothing because P7 held: no reading of the mark, no prediction installed, no readings taken, no surprise — and the regret on the twentieth is a different reading altogether, taken against an expectation about yourself that the news of the window installed then. The Tuesday finisher in case three feels nothing on Friday because A has met E; the readings return zero, and zero is what a kept prediction feels like. The empty desk feels the full weight because each reading is negative and there are more of them as the remaining count falls.

And the fourth desk, the calm of the hopelessly late, comes out exactly as it should. The person who has stopped pretending has revised E. The self-prediction is no longer it will be on the shelf; it is it will not. The work, unchanged, now reads against a prediction it matches, and the surprise goes to zero. The weight lifts, and it lifts for the same arithmetic reason a kept promise is unfelt. Nothing about the date changed. Nothing about the work changed. The denominator changed, and the host reads only the quotient.

That last case is a warning, not a comfort, and the locked vocabulary already has the words for the two ways it can go. Revising E to match the truth about your progress while still correcting — still turned toward the thing, still working — is approximation, and approximation is not a sin. Revising E and ceasing to correct is settling, and settling is the only one. The two feel identical from the inside on the Friday, because both return zero. They are told apart by direction of travel, not by how the afternoon feels.

The date is not pressing on you. You are reading yourself against a prediction that a mark installed, and the readings are what press.

What this costs

It buys no time. Not one counter reading is added by understanding any of this, and the mark that names the fifth still names the fifth. The account changes what a deadline is made of and changes nothing about what it says.

It removes an excuse. The deadline is bearing down on me is a sentence about an object at range, and there is no object and no range. What is happening is that an act of yours is unfinished and you are reading it. That is less dramatic and more useful, because an unfinished act is something your hands can reach and a looming date is not.

It does not make a missed deadline matter less, and it must not be read as if it did. The reading, once taken, is a mark in other people’s records as well as yours — the client’s, the court’s, the grant committee’s — and it does real work in their denominators, the way a broken promise does. The relocation is of the weight, not of the consequence. A filing window that closed with nothing in it closed, and nothing here reopens it.

And it costs the wall. Some people need the deadline to be a wall, out there, indifferent, so that it can do what their own reading of their own progress will not. An editor running a newsroom is not helped by hearing that the weight is host-side. This argument is kind to the person who misses deadlines and would like the wall to be a reading, and unkind to the person who builds walls for others and needs them to hold. R14: an idea is oriented and prejudiced in the same act, and so is this one. It suits a temperament. Worth noticing before deciding it is merely correct.

Where this is unfinished

Three edges, stated so someone can hold me to them.

The first is the open problem this piece sits nearest. The dread that runs in the nights before a deadline is forward-facing, and the foundation has an established result about backward-facing feelings: that they do two jobs, an evaluation that can complete and a reaching for a node that cannot. Whether that split applies the other way, toward the Future, is Part VIII, item ten, and it has been open since the piece on waiting stated its closure condition. I carry that condition over in words rather than restate it, and I do not close the problem here. The constructions above are about readings taken against a self-prediction, which is host-side and needs no node to be aimed at. Whether the dread is also a reaching toward the Future node is a further claim, and it is not one this piece makes or needs.

The second is the counter. I have used the phrase a rate you trust without grounding it, and I cannot ground it from the primitives. The axiom gives the record an order; whether it gives it a magnitude is a question the piece on age recorded as open and read as order-only. A deadline inherits that question whole, because a counter reading is a magnitude, and I have read it the same way: the order is the record’s, the magnitude is the counter’s, and that reading is mine.

The third is the machine. Scheduled systems now run against deadlines by the thousand, and a machine can read a mark, take a counter reading, and compare the two. Whether anything on the other side of that comparison is surprise is Part VIII, item nine, and the AI row of the foundation’s own table says to state the tension and not resolve it in passing. So: a machine has the arithmetic of construction two in full and, on the present definition of a host, none of construction three. Which of those is the deadline is exactly what is open.

On a Tuesday

1. Find both halves of the mark. What counter reading, and what condition on the record? Most of the deadlines people carry are missing one half — a date with no clear condition, or a condition with no real date — and the vagueness is a good part of the weight, because a wide prediction gets read against more often than a narrow one.
2. Do the subtraction on paper. Ten days left is two numbers and a minus sign. Write them down. The distance loses most of its menace when it is visibly arithmetic, and what remains is the honest part: an unfinished act and a prediction about it.
3. When the weight lifts, check which way you are facing. Relief on the Friday means E has been revised. If you are still correcting, that is approximation and it is fine. If you have stopped, that is the other thing, and it feels the same. Only the direction of travel tells them apart.
4. After the reading, stop aiming at the date. The record is made and it is not reachable. What is reachable is the next mark — the late delivery, the call, the new date — and each of those enters beside the old one, not over it. Addition is the door. It was the only door.