The Immutable Past · What Is
What Is a Technicality
A technicality is ordinarily described as a requirement that decides an outcome while having nothing to do with it. Derived from the foundation’s definition of a condition, the word turns out to name the one place people see conditioning bare — and the word they use for what they see there is only.
The count ordinary speech gets wrong
1
Kind of conditioning the definition allows. Ordinary speech runs two: the requirement that matters, and the one that is only technical.
The foundation defines a condition once, as a prerequisite in order for something to happen or exist, and says what its relation to the outcome is in a single clause: neither causation nor agency nor inertness. There is no second definition for requirements that feel procedural, and no clause that grades a prerequisite by how much of an outcome rests on it. What the word technicality adds sits on the side of the person using it.
Contents
- The technicality, stated fairly
- Two neighbours, separated first
- Three cases the word cannot hold
- What the word is the name of
- The third clause is not a hedge
- Why this one looks idle
- What he got off from
- What it costs
- An ordinary Tuesday
Everyone knows what a technicality is, and the word earns its keep. It names a requirement that is on the books, that somebody failed to meet or managed to exploit, and that has — on the ordinary account — nothing to do with what the matter was about. He got off on a technicality. It’s only a technicality. A technical breach. Technically late. In each phrase the speaker does the same thing with the word: concedes that a requirement decided the outcome, and denies, in the same breath, that the requirement had anything to do with it.
Underneath is a picture of requirements in two kinds. Some bear on the substance: the evidence has to show that he did it, the will has to say what she wanted, the traveller has to be the person on the passport. Others are form: the warrant, the second witness, the date printed inside the back cover. The first kind does work. The second kind merely stands there, and when it decides something the result feels like an accident — an outcome that turned on nothing. The picture is not stupid. It is how most people protest a result they think was wrong, and the protest is often right about something.
So it is worth asking what the word is the name of. Not whether technicalities are fair, and not whether the rules behind them should be rewritten. What a technicality is.
Two neighbours, separated first
Two earlier pieces in this series sit close enough that the difference should be stated before anything else. The piece on opportunity took a prerequisite and denied it the power to enable: an opening does not make anything possible; it is a condition, and conditions do not grant. A reader who accepts that — and who also accepts the older point that a condition does not cause — is left with an obvious conclusion. If it does not cause and it does not enable, it does nothing. This piece is about that conclusion. It does not re-run the enabling argument. It takes the reader who has been persuaded by it and denies them the next step.
The piece on chores covers the formality, the box-ticking exercise, the task done for form’s sake. That is an act — somebody going through motions. A technicality is not an act anybody performs. It is the standing of a prerequisite: the thing an outcome rests on, noticed at the moment it is missing or contested. The two meet at the phrase a mere formality, and they part there.
Three cases the word cannot hold
Put ordinary cases against the picture — not exotic ones, just the three situations in which the word is most often said.
Case one · the search
Police find the evidence in a search that turns out to have lacked a valid warrant. The evidence is excluded, the case cannot proceed, and the defendant walks out. He got off on a technicality. Hold the sentence still and ask what it asserts: that the outcome turned on the warrant, and that the warrant had nothing to do with anything. Both cannot be meant at once. Put the case beside its twin, in which the warrant was in order, and the one difference between a conviction and a release is the thing the sentence calls idle.
Case two · the will
A woman writes her will, signs it, and has one neighbour witness it. English law has asked for two witnesses, present together, since 1837. Nobody disputes what she wanted; nobody disputes the handwriting. The will fails, and the estate passes under the rules for people who left none. The relatives who inherit under those rules say the law is the law. The friends named in the will say it was a technicality. Same requirement, same page, same missing signature — and it is substance to one side of the room and form to the other. Whatever the word is tracking, it is not a property of the requirement.
Case three · the gate
You are at the gate with a passport that expired yesterday. You are exactly who the passport says you are. The photograph is you, the name is yours, and nothing about your identity is in question. It’s only a technicality, you say — and you say it from the wrong side of a closed aircraft door. The sentence and the situation disagree, and the situation is the one that is correct about where you are standing.
The seam is the same in all three. The word only is applied to the single thing the outcome was resting on. The ordinary picture needs a class of prerequisites that can decide an outcome while doing nothing at all, and the three cases are that class, examined, refusing to stay empty.
What the word is the name of
The foundation defines a condition as a prerequisite in order for something to happen or exist, and denies it three things at once: it does not cause, it does not make possible, and it does not happen (P6). What a condition does instead is stated in one sentence. A condition conditions — a real relation, neither causation nor agency nor inertness (P9).
Test the word against that. Strip a technicality to what all parties would sign. The second witness was a prerequisite for a valid will. The warrant was a prerequisite for admissible evidence. A current passport was a prerequisite for boarding. Each is true, and each exhausts what the word reports before only is added. A technicality is the name of a prerequisite. Named, it is an idea (P7), and it sits on the circumference with the rest of the conditions (S1). There is no second circumference for requirements that feel procedural.
The first two negative clauses in that sentence have been worked in this series already. The warrant did not cause the release; nobody believes it did. It did not act; nobody imagines it had a view about the defendant. Conceded. What people do next is the move this piece is written to stop. Having agreed that the requirement neither pushed nor chose, they conclude that the requirement did nothing — and they have a word ready for a requirement that did nothing. The word is technicality, and the adverb that goes with it is only.
The third clause is not a hedge
Read quickly, nor inertness looks like padding: a clause added so the other two do not sound too strong. It is doing more than that. It closes the one exit the other two leave open, and in closing it, it is the only clause in the sentence that says what the relation is like rather than what it is not.
Look at what inertness would require. A prerequisite is defined by what rests on it — in order for something to happen or exist. An inert prerequisite would be one on which nothing rests. That is not a weak prerequisite; it is no prerequisite. It could not decide an outcome, because deciding is exactly what resting-on looks like from outside. So a requirement that decided an outcome was, by that fact, not inert. And a requirement that was inert decided nothing, and would not be called a technicality by anyone, because people do not name the requirements that made no difference to them.
Marked construction 01 — consequence, not doctrine
“Only a technicality” cannot be said truly of anything that decided an outcome. If the outcome rested on it, it was not idle; if it was idle, it decided nothing.
Grounds. P6 defines a condition by what rests on it, and P9 denies the relation inertness in the same clause that denies it causation and agency. The construction is the elementary step between them: a thing that decided an outcome is, by that fact, something the outcome rested on. It follows from the two elements named and is not a numbered result, so it is marked rather than cited. It says nothing about whether the requirement ought to be there. A rule can be a bad rule and still be the prerequisite an outcome rested on.
That last sentence matters, because it is where most arguments about technicalities actually live, and nothing here settles them. Whether the exclusionary rule is wise, whether the formalities for wills are too strict, whether an airline should board a passenger whose passport ran out a day ago — those are arguments about which requirements a community should write down. This piece is about what a requirement is once it has been written, and on that question the answer is flat. It is not nothing.
Why this one looks idle
If a technicality is conditioning like any other, something still needs explaining. Why does this prerequisite feel idle when the others do not? Almost nobody calls the requirement that the evidence show he did it a technicality.
Look at what comes attached to each. The requirement that the evidence show guilt comes wrapped in a causal story. He did something; the doing left marks; the marks were gathered; the gathered marks persuaded a jury. Each step of that story is a thing happening, and the requirement is seen only through it. The warrant requirement has no story of that kind around it. Nobody acted through it. It pushed nothing. It sits in the proceedings as a prerequisite and only as a prerequisite, and when it decides the outcome there is no chain of happenings to see it through.
Marked construction 02 — consequence, resting on a silence
A technicality is not a second kind of condition. It is conditioning seen without a causal story laid alongside it — the one place ordinary life shows the relation bare, and the place where people call the relation nothing.
Grounds. P6 defines one relation and S1 puts every condition on one circumference, so the primitives supply no second class for procedural requirements. P9 gives the relation its character without giving it a strength: the foundation does not grade conditioning by how much of an outcome rests on it. The construction depends on that silence, and a silence is not a denial — the held-open note at the end states what would overturn it. If it holds, the ranking of requirements into substance and form has nowhere to sit on the condition’s side, and is carried by the reader.
The second case shows where it is carried. The same missing signature was substance to one side of the room and form to the other, and the only thing that differed was which outcome each side was facing. The foundation has a result for exactly that: every idea is biased toward itself, orientation and prejudice together (R14). A person facing the outcome a requirement blocks reads that requirement from the opposite orientation, and from there it looks like paperwork. A person facing the outcome it protects reads the same requirement as the whole point. Neither is lying. Both are reading from where they stand, and the requirement is where it was.
The warrant did not cause the release, and did not choose it. It was also the one difference between the release and a conviction. Those are three facts, and the word keeps two of them.
What he got off from
The phrase that carries most of the heat is got off, and it deserves a straight reading, because it contains a grievance the derivation does not dissolve.
Got off from what? Not from what he did. What happened is settled: the records admit exactly one consistent assignment, and no present operation can produce a different one (P0). A dismissal is a present operation. It is a mark, made in a courtroom on a date, and it is added to the record beside the other marks about the case. Records update expectation forward and never re-open (R2), so the dismissal does not reach back and alter the act, and nothing that happened is less settled because a court declined to say so.
What he got off from is a different mark — the conviction that would have been made had its prerequisites obtained. That is the whole of what the technicality decided: whether one particular artifact would be made. It had no purchase on the act, and the conviction would have had none either. A verdict is a mark about what could be established under the conditions for making it. It is not the act, and it is not a window onto the act.
So the grievance survives, relocated. The complaint cannot be that the outcome turned on nothing; it turned on a prerequisite that failed. The complaint that stands is that the record now carries a mark that misses what happened by more than anyone can bear. That is a fair complaint and the derivation takes nothing off it. It also puts nothing on it. The mark is made. Answering it means making another mark — an appeal, a civil action, a published account — and each of those has prerequisites of its own.
What it costs
Three costs, and they land on different people.
The defence goes. If you are the one at the gate, or the one who filed a day late, or the one whose form went in without a signature, it’s only a technicality is not available to you. The outcome rested on it. That is unwelcome precisely because the sentence is usually said in good faith, by somebody who knows they are who they say they are, and it is still wrong about the one thing it asserts.
The contempt goes. Got off on a technicality keeps its anger and loses its sneer. The requirement did what a prerequisite does. What remains to be angry about is a mismatch between a mark and the settled past, and that is a harder thing to be angry about, because there is no one — least of all the requirement — to be angry at for it.
The sorting goes. The habit of dividing rules into ones that matter and ones that are paperwork cannot be kept. What can be kept is a different division: the requirements you have read, and the ones you have not. That division is on your side of the account rather than the requirement’s, and it is the only one of the two anybody can act on.
And one refusal, stated once and kept. Nothing here says that a man who got off will be caught up with somewhere, that it comes round, or that it evens out for the person he harmed. No such promise is available on this side, and it would be dishonest to borrow one for the length of a paragraph.
If a case you cared about ended on one
If you are reading this because the person who hurt you, or somebody you love, walked out of a courtroom on a procedural ruling, nothing above is addressed to you as a correction. The argument does not say the procedure mattered more than what was done to you. It says the verdict rested on the procedure, which is a claim about how one particular mark gets made, and it leaves what happened exactly as settled and exactly as serious as it was.
It can take one thing off, and only one. The sense that the outcome turned on nothing — that something trivial beat something that mattered — is not an accurate reading, and there is some relief in not having to believe your case lost to a triviality. It will not do more than that. It restores nothing, and there is no schedule on which anybody is supposed to be finished being angry about it. Victim advocates, counsellors, and people who have been through the same thing are the help here. A metaphysics is not, and it must not be offered as though it were.
An ordinary Tuesday
- Strike the word only. Before you call something a technicality, ask what the outcome was resting on. If it was resting on this, drop the adverb. The sentence that remains — the outcome turned on a requirement I think is badly drawn — is an argument you can actually have.
- Sort requirements by whether you have read them. Substance and form is a ranking you cannot act on. Read and unread is one you can. What is revisable is the response to a readable condition (P5) — not the condition itself. The expiry date is printed inside the back cover; that is most of the advice.
- Keep the mark and the act apart. A conviction is not what happened, and neither is a dismissal. Both are marks made under conditions. If you want to know what happened, read the marks about the act, not the marks about the proceedings.
- Notice which side you are on. When a requirement looks like paperwork to you, check which outcome you are facing. The same requirement will look like the whole point to someone facing the other one, and you are both reading it from where you stand (R14).
- Answer for what you made. If the signature was yours to get, the missing signature is yours to answer for. The human is the site of conscious responsibility (R13) — heavier than the requirement being trivial, and considerably more useful.
A technicality is a prerequisite seen with nothing attached to it. It is the clearest view of a condition that ordinary life offers — and the word we use for what we see there is only.
Held open
- Does conditioning admit a degree?
- Marked construction 02 rests on the foundation’s silence about the strength of the relation: P9 characterises conditioning and does not grade it. A silence is not a denial. What would close it: either a derivation from P6 that a prerequisite is all-or-nothing by the grammar of in order for — the outcome rests on it or it does not — or one worked case in which a prerequisite bears more of an outcome than another in a sense that does not reduce to two separate outcomes. The obvious candidate for the second is a pair of alternatives either of which would do, a passport or a national identity card; whether that is one disjunctive prerequisite or two partial ones is exactly the question. If the second route succeeds, construction 02 weakens to a claim about kind and the substance-and-form ranking gets a foothold on the condition’s side. Construction 01 does not depend on the answer. Held open.
- Why a requirement is legible to one host and not another.
- The foundation records this as unresolved. The Tuesday list uses readability as a fact about a person and does not explain it. Not approached.