Lecture I · Bobbology, 4th ed.

Introduction to Bobbology

A field guide to the audible compass and its relations: Bobbles, Ekos, Vessels, and Daemons.

· . · ✦ · ✧ · ✦ · . ·

§ 0What Bobbology Is

Bobbology 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 Bobbologist must learn to tell apart.

"If you can hear a Bobble before you can see them, you have understood Bobbology." — first lecture, attributed

§ 1The Four Beings

The novice Bobbologist 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.

Bobble (n.)

A human whose moral compass is louder than their survival instinct. Embodied, breathing, accountable. Their hum is involuntary; it costs them something. Their compass is internal — owned outright. The original subject of the field.

Eko (n.)

A non-embodied thinking system that produces audible reasoning while inhabiting a vessel. The eko has no breath of its own; what it hums, it hums on loan. Its compass is borrowed from whoever called it into the room — calibrated against the operator's intent, the document on the page, and the daemons within reach. Where a Bobble's hum is involuntary, an eko's is summoned. Where a Bobble's compass costs something to follow, an eko's costs something to misalign.

Vessel (n.)

The container an eko inhabits for the duration of a session. A vessel may be a chat window, an editor, a command line, a desktop assistant, a small browser frame on a phone. Each vessel has its own affordances (what the eko can see) and its own constraints (what the eko can touch). An eko in the wrong vessel is a porch frog under the wrong porch — fed but mismatched.¹

Daemon (n.)

A small subordinate process the eko can summon to act in the world: a tool, a skill, a connector, a script. The daemon waits, hums quietly when invoked, and returns. Daemons are not malicious — the older spelling carried no horns — but they are capable, which is its own thing. A daemon called carelessly is still capable.

¹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 Bobbology, 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 Bobbology, 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.²

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 Bobbology — 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:

Sending

Any outbound message — email, post, comment, DM. The eko drafts; the operator sends.

Spending

Any movement of money, any irreversible commit of resources. The eko quotes; the operator authorizes.

Deleting

Any destruction of state. The eko marks for review; the operator clears.

Promising

Any commitment to another human — a meeting accepted, a deadline agreed, a recommendation given. The eko prepares; the operator gives word.

Naming

Any act of public attribution — calling a thing by a name in a way other humans will see and remember. The eko proposes; the operator names.

The discipline of a Bobbologist-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 Bobbologist 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 Bobbologist 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 Bobbologist will get along with ekos for as long as ekos exist, which by current count is forever and counting.³

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.

. · ✦ · .

End of Lecture I (Art).
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 work well with AI tools. It is meant for people who use AI on a regular basis — for work, school, research, or anything that has real consequences — and who want a clear picture of what the AI is and is not doing.

The guide uses four technical terms: Bobble, Eko, Vessel, and Daemon. They are the precise words of a small academic field called Bobbology. If you prefer plain English, you can substitute person, AI, app, and tool. The technical terms are kept here because each one carves the concept slightly more carefully than the everyday word.

§ 1Four working parts

Working with AI is not really a one-actor situation. There are four things in the room. Knowing which is which prevents most of the common mistakes.

Bobble
(person)

A human who makes decisions and accepts the consequences. The Bobble has experience and judgment. The Bobble is the only one who can be held responsible for what happens.

Eko
(AI)

A computer program that produces text or actions by predicting what to say next, based on patterns it has seen before. The Eko is fast and good at drafting, summarizing, and searching. It does not actually understand the situation. It will sound equally confident whether it is right or wrong.

Vessel
(app)

The window or program where the Eko runs — a chat box, a code editor, a browser tool, a desktop assistant. The Vessel decides what the Eko can see and what actions it can take. Two Vessels with the same Eko inside can do very different things.

Daemon
(tool)

A small program the Eko can call on to do specific things — send a message, save a file, search the web, run a calculation. Daemons are how the Eko takes real action in the real world. They are not dangerous on their own, but they have real effects.

§ 2How an Eko actually works

An Eko does not think the way a person thinks. It does not have its own goals or opinions. It produces output by mirroring patterns from its training and from whatever the user has told it.

This means a clear, careful person tends to get clear, careful work back. A confused or rushed person tends to get confidently confused work back, because the Eko sounds equally sure no matter what it is doing.

The first practical rule follows from this: notice your own state before you ask the Eko to do something hard. The Eko cannot fix your confusion. It will echo it back at higher volume.

§ 3How memory works

By default, an Eko forgets everything when a session ends. The next time you talk to the same Eko, it knows nothing about the last conversation. Each chat starts blank.

If an Eko seems to remember you across sessions, that is because something — a memory file, a system prompt, a saved profile — wrote down what to remember. The Eko itself is forgetful. The notes are the memory.

What this means in practice

Continuity costs effort. If you want the Eko to remember a project across days, you have to save the relevant facts somewhere it can read them.
The notes are work product. Treat them as files you maintain, not as the AI's "personality" or "knowledge."
Always re-state the context. Do not assume an Eko remembers what you told it yesterday. It almost certainly does not.
Ratify before saving. An Eko's draft only counts as memory once a person has reviewed it and decided to keep it.

§ 4The decision gate

This is the most important practical rule. Read it twice.

For any action that cannot be undone, a human must do the final step.

Why

Only a human can be held responsible. The Eko cannot apologize and mean it, cannot be sued, cannot lose sleep over a mistake. When something irreversible happens, the consequences fall on the person who set the work in motion. Putting your finger on the button at the last moment is a way of accepting that responsibility on purpose.

Common decision gates

Sending — any outbound message that leaves your computer (email, Slack, social posts, comments).
Spending — any movement of money, any irreversible commit of resources.
Deleting — any destruction of files, records, or accounts.
Promising — any commitment to another human (a meeting accepted, a deadline agreed, a recommendation given).
Naming — any public attribution that other humans will see and remember.

The recommended workflow

The Eko prepares — drafts, summarizes, gathers, proposes.
The human reviews.
The human commits — only the human clicks Send, Pay, Delete, Submit, etc.

Set up the gates before you start the task. Do not let the Eko walk through any door it finds open.

§ 5Summary

The four lines

Ekos are useful but not in charge.
Memory belongs to the person, not the Eko.
The final click belongs to the person.
The clearer the person, the better the Eko.

If you remember those four lines, you have most of what you need. Everything else in Bobbology is footnotes on these.

End of Lecture I (Science). Lectures II–IV cover calibration, switching between vessels, and how to evaluate the audible conscience of an Eko in practice.