What Is Blame

The Immutable Past · What Is

What Is Blame

“Who is to blame?” sounds like one question. Derived from the foundation’s result that ownership is a category error and the manifestation is accountable, it turns out to be two — whose was it, and who made the mark — and only the second has an answer. So “it was the idea” is true, and excuses nothing.

  • AuthorJohn Rector
  • Published
  • FormEssay · 15 min
  • Result doing the workR12 · the manifestation is accountable
  • RegisterDoctrine · three marked constructions
  • FoundationSpine v1.41

The assumption folded inside the question

whose ≠ who

Whose idea it was has no answer. Who made the mark has one.

The ordinary picture finds blame by tracing a fault back to where it started and stopping at the first person standing there. The foundation this series works from has no first person to find — and keeps, without losing anything, the person who made the mark. This piece follows what that does to the first question asked in any room after something has gone wrong.

Contents
  1. Blame, stated fairly
  2. The neighbours
  3. Three cases the picture cannot hold
  4. Two questions in one
  5. The first question has no answer
  6. The second question has one
  7. “It was the idea”
  8. Blame does not divide
  9. What it does not mean
  10. What it costs
  11. An ordinary Tuesday

Something has gone wrong. The deploy took the site down on a Friday night. The dinner ended in a row. The shortcut through the flooded road wrote off the car. And the room asks the question rooms ask: who is to blame?

The ordinary answer works by tracing. Follow the fault back along the chain of events until you reach the place where it started, and whoever is standing there is to blame. People further down the chain are less to blame, or not at all, roughly in proportion to how far from the start they stood. That is why the first thing people say in their own defence is about the start: it wasn’t my idea; I was told to; he suggested it. And it is why the oldest excuse in the language points further upstream still: the idea made me do it; the devil made me do it; something came over me.

The picture is not foolish. Tracing is how a great deal of good work gets done — how an engineer finds the line of code, how a doctor finds a cause, how a court establishes what happened. The question here is not whether tracing is useful. It is what blame finds when it reaches the top of the chain, and whether anybody is standing there.

The neighbours

Several earlier pieces have already worked one half of the result this piece rests on. The pieces on loyalty, on a copy and on a discovery each read its first clause — that owning an idea is a category error — at a bond, at originality, and at a name on a finding. This piece carries that clause from them in words rather than running it again. Its subject is the second clause, which no piece in the series has made a subject: the manifestation is accountable.

The piece on temptation said in passing that a person is not the origin of a pull and is still the place where a response to it is made. That piece was about the moment before a mark. This one is about the moment after, when the mark is made and somebody asks whose fault it was. The piece on a reputation took a second layer of self-blame off the loss of a good name; self-blame in general has its own row in the foundation and gets the care it needs near the end of this piece, not a construction.

And the piece on set in stone, published yesterday, took apart a different excuse: I can’t change it, it’s set in stone. That excuse points at the material — at a thing being kept — and says the keeping is out of anyone’s hands. The excuse in this piece points upstream, at where a thing came from. One says the thing is too hard to move; the other says the thing was never mine. They are answered by different machinery, and nothing here depends on that piece.

Three cases the picture cannot hold

Case one · the suggestion

On a Friday afternoon a senior engineer says to a junior one: just push it, nobody will notice before Monday. The junior pushes it. The site is down for the weekend. In the review the junior says it was not my idea, and that is true. The senior says I never touched the deploy, and that is true too. The tracing picture has to decide which of these is the start of the chain, and then it has a problem. If the suggestion is the start, the junior is nearly blameless, and nobody in the room believes that. If the deploy is the start, the senior said nothing that mattered, and nobody believes that either. The room ends up splitting it — sixty-forty, seventy-thirty — and both people leave feeling the number is wrong.

Case two · the same mistake twice

