Philosophy on TurboVision

AI, Language, and Protocols

Mon, 20 Apr 2026 00:00:00 +0000

A Small Essay Series

This subsection gathers a connected series of essays about what really changes once natural language becomes an interface to computation. At first that shift looks like pure liberation: fewer rigid commands, fewer formal barriers, and a much wider audience that can suddenly “program” by speaking in ordinary language. But the moment this freedom becomes useful at scale, the old questions return in a new form: structure, protocol, control, abstraction, governance, consequence, and the strange human urge to rebuild frameworks around every promising new medium.

The series moves through several connected ideas: why freedom quickly recreates formalism one layer higher, why prompting is not quite the same thing as conversation, whether a machine-native control language may sit beneath English prompting, how agent-to-agent communication could evolve beyond human prose, why the best historical analogy for all of this may not be science fiction at all, but the older story of writing hardening into administration, and why MCP changes the question from usefulness to consequence.

These texts are meant less as isolated blog posts and more as one long argument explored from different angles. They are technical where the topic demands it, philosophical where the topic deserves it, and intentionally provocative where the current AI discourse has become too shallow, too euphoric, or too lazy in its metaphors.

The Real Historical Analogy

Mon, 20 Apr 2026 00:00:00 +0000

The most popular analogies around AI are usually the worst ones, because they jump straight to apocalypse, utopia, or machine rebellion and miss the transformation already happening in front of us. A far better analogy is older, less glamorous, and much more revealing: the history of writing becoming administration.

TL;DR

The strongest historical analogy for LLMs is not Skynet, industrial automation, or a new species. It is the old pattern in which an expressive medium expands access and then hardens into records, templates, procedure, governance, and bureaucracy. Less cinema. More paperwork. Unfortunately that is usually where real power hides.

The Question

You may ask: if natural-language AI feels like a liberation from rigid interfaces, what historical pattern does it actually resemble? Is there an older moment where a flexible medium spread widely and then slowly turned into structure, procedure, and control?

The Long Answer

Yes. Writing.

The Better Analogy Is Older and Less Glamorous

Or more precisely: writing after it stopped being rare.

When we romanticize writing, we think of poetry, letters, memory, literature, philosophy, scripture, and thought made durable. All of that matters. But historically, writing did not remain only an expressive medium. As soon as it became socially central, it also became a machine for legibility.

It began to support:

ledgers
tax records
property claims
legal formulas
decrees
inventories
forms
standard contracts
administrative routines

The same medium that enabled reflection also enabled bureaucracy.

That is not an accidental corruption of writing’s pure spirit. It is what happens when an expressive medium starts carrying coordination at scale. The lyric and the ledger share a medium, and the ledger is usually better funded.

This is the historical rhyme that matters for AI.

Natural-language interfaces feel, at first, like a return from bureaucracy to speech. No more memorizing commands. No more obeying narrow syntactic rituals. No more learning the machine’s rigid grammar before the machine will meet you halfway. You can just speak.

But the moment that speech starts doing real work, the old dynamic reappears. The free exchange has to become legible, stable, and reusable. Then come templates. Then conventions. Then control layers. Then record-keeping. Then policy.

In other words, the medium begins to administrate.

Writing Became Administration

That is why I think the right analogy is not “AI replaces humans” but “language-to-machine interaction is becoming administratively scalable.” That phrase has none of the drama of science fiction, which is exactly why I trust it.

Notice how much current AI practice already fits that pattern.

At the expressive edge:

exploratory prompting
brainstorming
rewriting
questioning
improvisation

At the administrative edge:

system prompts
reusable role definitions
skill files
output schemas
tool policies
safety rules
evaluation harnesses
memory and trace retention

That is exactly the same medium bifurcating into two functions:

expression
governance

The mistake would be to think governance arrives from outside as an alien force. More often it emerges from the medium’s own success. Once too many people, too many workflows, and too many risks pass through the channel, informal use becomes too expensive.

This is why the writing analogy beats the science-fiction analogy. Science fiction lets us talk about AI while keeping one eye on spectacle. Administration forces us to talk about rules, defaults, records, compliance, and who gets to decide what counts as proper use. Less fun, more dangerous.

Science fiction keeps us staring at agency in the dramatic sense: rebellion, consciousness, domination, replacement. Those questions may have their place, but they are not what we are living through most directly right now.

