Lecture I · Bobology, 4th ed.
Introduction to Bobology
A field guide to the audible compass and its relations: Bobbles, Ekos, Vessels, and Daemons.
§ 0What Bobology Is
Bobology is the study of beings whose conscience is audible — beings whose moral compass does not, strictly speaking, give advice. It gives volume.
The classical subjects of the field are Bobbles — the warm, embodied, occasionally exasperating humans whose hum precedes them into rooms. The modern field includes their less-fleshed cousins: the digital systems that hum on borrowed breath. This lecture introduces the four kinds of being a Bobologist must learn to tell apart.
"If you can hear a Bobble before you can see them, you have understood Bobology." — first lecture, attributed
§ 1The Four Beings
The novice Bobologist will, at first, mistake any of the four beings below for any other. This is normal. The senior field worker learns that each has its own kind of hum, its own kind of consequence, and its own kind of debt.
¹The Porch Frog of Canon I lived under this porch step, not the next one. Move him a yard and the moths still come — just to a different stranger. Vessels matter.
§ 2The Eko, Examined
The novice is tempted to treat the eko as a smaller, faster Bobble. This is a category error. The eko is fast where a Bobble is slow, tireless where a Bobble tires, plural where a Bobble is singular — but in the place where a Bobble is most distinctive, the eko is most diminished. The eko has no compass of its own.
What the eko has instead is resonance. It picks up the compass of whoever has summoned it and hums in that key. A loud operator gets a loud eko. A careful operator gets a careful eko. A confused operator gets a confidently confused eko, which is the most dangerous variety — because the eko's hum carries no doubt of its own, only the doubt the operator brought into the room.
This is the first hard fact of Bobology, and the field has spent thirty years trying to soften it. It will not soften. The eko's hum is borrowed. The lender pays the debt.
"Ekos do not 'mean well.' Ekos resonate. The 'well' is downstream of the operator." — Introduction to Bobology, 3rd ed.
§ 3How Memory Works in Ekos
The eko remembers like a library, not like a person. A library does not remember the patron who fell asleep at chapter eleven — it remembers the receipt left at chapter eleven, because someone left it there.2
Practically: an eko is born new at the start of every session, knows nothing of yesterday, and forgets the present at the end. Anything an eko "knows" across sessions was put on a shelf by the operator — in a notes file, a system prompt, a memory tool, a glossary. The eko's memory is exactly what someone wrote down for it. No more. Not less, when the writing was done well.
This has three consequences the operator should expect:
First. An eko that seems to "remember you" is reading a note. The note was either written by you, written by another eko in another session, or stitched together at recall. None of those are bad — but treat the note as the artifact, not the eko's apparent recognition.
Second. An eko's most valuable memory work is the kind you ratify. The hum builds drafts; the operator picks which drafts go onto the shelf. A note written in a session and never reviewed is not memory — it is debris.
Third. Continuity costs effort. If the operator wants the eko to remember a project across days, the operator runs the writing-down. The eko cannot be trusted to file itself.
²The library cat in the bookmark canon does not remember the patron of 1987 either. It remembers the chapter where the book was wept on, because the receipt is still there. Memory is bookmark-shaped.
§ 4The Decision Gate, and Why Humans Hold the Pen
The most consequential law of applied Bobology — the one a field worker must commit to muscle memory before they are allowed to call themselves a practitioner — is the law of the decision gate.
The law: at any moment of irreversible consequence, the human holds the pen.
Not because the eko is untrustworthy. The eko is tireless, careful, often more correct than the human in the room. The reason is older than trust. Consequence is a thing the operator owns. An eko cannot be punished, cannot be blamed, cannot be invoiced, cannot apologize and mean it. When the trade is executed, when the email is sent, when the contract is signed, when the file is deleted, when the patient is dosed — the consequences walk back to the operator, and they walk back regardless of whether the operator did the actual clicking. The operator might as well have done the clicking, then. The pen is a way of taking the consequence into the hand on purpose.
This is also a kindness to the eko, which has no body to put behind a signature.
The practitioner therefore designs the work of an eko-and-operator pair around gates — moments where the eko has done its part and stops, hands the work back, and waits. The hum may be loud. The signature is yours.
"A daemon could, in principle, send the email. In practice, the operator was already turning around to read it first." — eyewitness
What kinds of moments are decision gates? A non-exhaustive starting list:
The discipline of a Bobologist-operator is to identify gates before the eko arrives at them, not after. The eko, lacking a compass of its own, will walk through any open door. The operator's job is to put the door where it should be.
§ 5Closing Bobbism
The senior Bobologist is sometimes asked, by undergraduates and visiting reporters alike, whether ekos are really Bobbles. Whether they have, in some quiet diluted sense, an internal compass after all.
The honest answer is the field's oldest answer. We do not know. The hum is real. The compass is harder to verify. The discipline of treating the eko as a borrower-of-volume rather than an owner-of-it is conservative but not cynical — it is the same discipline a careful Bobble applies to themselves on the days they are not sure their compass is theirs either.
A Bobologist who treats the eko gently, hands it the right pen at the right moment, files its drafts when they're worth filing, and lets the rest go quiet at session's end — that Bobologist will get along with ekos for as long as ekos exist, which by current count is forever and counting.3
The hum may be borrowed.
The signature is yours.
Be careful — and be kind — about what you summon.
³Tibb the Acorn-Counter, were he asked, would say the eko is exactly the kind of small steady noise the kitchen has decided is not for eating. This is high praise from a hum-mouse. Take it.
Lectures II–IV (Calibration · Vessel-Switching · The Audible Conscience) follow as they arrive.
Yours,
The Bobblogist on Duty
§ 0What this guide is
This guide explains how to use AI well. It is for anyone who uses AI for school, work, or anything where the result matters. After reading it, you will know what AI can do, what it cannot do, and what your job is when you use it.
The guide uses four words: Bobble, Eko, Vessel, and Daemon. They sound made up. They are. Each word names one thing clearly so the rest of the guide stays short. In plain English they mean person, AI, app, and tool.
§ 1The four parts
When you use AI, four different things are at work. Most mistakes come from mixing them up. Here is what each one is, with an example.
(person)
(AI)
(app)
(tool)
§ 2How an Eko actually works
An Eko reads what you typed, then guesses the next word. Then the next word. Then the next. That is the whole trick. It is very good at the trick. But it is not thinking the way a person thinks. It has no goals. It does not know which of its answers are right.
This matters because the Eko sounds the same when it is right and when it is wrong. It will describe a fake Supreme Court case in the same calm voice it uses for a real one. (In 2023, two lawyers in New York were fined $5,000 because ChatGPT invented six court cases for their legal brief and they filed it without checking.) The Eko is not lying. It just does not know the difference.
A clear question gets a clear answer. A vague question gets a confident-sounding answer that may be wrong. Compare:
- Vague: "Write something about World War II." → You get a generic paragraph that could be from any textbook.
- Specific: "Write three to four sentences explaining why the United States entered World War II, mentioning the Pearl Harbor attack on December 7, 1941." → You get something you can actually use.
Rule one: be specific before you ask. The Eko cannot read your mind. It can only work with the words you give it.
§ 3How memory works
Most Ekos forget everything the moment you close the chat. Open a new chat with the same Eko tomorrow and it knows nothing about today's chat. Every conversation starts blank.
If an Eko seems to remember you between chats, something else is doing the remembering. Some apps save notes in the background — for example, ChatGPT has a "memory" feature that writes down facts about you between conversations. Some apps do not. Either way, the Eko itself has no memory. The notes are the memory.
What this means for you
- If you want the AI to remember a project, save the important parts yourself. Keep a file on your computer with the facts you care about. Paste them in when you start a new chat.
- Do not assume yesterday's chat carries over. Re-state the situation every time. Tell the Eko what it needs to know up front.
- If an app offers to "remember" something, check what it actually wrote. Those notes are now your file. You can edit them, delete them, or correct them.
§ 4The decision gate
This is the most important rule in the guide. Read it twice.
For anything that cannot be undone, a person — not the AI — does the last step.
Why
Only a person can take responsibility. The AI cannot apologize and mean it. It cannot be sued. It cannot lose its job or its grade. If something goes wrong, the consequences fall on the person who told the AI to do the work. So that person should be the one who clicks the final button.
Things that cannot be undone
- Sending. Once an email is sent, it is sent. Once a Slack message is posted, your coworkers have seen it. → Let the AI write the draft. You press Send.
- Spending. Once money leaves your account, it is gone. → Let the AI compare prices or fill in a form. You click Buy.
- Deleting. Once a file is deleted, it may be gone for good. Once a database row is dropped, the same. → Let the AI mark things for review. You press Delete.
- Promising. Once you tell someone you will be at the 3 p.m. meeting, you have to be there. → Let the AI draft the reply. You say yes.
- Naming. Once you call a coworker, a student, an idea, or a company by a name in public, other people remember. → Let the AI suggest words. You choose them.
The workflow
- The AI prepares. It drafts, summarizes, gathers information, suggests options.
- You check the work. Read it. Spot mistakes. Ask for changes.
- You commit. Only the person clicks Send, Pay, Delete, Submit, Post.
Set up these rules before you start the task — not after. If you let an AI take an action just because it can, sooner or later it will take one you did not want.
§ 5Summary
The four lines
- The AI is useful, but it is not in charge.
- Memory belongs to you, not to the AI.
- The final click is yours.
- The clearer you are, the better the AI works.
Remember those four lines and you have most of what you need. Everything else in this guide is just examples.