Two developers at two companies, who have never met, write the same bug in the same week: the same off-by-one, in the same kind of loop, for the same plausible reason. Each is called to account at their own company. Ask the tracing question: whose idea was the bug? Neither copied it. Neither started it. If blame lives at the origin there is nowhere to put it — and yet each of them is plainly answerable for the code they shipped.

Case three · blaming the idea

Greed caused the crash. Ambition ruined him. Fear made them do it. People say this sort of thing about whole episodes, and the sentence has a curious effect: it closes the inquiry. The defendant it names cannot be called, questioned, or asked to make anything right. An essay on this site from 2024 made the same move about a relationship. Don’t blame love, it said; the trouble lies in the idea. The tracing picture reaches the top of the chain, finds an idea standing there, and hands the blame to it.

The seam is the same in all three. The picture assumes blame is found by tracing to an origin. In the first case there are two candidate origins and neither will hold the whole of it. In the second there is no origin at all and the blame is still plainly due. In the third the origin found is something that cannot answer. The first two cases are composites, not reported events. The third quotes ordinary speech and this site’s own 2024 essay, which is linked at the foot of the page.

Figure 01

The two questions inside “who is to blame?”, read against the Friday deploy

QuestionWhat it asks afterWhat the foundation gives itThe Friday deploy
Whose was it?An origin: who started it, whose idea it was.No answer. Owning an idea is a category error.Neither the senior nor the junior — nor anybody else.
Who made the mark?The marks: what was said, written, pushed, done.An answer for each mark: its maker.The senior, for the sentence. The junior, for the deploy.
The split is the author’s. The first row rests on the first clause of R12, with P8 beneath it; the second row on its second clause, read as the mark, with R13 for the maker. The ordinary question asks both at once, and the arguments about blame happen where the two answers come apart.

Two questions in one

I work from a small set of numbered primitives and the results derived from them. The one doing the work today is a result rather than a primitive: ownership is a category error; the manifestation is accountable (R12). It is derived from the primitive of priority. A condition is prior to what it conditions, and where a person’s naming of a condition is itself conditioned by it, that person is not its origin. Ideas have people; people do not have ideas (P8). An idea, in the foundation’s vocabulary, is a named condition (P7).

The result has two clauses, and the ordinary question has two questions welded inside it. Who is to blame? asks, at once, whose was it? and who did it? In daily life the two usually get the same answer, which is why the weld goes unnoticed: the person who thought of it is usually the person who did it. The three cases are the ones where the answers come apart — and that is exactly where the arguments about blame take place.

The first question has no answer

Take the first question by itself. Whose idea was it? The tracing picture assumes somebody stands at the top of the chain who had the idea first, and that the idea was in some sense theirs. The foundation says no such person stands there, and not because they are hard to find. A condition is prior to what it conditions, and a person’s naming of it does not make them its origin (P8). The question asks after an owner, and owning an idea is not a hard thing to establish; it is a category error (R12). The piece on a discovery followed that to its end for credit: a name on a discovery records a naming and a mark, not an origin. The same holds for blame, word for word, in the other direction.

So the first question does not have a hidden answer waiting for a better investigation. It has none. That is why the second case cannot be solved by tracing: two developers wrote one bug, nobody originated it, and a blame that lives at the origin has nowhere to land. It is also why the first case cannot be settled by arguing about whose idea it was. The senior did not originate push it on Friday any more than the junior did. The idea that a deadline can be met by not looking has had a great many people.

The question “whose idea was it?” does not have a hidden answer waiting for a better investigation. It has none — for the accused, and for the accuser too.

The second question has one

Now the second clause: the manifestation is accountable. The result does not spell out which thing the manifestation is, and I should say how I am reading it. I read it as the mark — what was actually made: the artifact, in the foundation’s locked sense, an imperfect historical mark made in relation to an exemplar. Earlier pieces in the series read the clause the same way. The reading is mine, and it is listed as held open at the end of the piece.