What we are living through is far more mundane and therefore far more transformative:

who gets to issue instructions
in what form
with what defaults
under whose hidden constraints
with what record of compliance
and according to which evolving norms

That is administration.

A government clerk, a shipping office, a medieval chancery, and a modern AI platform may look worlds apart, but they share one deep concern: turning messy human intentions into legible operations.

That is why some of the current discourse feels so unserious to me. People keep asking whether the machine is becoming a person while entire companies are busy making it into procedure.

Once you look through that lens, many supposedly strange features of the current AI moment become obvious.

Why are people standardizing prompts? Because legibility enables coordination.

Why are teams writing internal style guides for model use? Because institutions cannot run on charm alone.

Why do skill files, tool schemas, and structured outputs proliferate? Because the medium is being prepared for scale.

Why does the language of “best practice” appear so quickly? Because informal success always creates pressure for repeatability.

Freedom and Bureaucracy Grow Together

This is also why the present moment feels ideologically confused. We are using the rhetoric of liberation while simultaneously building new bureaucratic layers. People notice the contradiction and either celebrate one side or denounce the other. I think both reactions are too simple.

The bureaucracy is not a betrayal of the freedom. It is what the freedom becomes when it has to survive contact with institutions.

That is an irritating sentence, but I think it is true.

There is another historical layer worth noticing: standardization often follows democratization, not the other way around.

Printing expands who can read and write, and then spelling, grammar, and editorial norms harden. Open networks expand who can communicate, and then protocols stabilize the traffic. Mass politics expands participation, and then bureaucracy grows to make populations administratively legible. Natural-language computing expands who can “program,” and then prompt rules, tool contracts, and agent frameworks appear.

This pattern is almost embarrassingly regular. We keep acting surprised by it anyway, which may be one of the more stable features of modernity.

It should also change how we talk about power.

The frightening question is not only whether AI becomes an autonomous sovereign. The more immediate question is who controls the administrative grammar of human-machine exchange. In older regimes, literacy itself was power. Later, access to legal language was power. Later still, access to code and infrastructure was power.

Now the emerging power may sit in the ability to shape:

system defaults
hidden instructions
moderation layers
tool affordances
evaluation criteria
acceptable interaction styles

That is a quieter kind of power than Skynet fantasies, but in practice it may matter more. It is much easier to smuggle power in through defaults than through manifestos.

Because most people will not meet AI as pure model weights. They will meet it as institutionalized behavior.

And institutionalized behavior is always partly political.

The Real Struggle Is Over Administrative Power

This is where the analogy becomes genuinely useful rather than merely clever. It gives you a way to organize the whole field without falling into either marketing or panic.

You can ask of any AI feature:

Is this expressive? Is this administrative? Or is it a hybrid trying to hide the transition?

A freeform chat UI is expressive. A schema-constrained workflow is administrative. A friendly assistant with hidden system rules is a hybrid, and hybrids are where most of the real tension lives.

The writing analogy also helps explain the emotional tone people bring to AI. Some are exhilarated because they feel the expressive release. Others are suspicious because they can already smell the coming bureaucracy. Both are perceiving real parts of the same transformation.

The optimists are seeing the collapse of unnecessary formal barriers. The skeptics are seeing the rise of a new governance layer.

Again, both are right.

And this returns us to the opening paradox. Why does a medium that promises freedom generate rules so quickly? Because freedom by itself is not enough for archives, institutions, teams, compliance, safety, memory, and distributed execution. A society can play in a medium informally for a while. It cannot run on that informality forever.

That does not mean we should embrace every new layer of prompt bureaucracy with cheerful obedience. Quite the opposite. Once you recognize the administrative turn, you can ask better questions:

which rules are genuinely useful?
which are cargo cult?
which increase transparency?
which hide power?
which preserve human agency?
which quietly narrow it?

That is the adult conversation.

So if you want the real historical analogy, here is mine:

LLMs are not best understood as a talking machine waiting to rebel. They are better understood as the latest medium through which human intention becomes administratively legible at scale.

That may sound less cinematic than Skynet, but it is more historically grounded and much more relevant to the systems we are actually building.

The true drama is not that the machine may wake up one day and declare war. The true drama is that we may succeed in building a new universal administrative layer and barely notice how much social power gets embedded in its defaults, templates, and permitted forms of speech.

