Journal № 14

From Interaction to Action

How does something vague become precise?

Every action starts somewhere vague. A dry mouth. A page you need on paper. A few seconds later there’s a glass in your hand, or a sheet coming out of a printer.

In between, something vague becomes precise. This piece follows that path, level by level, first in a person, then in a machine. Then it looks at what changes now that AI can start from the vague part too.

Where I started: clarity

My starting point was Wittgenstein. The Tractatus opens with a promise: what can be said at all can be said clearly.

Russell and the logicians of his time wanted exactly that. A language with no ambiguity.

In a way, that language exists now. We use it every day. It’s called code.

But intentions start before words, and before words everything is vague. Code only begins after someone has done the work of being precise.

How it works for a person

Take the simplest thing. You’re thirsty, and you drink a glass of water. It looks like one gesture. It goes through five levels.

InteractionDry mouthIntentionI want waterPlanThat glass, thereActionReach, adjust, drinkFeedbackThirst fades. The goal ends.
  1. InteractionDry mouth
  2. IntentionI want water
  3. PlanThat glass, there
  4. ActionReach, adjust, drink
  5. FeedbackThirst fades. The goal ends.

These levels aren’t separate floors. They talk to each other all the time. The body corrects while it moves, and sometimes the intention only takes shape while you’re doing it.

The goal is yours. Shaped by your body, your culture, other people. But yours.

How it works for a machine

Now the machine version. You press Print, and a few seconds later a sheet of paper comes out of a printer.

Print PagesCopiesPrinter 1–3 2 Office Print Print queue Network InteractionInterpretationHandoffExecution You press PrintCode writes instructionsSent to the printerInk on paper Feedback: “Printed”, or “Paper jam”
Print PagesCopiesPrinter 1–3 2 Office Print InteractionYou press Print InterpretationCode writes instructions Print queue Network HandoffSent through the print queue and network ExecutionInk on paperFeedback“Printed”, or “Paper jam”

The print dialog does something important before anything else: it makes you be precise. Which pages, how many copies, which printer. The vague part stays with you.

From there, each level translates for the next one. Code turns the document into instructions, the system sends them along, and at the end the printer moves.

The machine starts from a goal it received, and settles every ambiguity before it acts.

The ladder and the circle

Same levels. Two architectures.

Comparison
Person
Machine
Where the goal comes from
From a need
Received
When it decides
While acting
Before acting
Where feedback reaches
Every level
Some levels

Where AI comes in

With classic software, the hardest step is yours: turning a vague want into precise input. That’s what the print dialog is for.

A language model takes over that step. You say what you want in your own words, and the model does the interpretation that used to need a dialog, or a programmer.

Classic software With a language model What you want You make it precise Same ladder below What you want Print the pricing part for tomorrow, two copies.| In your own words The model makes it precise Same ladder below
Classic software Print the pricing part for tomorrow, two copies.| What you wantYou make it preciseSame ladder belowWith a language modelWhat you wantIn your own wordsThe model makes it preciseSame ladder below

It’s the first machine that starts closer to where people start.

The ladder below it stays the same, and the goal is still received. Agents are starting to close the loop in a few places: they try, check, and correct. What’s still missing is real learning during use, and goals of their own.

The levels, one by one

Scroll. The person and the machine go down together, level by level.

LevelPersonMachine
1Interaction. Your mouth is dry. Nobody asked you anything: your body did.Interaction. You press Print. The dialog has already made you precise: which pages, how many copies.
2Intention. I want some water. The need becomes a goal.Interpretation. The app turns the document into instructions the printer understands.
3Plan. That glass, on the table. The goal meets what’s around you.Handoff. The instructions travel through the print queue and the network to the printer.
4Action. You reach, grip, drink. Your hand adjusts all the way.Execution. The printer moves the paper and puts ink exactly where it was told.
5Feedback. Thirst fades, and the intention simply ends. Or it doesn’t, and you pour another.Feedback. “Printed”, or “Paper jam”. It can try again. It can’t decide you needed a different page.

An open question

So, in this view, AI is a new disambiguation tool: it takes on our ambiguity and translates it into the deterministic level of code.

For now, AI systems don’t generate their own goals. They only work through short chains of tasks, and the ultimate goal still originates from an interaction with us. We’ve also seen that they haven’t yet closed the loop.

But if, as is happening, we’re moving toward these systems being able to close the feedback loop at every level, making them adaptive and therefore more capable of generating genuine goals of their own, are we still talking about tools?


Further reading

← Back to Journal

Get the next entry in your inbox.

One email per article. Roughly. Plus the occasional update, when it ships.