On that reading, accountability sits on marks, and marks have makers. The foundation is plain about where the maker stands. The host can occupy a position from which its response to a readable condition is revisable (P5), and agency is relocated, not abolished: the human is the site of conscious responsibility (R13). The record does not let a mark be moved either. Records update expectation forward and do not reopen (R2). The pushed deploy is in the record, and so is the sentence on Friday afternoon. Neither can be reassigned by an argument about where the idea came from.

The foundation also separates acts from artifacts. An act is a process, an artifact is a mark, and some acts leave no mark. That matters here. A thought that passed through somebody’s head and was never said, written or acted on is an act that left no artifact, and the second question has nothing to read. The first question would have blamed the person for having the thought. The second can find only what they made.

Marked construction 01 — consequence, not doctrine

“Who is to blame?” is two questions welded together: whose was it, and who made the mark. The first asks after an owner and has no answer — not a hidden one; owning an idea is a category error. The second has an answer for each mark: its maker, who answers for it. Blame, where it is paid at all, is paid in the second question.

Grounds. R12 at both clauses — the first for the origin question having no answer, the second, read as the mark, for the mark question having one; P8, from which R12 is derived; P7 for an idea as a named condition; P5 and R13 for the maker as the site of responsibility; R2 for the mark staying where it was made; and the foundation’s distinction between acts and artifacts. Reading “the manifestation” as the mark is the author’s. The construction says nothing about how much any mark should cost its maker.

“It was the idea”

Now the excuse, in its three common forms. It wasn’t my idea. It was the idea. The idea made me do it.

On the first two, the foundation is on the speaker’s side, and that should be said first rather than conceded later. It was not your idea. It was not anybody’s idea. The person who says it wasn’t my idea is saying something true — truer than they mean, because they usually mean it was somebody else’s.

The third needs its grammar corrected before anything else. The idea made me do it puts the idea where an agent goes, as the subject of a verb of making. The foundation does not allow that. A condition conditions — a relation that is neither causation nor agency — and it does not intend: no wanting, no strategy, no preference (P9). The idea did not make anybody do anything. It conditioned, and somebody did. The verb belongs to the person.

And then the excuse fails, because of where it points. It is an answer to the first question — whose was it — offered in place of an answer to the second. But the first question has no answer for anyone: not for the person offering the excuse, and not for the person it is offered to. Disowning the idea moves no mark. The deploy still has a maker.

Marked construction 02 — consequence, not doctrine

“It was the idea” is true and excuses nothing. It answers the question that has no answer, and blame is paid in the other one. Nor can the blame be handed to the idea instead: a condition conditions and does not intend, it made no mark, and so there is nothing in it to call to account.

Grounds. Construction 01; P8 and R12 for the truth of the excuse; P9 for conditioning being neither causation nor agency, and for a condition not intending; R12’s second clause, read as the mark, for where blame is paid. The construction does not call the idea innocent or guilty. Neither word applies to a condition.

There is an obvious objection, and it is the strongest one against this whole series. Ideas have people sounds like the oldest excuse there is. An essay on this site from 2025, on inspiration from beyond the self, recounts how an earlier age treated a work’s genius as something outside the artist, which took the credit if the work was brilliant and could be blamed if it failed — sparing the artist’s own psyche either way. Is the foundation the genius back again, under a new name?

No, and the difference is exact. The old genius could take the blame because it was pictured as an agent and a possessor: it did the work, and the work was its. The foundation denies both to an idea. A condition does not act (P9), and ownership is a category error in either direction — for the person and for the idea alike (R12). So the genius cannot take the blame for the same reason the person cannot shed it by disowning the idea: the blame was never at the origin. It is at the mark, and the mark has a person’s hands on it.

The 2024 essay mentioned above made a version of the genius move about love. It said the trouble in a relationship is not love’s fault but lies in the idea, and spoke of an idea beginning to cause discord. Read against the foundation, that essay moves the blame from one thing that cannot answer to another, and gives the idea a verb of causing that the foundation withholds. It stays up as the record of an earlier position, with a note at the foot of this page saying so.

