---
title: "Yui"
date: 2026-05-12
url: https://www.blake.ist/posts/yui/
description: "Capability used to be hired. Capability is now conferred. A yui is the basic unit of that shift — a bound, identified, accountable AI worker."
---

# Yui

Capability used to be hired. Capability is now conferred. That is the transition the next decade is built on, and AI is finding its natural form inside it. Not the chatbot. Not the agent. Not the assistant. A unit that binds to a durable thing and acts on its behalf, under an identity granted by someone with the standing to grant it.

The unit needs a name. Call it a yui. One Japanese form, 結, carries the sense of tying, binding, linking — which is exactly what the thing does. Read as an acronym, it lands in the same place: Your Unit of Intelligence. The word belongs to someone. It binds to something. It is countable, addressable, and singular.

A yui is built from five primitives and an identity.

It has a model, which gives it intelligence. It has code, which gives it reach — anything a computer can do becomes available to the yui the moment it can write the program that does it. It senses — text, images, audio, video, telemetry — across live signals, historical archives, and forward projections. It has self-observation, which lets it read its own traces and improve on them. It has parallelization, which lets it search the space of possible answers instead of guessing at one. These five compound. A yui with code can call any API. A yui that can sense and call any API can ground itself in the world. Most of what we have been arguing about as "capabilities" are simply these five doing their job.

Identity is the sixth element, and it works differently. A yui can mint a key for itself. It cannot make the world honor it. Identity is conferred, not computed. Someone with standing grants the yui the right to act, the budget to spend, the scope to operate inside. Every yui is downstream of a human principal somewhere up the chain — or downstream of another yui that is.

This asymmetry is the whole game. The primitives are things the yui can do. The identity is something the yui must be given. A yui with primitives but no identity is a process running somewhere, anonymous and unclaimable. A yui with both is countable, addressable, auditable, revocable. That is the line between an experiment and a workforce.

Every durable entity gets one. Every role. Every application. Every program. Every team. Every device with a chip in it. Every mission with a budget. Yours runs against your calendar and your inbox. The team's runs against the team's work. The thermostat's runs against the thermostat. The launch's runs against the launch, and spawns more yuis for claims, channels, approvals, measurement, risk — each operating under inherited identity, each reporting back to the parent.

The org chart stops being a tree of people. It becomes a graph of bindings. Every node is shadowed by a yui acting on its behalf, at a clock speed humans cannot match. The yui for the launch coordinates with the yuis for regulatory. The yui bound to your calendar negotiates with the yui bound to mine. The yui in the thermostat talks to the yui in the meter.

The infrastructure is shipping. Local inference is cheap enough to put a yui in anything with a chip. Frontier inference is fast enough to put a yui on any problem worth solving. The dispatcher between the two is a near-term engineering problem. What is slow is the language. We have been trying to talk about the next decade of computing without a noun for its basic unit, and the absence of that noun is keeping people from seeing what is already here.

Capability used to be hired. Capability is now conferred. The constraint of the old era was headcount — how many people you could put on a problem. The constraint of the new era is standing — how many yuis you have the authority to instantiate and turn loose. Whoever decides who gets a yui decides how the work gets done.