An ugly example helps here. Suppose every internal assistant in a large company quietly prefers one style of project plan, one tone of escalation, one definition of risk, one preferred sequence of approvals, one acceptable way of disagreeing. Nobody declares a doctrine. Nobody publishes a manifesto. People just start adapting to what the system rewards. That is how a lot of administrative power actually enters the room.

That is not a reason for panic. It is a reason for seriousness.

Every civilization that learns a new medium first celebrates its expressive power. Soon after, it learns what paperwork can do with it.

Summary

The best historical analogy for LLMs is not cinematic rebellion but administrative expansion. Like writing before them, natural-language interfaces begin as expressive tools and then harden into templates, records, procedures, and governance. That is why AI feels simultaneously liberating and bureaucratic: both experiences are true, because the same medium is serving both expression and institutional control.

Seen this way, the important question is not whether structure will emerge. It is whether the coming administrative layer will stay legible, contestable, and open to public scrutiny, or whether it will arrive in the usual smiling way: convenient, useful, efficient, and already half invisible.

When AI becomes part of society’s paperwork rather than its science fiction, who will notice first that the defaults have become law-like?

Related reading:

Freedom Creates Protocol

Mon, 06 Apr 2026 00:00:00 +0000

Natural-language AI was supposed to free us from syntax, ceremony, and the old priesthood of formal languages. Instead, the moment it became useful, we did what humans nearly always do: we rebuilt hierarchy, templates, rules, little rituals of correctness, and a fresh layer of people telling other people what the proper way is.

TL;DR

Natural language did not abolish formalism in computing. It merely shoved it upstairs, from syntax into protocol: prompt templates, role definitions, tool contracts, context layouts, reusable skills, and the usual folklore that grows around every medium once people start depending on it.

The Question

You may ask: if LLMs finally let us speak freely to machines, why are we already inventing new rules, formats, and best practices for talking to them? Did we escape formalism only to rebuild it one floor higher?

The Long Answer

Yes. And no, that is not a failure. It is what happens when a medium stops being a toy and starts carrying consequences.

Freedom Feels Loose at First

When people first encounter an LLM, the experience feels a little indecent. You type something vague, lazy, half-formed, maybe even badly phrased, and the machine still gives you back something that looks intelligent. No parser revolt. No complaint about a missing bracket. No long initiation rite through syntax manuals. Compared to a compiler, a shell, or a query language, this feels like liberation.

That feeling is real. It is also the beginning of the misunderstanding.

Because the first successful answer encourages people to blur together two things that should not be blurred:

expressive freedom
operational reliability

Those are related, but they are not the same thing.

If you want one answer, once, for yourself, free language is often enough. If you want a result that is repeatable, auditable, safe to automate, shareable with a team, and still sane three months later, then free language starts to feel mushy. That is the moment protocol walks back into the room.

You can watch the progression happen almost mechanically.

At 09:12 someone writes a cheerful little prompt:

Summarize this file and suggest improvements.

At 09:17 the answer is interesting but erratic, so the prompt grows teeth:

Summarize this file, keep the tone technical, do not propose speculative changes, and separate bugs from style feedback.

At 09:34 the task suddenly matters because now it is being copied into a team workflow, or wrapped around an agent that can actually do things, or handed to a colleague who expects the same behavior tomorrow. So examples get added. Output format gets fixed. Constraints get named. Edge cases get spelled out. Tool usage gets bounded. Failure behavior gets specified. And with that, the prompt stops being “just a prompt.” It becomes a contract wearing friendly clothes.

The Prompt Becomes a Contract

At that point it starts acquiring all the familiar properties of engineering:

assumptions
invariants
failure modes
version drift
style rules
compatibility concerns

That is why “prompt engineering” so quickly mutated into “context engineering.” People noticed that the useful unit is not the single sentence but the whole frame around the task: role, memory, retrieved documents, allowed tools, desired output shape, refusal boundaries, escalation behavior, evaluation criteria. In other words, not a line of text, but an environment.

That is also why “skills” emerged so quickly. I do not find this mysterious at all, despite the dramatic naming. A skill file is simply what happens when a behavior becomes too valuable, too repetitive, or too annoying to restate every time. It says, in effect: “When this kind of task appears, adopt this stance, gather this context, follow these rules, and return this shape of answer.” That is not magic. It is protocol becoming portable.