Blame does not divide

Go back to the Friday deploy and the sixty-forty split. Why does it feel wrong to both people?

Because a split presupposes the tracing picture. A percentage of blame is a share of one quantity, and the one quantity was the fault at the origin, to be divided among whoever stood near it. If no origin can be owned, there is no single quantity to divide. What there is instead is two marks: a sentence on Friday afternoon and a deploy on Friday evening. Each was made by one person. Each is read on its own.

So the senior answers for the sentence — what was said, to whom, in relation to what — in full. The junior answers for the deploy, in full. Neither answer is a fraction of the other, and neither is reduced by the other’s being there. That is what both people felt when they were offered a percentage. The junior was not seventy per cent of a deploy. The senior was not thirty per cent of a sentence.

Marked construction 03 — consequence, not doctrine

Blame does not divide, because it was not one quantity at an origin to begin with. Each mark is answered for in full by its maker, and another person’s mark does not reduce it. “If it’s partly his fault, it’s less mine” does not follow.

Grounds. Construction 01 for blame being paid at the mark; R12 for there being no owned origin whose fault could be divided; R2 for each mark standing in the record as made. The construction does not say what any mark should cost, how two marks compare, or what anyone deserves. Who pays a bill is a different question — a fixed sum can be split, and courts split such sums in many places — and nothing here says how. Nothing here is legal advice.

This is not a balance, and it should not be read as one. Nothing here says the marks add up to anything, are set against each other, or are made up for anywhere. The ledger is not invoked.

What it does not mean

Four misreadings sit close enough to the argument that they should be stated and refused.

Nobody is to blame. The opposite. The first question loses its answer and the second keeps its answer, for everybody. If anything, more people answer than under the tracing picture, because no mark is discounted for standing far from the start.

Ideas are harmless. The piece says nothing about which conditions are worth being had by. That question is about fidelity, not blame, and earlier pieces have taken it up.

The one who suggested it gets off. No. A suggestion is a mark — said, in a room, to a person — and it is read like any other. What the suggester loses is only the claim to have originated the idea, which nobody could have had.

Blame is a debt. Blame here is a question about marks, not a quantity owed. Nothing in the piece says what anyone deserves, what a punishment should be, or that anything is made good anywhere.

What it costs

The excuse loses its oldest form. It wasn’t my idea stays true and stops working. That is unwelcome to everybody who has leaned on it, which is most people.

The accusation loses its oldest form too. You started this is a claim about an origin, and it fails exactly as the excuse does. Nobody started it. What can be said is: you said this, you wrote that, you did this other thing. The accuser has to point at marks, which is harder work and far easier to check.

The comfort of a share goes. A percentage felt like relief: if it is seventy per cent his, it is only thirty per cent mine. That relief was borrowed from the origin, and it goes with it.

The reading takes nothing from one side of a dispute that it does not take from the other. An accuser keeps every mark they can point to and loses the claim that the other person is the source of the trouble. An accused keeps the protection of every mark they did not make — on this reading a mark is answered for by the person who made it, not by whoever stood nearby — and loses the excuse of where the idea came from. Who made which mark is a matter of fact, and this piece settles none.

If the blame is your own

Self-blame tends to run on the first question. Not what did I make? but what kind of person has an idea like that? — as if a thought were a stain on whoever had it. That second layer can come off. The idea was not yours to have; ideas have people (P8). What you answer for is what you made, and you answer for it the way anyone answers for a mark: by reading it plainly, and by making the next one. The record does not reopen (R2), so amends are new marks beside the old one, not edits to it — and your response from here is revisable (P5).

Understanding the mechanism does not stop it, and there is no schedule for when it should. Taking the second layer off is not a reason to take what you did less seriously. And if blaming yourself has become something that loops and will not finish, a better argument is not the next step. A person you trust, or a professional, is.

