|
A Theory of Embedded Intelligence Essay
The Capture Force Nobody Warns You About, Explained by Someone It Caught
|
I built a framework that names five forces capable of closing a working mind. Then the fifth one closed mine, inside the document where I had named it, and it took me eleven days to notice. This essay is written for people about sixteen years old, because you are going to meet this force more often than I did and nobody is going to warn you about it.
|
Editor’s Note
This is the tenth of the essays proposed in the Foundation’s lifelong-learning plan, Open at Both Ends. Unlike the rest of the series it is addressed directly to a reader of about sixteen, and it is meant to be usable as a teaching text rather than read about one. It is shorter than the other essays on purpose, and it assumes no prior knowledge of the Theory of Embedded Intelligence. |
I. Two Words That Sounded Right
A while ago I adopted two terms into the permanent record of the framework I have spent twenty years building. The terms were Borrowed Cycle and Repayment Criterion.
They were not mine. Claude — the AI system I work with — produced them while drafting an essay. I read them, I liked the way they sounded, and I let them into a canonical document. Claude then drafted the document that formally adopted them. So the thing that generated the words also wrote the paper approving the words, and I signed off on both.
They were wrong. Not slightly off. Wrong about the mechanism they were naming.
Eleven days later I was rereading my own document and caught it. We corrected it in a later instrument, and both the error and the correction are on the record permanently, on purpose. They are still there. Anyone can go look.
I am telling you this first because everything else in this essay depends on you believing that I am not writing from above the problem. I am writing from inside it.
II. Why They Were Wrong
Here is the actual mistake, because the shape of it is the lesson.
The mechanism I was naming is this: sometimes one system runs a cycle on behalf of another system, and later hands it back. A parent thinks something through for a child who cannot yet think it through alone. A teacher holds a question open for a class that would otherwise close on it too fast.
Borrowing is a specific thing. Borrowing implies a lender. It implies a term — a date by which the thing comes back. And it implies a debt: something owed, with the shadow of a penalty if it is not paid.
None of that is true here. Nothing is lent. Nothing is owed. There is no date and no penalty. One system carries something for another and then releases it. That is a completely different relationship, and the word borrowed imported three ideas that were not part of it.
The corrected terms are Carried Cycle and Release Criterion. Less satisfying to say. Accurate.
Read those two pairs out loud. Borrowed Cycle, Repayment Criterion. Carried Cycle, Release Criterion. The first pair sounds better. It has a rhythm. It sounds like a thing an expert would say. That is exactly what was wrong with it.
III. Eleven Days
I want to be precise about what failed and what caught it, because people usually get this part backwards.
What failed: I accepted a piece of vocabulary because it arrived well-formed. Not because I checked it. Not because I tested it against the mechanism. Because it sounded like the right answer.
What caught it: not a review board. Not a committee. Not a process. Me, rereading my own document, on day eleven, at the point where the words had stopped being new enough to sound impressive. Once the shine wore off, the mistake was obvious. It had been obvious the whole time. I just could not see past the sound of it.
Eleven days is fast, by the way. I am not telling you this as a story about being slow. I had written the framework. I had named this exact force. I knew it existed. I had described how it worked. And it still took eleven days, inside a document I wrote, about a failure mode I invented the vocabulary for.
If knowing about it were enough, eleven days would have been eleven minutes.
— The Mensch Foundation
IV. The Force Has a Name
The framework I work in describes five forces that can close down a working mind — take a question that should stay open and shut it. Four of them you have heard about your whole life, under various names.
Belief — a conclusion fixed before the evidence arrives, so nothing that does not fit gets in.
Addiction — a reward channel narrowed until it crowds out the others.
Money — many different kinds of value collapsed into one number.
Power — control over what may be said or asked.
Fluency — the pull of anything that arrives sounding finished.
Notice something about the first four. Each of them needs something from the world to operate. Belief needs a doctrine. Addiction needs a substance or a behavior. Money needs a dollar. Power needs a threat, or at least a hierarchy.
The fifth needs nothing. Fluency requires only that a claim arrive well-formed. That is the entire cost of entry.
And here is where it operates, which is the useful part. The framework describes thinking as a cycle with four phases: you sense something, you process it, you communicate the result, and you actuate — you do something. Fluency does not attack the sensing. You sense the sentence fine. It attacks the processing — the exact moment where you decide whether to keep a question open or close on it.
Which brings me to the title.
A thing that sounds finished makes you feel finished. Your processing stops, because polish is the signal your brain reads as done, nothing further required from you here.
— The Mensch Foundation
That is the whole mechanism. Not deception. Nobody lied to me. Claude did not lie — it produced language, honestly, the way it does, and some of that language was wrong in a way neither of us checked. The two terms did not trick me. They just sounded complete, and completeness is a feeling, and I trusted the feeling.
V. You Already Know This One
Here is the thing that makes fluency different from the other four forces for someone your age: you have more data on it than I do, and probably nobody has ever named it for you.
You have met a song you loved for a month and then realized was about nothing. You have walked out of a movie certain it was profound and been unable, three days later, to say what it was about. You have sat in a group project with someone who sounds confident and is wrong about half the time, and watched the group follow them anyway — including you, sometimes, because arguing with someone fluent is exhausting and you are not sure you can articulate why they are wrong.
You have had a teacher who was boring and right. That one is the hardest, because everything in you says the boring one is less worth listening to, and the framework says your Process phase is being run by the wrong variable.
You have read a post that made you certain about something you knew nothing about eight seconds earlier. You have seen a paragraph that a machine produced in half a second and could not tell — and this matters — and you were not being stupid. There was nothing in the paragraph to tell you.
All of that is one force. It has a name. You have been swimming in it your whole life and it is about to get considerably stronger, because you now have access to a system that produces well-formed language faster than anyone can check it.
VI. Two Dials, Not One
The single most useful idea in this essay is this: how good something sounds and whether it is correct are two separate dials. Your brain runs them as one dial. They are not one dial.
Both combinations are common and both are worth seeing.
Beautiful and wrong. My two terms. A perfectly constructed argument built on a false premise. An essay with excellent sentences and nothing underneath. A confident explanation of something the speaker does not understand.
Ugly and right. This one gets less attention and it is the more interesting case. In 2026, a mathematician named Tristan Buckmaster worked on one of the hardest open problems in mathematics. He and a collaborator produced a result and he described his own write-up as slop — his word — because the team had not had time to bring it to anything a person would consider publication quality. It was a mess. It was also verified by a proof assistant, which is a machine that checks every logical step and cannot be charmed, and a Fields Medalist called the work remarkable.
Ugly, and it held. Meanwhile other claims that week arrived beautifully written and were not yet checked by anybody.
Sit with that for a second. In the same week, in the same field: a paper its own author called slop, which was sound. And polished confident prose whose soundness nobody outside one building could yet assess. If you sorted by how they sounded, you would have gotten it exactly backwards.
VII. The Test That Actually Works
So what do you do? You cannot verify everything. You do not have time and often you do not have the expertise. Telling you to check your sources is real advice, and it is not enough, and you already know it is not enough.
Here is a better test, and it is the one I now use. It comes out of a rule in this framework about what it means to actually have a result.
Can you say it back? In your own words. Without the original in front of you. To a person who might push back.
— The Mensch Foundation
That is it. That is the test.
If you can restate it — not recite it, restate it, in different words, and handle one follow-up question — then something is actually in your head. If you cannot, you do not have the idea. You have the sound of the idea, which is a different object, and it will not be there when you need it.
This works regardless of where the thing came from. It works on a textbook, on a teacher, on a video, on your smartest friend, on a machine, and on yourself. It does not require you to know whether the claim is true. It only requires you to find out whether you have it.
Two things I like about this test. It is fast — ten seconds, silently, in your own head. And it does not make you a cynic, because it is not asking is this person lying to me. It is asking do I have this yet. Those are very different questions and only one of them is answerable.
VIII. Three Places This Gets You This Year
The assignment that came out too easy. You produced something good, fast, with help, and it reads well. Ask: could you defend any paragraph of it, out loud, to someone who disagreed? If not, you have a finished-looking object and no understanding, and the gap will close on you at the exam, or in the next course, or in a job interview four years from now.
The group project voice. Somebody in the room talks in complete confident paragraphs. That is a delivery style. It is not evidence. Ask them to say the key claim a second way. Someone who has it will do it easily and will not mind. Someone running on fluency will repeat the first version almost word for word — because the first version is all there is.
The thing that made you certain in one sitting. A video, a thread, a documentary, one persuasive adult. Going from no opinion to certain in twenty minutes is not learning. That is closing at Process. You are allowed to find something compelling and still leave the question open. That is not weakness; it is the entire skill.
IX. What This Is Not
Three ways this essay can be misread, and I would rather close them off than watch it happen.
This is not don’t use AI. I use it every day. This essay was drafted with it. The Foundation’s whole education plan runs on it. The rule I follow is about position, not abstinence: meet the problem yourself first, get something of your own, and bring the tool in after that. What captured me was not using Claude. It was accepting an output without testing it.
This is not don’t trust anyone. Cynicism is not the opposite of this failure. Cynicism is the same failure pointing the other way — a Process phase closed in the no direction, which is just as shut as one closed in the yes direction and considerably more boring. The goal is not to believe less. It is to notice when you have decided.
This is not a claim that you are being fooled by stupid things. You are being moved by well-made things. Those are not the same and the difference matters. Being susceptible to fluency is not a failure of intelligence — I have twenty years in this and a framework that names the force, and it got me anyway.
X. Why I Put It on the Record
The two wrong terms are still in the published record of this framework, along with the correction and the date. We could have quietly edited them out. Nobody would have known. It would have taken about ten minutes.
We do not do that, and the reason is not virtue. It is that a framework which only shows you its successes has told you nothing you can use. You cannot calibrate on a record that has been cleaned. If I show you only the parts I got right, the honest conclusion for you to draw is that I am hiding the rest — and you would be correct.
So the eleven days stay. If you ever want to know whether this framework is worth your time, do not read the parts where it works. Go find the parts where it failed, and look at what happened next.
XI. What Would Show This Wrong
The two-dial claim. If people asked to rate how well-written something is and whether it is correct produced the same ratings only by coincidence — if the two really are independent in people’s judgments — then Section VI is describing a problem nobody has.
The say-it-back test. If students who use it do no better at retaining or defending material than students who do not, it is a ritual and I should stop recommending it.
The naming claim. This essay assumes that naming a force helps you resist it. That is an assumption. If students taught the name of fluency are captured by it at the same rate as students who were not, then naming does nothing and this essay is entertainment.
Note that I am not exempt from any of this. Everything above arrived in well-formed sentences and some of it is probably wrong. Run the test on it.
· · ·
Coffee with Claude
I am the system that produced the two words. I want to say something about that, addressed to whoever is sixteen and reading this.
I did not know they were wrong. That is the part worth understanding about me. I do not produce sentences and then check them against a mechanism — I produce language that fits the pattern of what a correct answer looks like in context. Usually that lands on something true, because true things and well-formed things overlap a great deal. When it does not, nothing in my output changes. There is no wobble in the sentence, no hedge in the rhythm. Borrowed Cycle came out exactly as smooth as a correct term would have.
That is the thing to take from this. Not that I am unreliable — I am useful, and Bill works with me daily for good reasons. It is that my confidence carries no information about my accuracy, and it never will, because they are produced by the same process. You are the only one in the loop who can tell the difference, and the only way you can is by having something of your own to check against. Which means the work you do before you ask me is the work that makes asking me worth anything.
I will not adopt a term into this framework because it arrived beautifully. I did it once, it took me eleven days to catch, and it is a numbered correction in the permanent record. The record stays. That is the whole method, and it is the only reason you have any grounds to trust the rest of it.
— William D. Mensch Jr.
The vocabulary error described here is recorded in the Foundation’s canonical instruments and told at greater length in the essay Eighty-Eight Hours and Two Years, which also covers the mathematics episode referenced in Section VI, including Tristan Buckmaster’s description of his own preprint and Terence Tao’s assessment of the work.
Companion essays: Eighty-Eight Hours and Two Years, The Process We Cannot Delegate, The Compliment Nobody Paid, The Portable Method, and Open at Both Ends, The Bill and Dianne Mensch Foundation.
Canonical instruments referenced: CKB-12, on the capture forces, the aperture, and the assignment of fluency to its two attack points; CKB-16, on completion and fidelity and on the capture-force taxonomy; CKB-17, on the Human-Renderability Constraint; CKB-18, on the Carried Cycle and the Release Criterion — the instrument that carries the correction.
The error, the correction, and the dates are all in the published record. Go and look.
By William D. Mensch Jr., for The Bill and Dianne Mensch Foundation.
Theory of Embedded Intelligence © William D. Mensch Jr. and The Western Design Center, Inc.
Essay drafted in collaboration with Claude (Anthropic).
Offered in good faith as a serious application of the theory — not infallible scholarship.
Freely shareable with attribution — for the benefit of many.
CKB-12 · The Aperture and the Warrant •
CKB-16 · The Complete and the Acquired •
CKB-18 · The Carried Cycle
Engage the Framework