There is a faintly comic irony in all of this. We escape the old priesthood of formal syntax and immediately grow a new priesthood of prompt templates, system roles, and context strategies. Different robes, same instinct.

You could object here: if we are writing rules again, what exactly did we gain?

Quite a lot.

The old formal layers required the human to descend all the way into machine-legible syntax before anything useful happened. The new model lets the human stay much closer to intention for much longer. That is a major shift. You no longer need to be fluent in shell syntax, parser behavior, or API schemas to start interacting productively. You can begin from goals, not grammar.

But goals are high-entropy things. They arrive soaked in ambiguity, omitted assumptions, social shorthand, wishful thinking, and the usual human habit of assuming other minds will fill in the missing parts. Machines can sometimes tolerate that. Systems cannot tolerate unlimited amounts of it once money, time, correctness, or safety are attached.

This is where a lot of current AI talk becomes mildly irritating. People love saying, “you can just talk to the machine now,” as if that settles anything. You can also “just talk” to a lawyer, a surgeon, or an operations engineer. That does not mean freeform speech is enough when the stakes rise. The sentence becomes serious long before the sentence stops being natural language.

So the new pattern is not:

free language replaces formal language

It is:

free language captures intent
protocol stabilizes intent
tooling operationalizes protocol

That is the more honest model. Less romantic, more true.

Why Humans Keep Rebuilding Structure

The deeper reason is that structure is not the opposite of freedom. Structure is what freedom turns into, or curdles into, depending on your mood, once scale arrives.

Human beings romanticize freedom in abstract form, but in practice we keep generating conventions because conventions reduce coordination cost. Even ordinary conversation works this way. Speech feels free, yet every serious domain develops jargon, shorthand, ritual phrasing, and unstated rules. Lawyers do it. Operators do it. Mechanics do it. Programmers certainly do it. The more a group shares context, the more compressed and rule-like its communication becomes.

There is also a more intimate reason for this, and I think it matters. Human minds are greedy for pattern. We abstract, label, sort, compress, and build little frameworks because raw complexity is expensive to carry around naked. We want handles. We want boxes. We want categories with names on them. We want a map, even when the map is smug and the territory is still on fire. That habit is not just intellectual vanity. It is one of the main ways we make memory, judgment, and navigation tractable.

That is why, when a new medium appears to offer radical freedom, we do not stay in pure openness for long. We start sorting. We separate kinds of prompts, kinds of contexts, kinds of failures, kinds of agent behaviors. We name patterns. We collect best practices. We define anti-patterns. We build checklists, templates, taxonomies, and eventually frameworks. In other words, we do to LLM interaction what we do to almost everything else: we turn a blur into a structure we can reason about.

Sometimes that instinct is useful. Sometimes it is cargo-cult theater. Both are real. Some prompt frameworks genuinely clarify recurring problems. Others are just one lucky anecdote inflated into doctrine and laminated into a slide deck.

LLM work is following the same path, only faster because the medium is software and software records its habits with ruthless speed. A verbal superstition can become a team standard by next Tuesday.

From Expression to Governance

There is a second irony here. We often speak as if prompting were the end of programming, but much of what is happening is actually the return of software architecture in softer clothes. A serious agent setup already contains the familiar layers:

input validation
API contracts
middleware rules
orchestration logic
error handling
logging and evaluation

The difference is that the central compute engine is now probabilistic and language-shaped, which means the surrounding discipline matters even more, not less.

This is why ad hoc prompting feels creative while production prompting feels bureaucratic. And let us be honest: once a company depends on these systems, bureaucracy is not a side effect. It is the bill. You want repeatability, compliance, delegation, and reduced blast radius? Fine. Someone will write rules. Someone will freeze templates. Someone will decide which prompt shape counts as “correct.” Someone will eventually win an argument by saying, “That is not how we do it here.”

The historical pattern is old enough that we should stop acting surprised by it. When literacy spreads, spelling gets standardized. When communication networks open, protocols appear. When institutions grow, forms multiply. When natural-language computing opens access, prompt scaffolds, schemas, and skills proliferate.

Freedom expands participation. Participation creates variation. Variation creates friction. Friction creates standards.

That cycle is almost boring in its reliability.

The most interesting question, then, is not whether this protocol layer will emerge. It already has. The real question is who gets to define it before everyone else is told that it is merely “the natural way” to use the system.