An ordinary Tuesday

  1. When something goes wrong, ask what was made, not where it started. The sentence, the commit, the email, the decision as written. Point at marks; they are the only things the question can find.
  2. Answer for yours in full. Not “my part in it” — my mark. It is a smaller thing to answer for, and you can answer for all of it.
  3. Do not take a percentage, and do not hand one out. Each mark is read on its own. Another person’s mark does not make yours lighter.
  4. Say “it wasn’t my idea” if it is true — and then say what you did. The first half is true of everyone. The second half is the one anybody can use.
  5. Do not blame the idea. “Greed caused it” ends the inquiry. Name the marks instead, and the inquiry can go on.
  6. When the blame is your own, drop the question about what kind of person has thoughts like that. Read the mark. Make the next one.

Blame asks whose it was and who made it. The first question has no answer, for anyone. The second has an answer for each mark, and the maker answers for it in full. “It was the idea” is true. It is just not what blame was asking.

Held open

What “the manifestation” names.
The result’s second clause does not say whether the manifestation is the mark or the person in whom the condition becomes manifest. This piece reads it as the mark and lets the result on relocated agency carry the person, as earlier pieces did. On the other reading the argument still holds for the person who made a mark, but it would say something different about an act that left none. Settling it is an amendment to the wording of a numbered result, not something a piece can do. Named, not closed.
How much a mark should cost its maker.
The foundation gives fidelity as the question to ask of an artifact. It gives no scale of blame, derives no desert, and says nothing about punishment. This piece inherits that gap and does not fill it. Named, not filled.

Sources and what was left out

  • The genius that took the blame (reported). “Ideas Have People”: Inspiration Striking from Beyond the Self, this site, 18 October 2025, for the account of an earlier age treating genius as outside the artist and blaming it when a work failed. Reported as recounted there, with that essay’s own sources; not used as grounds.
  • Superseded in the open. Don’t Blame Love (15 August 2024) predates the foundation this series is written against. Three of its moves are retired: moving blame from love onto an idea, where the foundation places it at the mark; ideas as the subject of verbs of causing and creating (“begins to cause discord”, “starts to create tension”), where conditioning is neither causation nor agency; and the node described as seeking and dedicated without being marked as frame-language. The essay stays up as the record of a position, with this note attached.
  • The cases. The Friday deploy and the twin bug are composites, not reported events.
  • Deliberately left out. Forgiveness has its own piece. Self-blame has its own row in the foundation and gets care here, not a construction. How courts apportion fault or damages is not addressed. Nothing here says what anyone deserves, and nothing says a fault is made up for anywhere. The ledger is not invoked.

Read next

Citation stamp

Foundation
The Spine v1.41 · 30 September 2026
Primitives
P5, P7, P8, P9
Results
R2, R12, R13
Registers
DOCTRINE for the primitives and results above, with the ownership result read at its second clause — the manifestation is accountable — and that clause read as the mark. CONSEQUENCE for the three marked constructions. REPORTED for the account of genius, as recounted in this site’s 2025 essay. The deploy and the twin bug are composites and are marked as such.
Open questions touched, left open
What “the manifestation” names — named, not closed. How much a mark should cost its maker — named, not filled.
Ledger
Not invoked. Nothing here says a fault is made up for anywhere, or what anyone deserves.

Author: John Rector

John Rector is a Charleston-based entrepreneur, author, and AI strategist. He co-founded E2open, the supply-chain software company acquired for $2.1 billion in 2025, and in 2026 opened Charleston AI, a 3,000-square-foot lab that helps people and organizations understand and use artificial intelligence. He is the creator of The Reality Equation — a lecture series, book, and curriculum exploring attention, prediction, and how reality is experienced — and the author of more than two dozen books. He writes and speaks widely on artificial intelligence, attention, and the future of human work.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Discover more from John Rector

Subscribe now to keep reading and get access to the full archive.

Continue reading