Will it be model vendors through hidden system prompts and product defaults? Teams through internal conventions? Open communities through shared practices? Or individual power users through private prompt libraries? Each one of those choices creates a different politics of machine interaction.

And that is where the topic stops being merely technical. The prompt is not only a command. It is also a social form. It decides what kinds of instructions feel legitimate, what kinds of behaviors are treated as compliant, and what kinds of ambiguity are tolerated. Once prompting becomes institutional, it becomes governance.

That sounds heavier than the cheerful “just talk to the machine” sales pitch, but it is closer to the truth. Natural language lowered the entry threshold. It did not suspend the need for discipline. It redistributed discipline.

So if you feel the contradiction, you are seeing the system clearly.

We did not fight for freedom and then somehow betray ourselves by inventing rules again. We discovered, once again, that free interaction and formal coordination belong to different layers of the same stack. The first gives us reach. The second gives us stability.

And in practice, every medium that survives at scale learns that lesson the same way: first by pretending it can live without structure, then by building structure exactly where reality starts hurting.

Summary

Natural language did not end formal structure. It delayed the moment when structure became visible. We gained a far more humane entry point into computing, but the moment that freedom had to support repetition, collaboration, and accountability, protocol came roaring back. That is not hypocrisy. It is how human coordination works, and probably how human thought works too: we reach for abstraction, labels, and frameworks whenever openness becomes too costly, too vague, or too exhausting to carry around unshaped.

So the interesting question is not whether rules return. They always do. The interesting question is who writes the new rules, who benefits from them, which ones are genuinely useful, and which ones are just fashionable superstition with a polished UI.

If natural-language computing inevitably creates new protocol layers, who should be allowed to write them?

Related reading:

Why Constraints Matter

Tue, 10 Feb 2026 00:00:00 +0000

Give a programmer unlimited resources and they’ll build a mess. Give them 640 KB and they’ll build something elegant.

Constraints force creativity. The demoscene proved that artistic expression thrives under extreme limitations. The same principle applies to web design: this site uses no JavaScript, and the CSS-only approach has led to solutions I would never have considered otherwise.

I have seen this pattern in codebases, hardware, writing, and product work: when limits are explicit, quality decisions become visible. You stop saying “we can optimize later” and start choosing what must be fast, simple, and stable right now. Constraints are not a prison. They are a filter.

Types of useful constraints

Not all limits are equal. Bad constraints are random bureaucracy. Good constraints are deliberate boundaries with a clear purpose:

time budget (ship in one week, cut scope aggressively)
resource budget (fixed RAM, battery, or CPU envelope)
interface budget (few options, clear defaults, no hidden state)
dependency budget (prefer fewer moving parts)

A tight budget often produces better architecture because you are forced to separate “core value” from “nice decoration.” In practice, this means fewer layers, stronger naming, and less accidental complexity.

Constraint-first design habit

Before building, I write down expected limits and expected outcomes. Then I test if the implementation actually behaves inside those limits. That small ritual catches wishful thinking early, especially in performance-sensitive or low-level work.

Related reading:

The Beauty of Plain Text

Mon, 14 Jul 2025 00:00:00 +0000

Plain text is the universal interface. Every tool can read it, every language can parse it, and it survives decades without bit rot.

Markdown, man pages, RFC documents, source code — the most durable artifacts in computing are all plain text. When everything else decays, ASCII endures.

What I like most is not nostalgia, but mechanical sympathy. Plain text works with the grain of the machine: streams, pipes, diffs, compression, version control, search indexes, backups, and even corrupted-file recovery. When data is text, you can inspect it with twenty different tools and still understand what changed with your own eyes.

Why it keeps winning

Text has a low activation energy. You do not need a heavy runtime or a vendor-specific UI to open it. If a future tool disappears, your notes do not disappear with it. If a process breaks, text logs remain readable in a terminal. If a teammate joins late, they can grep the repo and catch up.

That portability is not just convenience; it is risk reduction. Teams often overestimate feature-rich formats and underestimate operational longevity. A fancy binary store can feel productive right now and still become an incident in three years.

A practical workflow

For knowledge work, I keep a tiny stack: markdown notes, newline-delimited logs, and simple scripts that transform one text file into another. This gives me reproducible output with almost no tooling friction. When I need structure, I add conventions inside text first, then automate later.

Related reading: