May 27, 2026

KaKeKiKoKu Studio is built on bounded blocks

The size caps are not a limit. They are the design.

People sometimes notice the size caps first. Sections in Studio stop at 4,000 characters. Every folder sidecar, file sidecar, and entity stops at 52,000 characters of prose. The first reaction is usually a small surprise: why not bigger?

The honest answer is that I could have made them bigger. The technology doesn’t care. The reason they exist where they exist is not technical. It is a design bet, and it is one of the things I am most convinced about in this whole project.

The bet

Knowledge that is useful to a human and to an AI fits in bounded atomic units. Walls of free-form text are not knowledge — they are material waiting to be organized. The moment you let a document grow without a shape, you start losing the ability to reason about it. You read it less, the AI reads it worse, and the signal hidden inside it dilutes.

Studio picks the opposite stance. Every piece of knowledge lives in a bounded block with its own identity:

• Every section and every subsection holds up to 4,000 characters.
• Every folder sidecar, file sidecar, and standalone entity holds up to 52,000 characters of prose.
• Every resource holds at most 30 top-level sections (including _description) and 60 subsections in total.

Inside those caps you compose freely. A section can hold subsections, each with its own budget; an entity can host many sections; a folder can describe a complex module without losing breath. The shape and the composition are finite on purpose, but flexible enough to model real projects.

The canary

The interesting part is what happens at the edge.

When a section refuses to fit in 4,000 characters, Studio does not negotiate. It does not raise the cap, ask for permission to expand, or quietly absorb the overflow. It refuses the write. The first reaction tends to be frustration: let me write what I need to write.

That refusal is the point.

If your knowledge does not fit in a block, the block is hiding two blocks. The plan needs splitting — not Studio.

I call this the canary. Every time it fires, it is telling me my own thinking was rushed. The section I tried to write is actually two sections. The entity I tried to grow is actually two topics. The folder sidecar that won’t close is trying to carry knowledge that belongs in its children. Almost without exception, the restructured version reads better than the version I was about to force in.

I did not expect this when I designed it. I assumed I would resent the limits. Instead I started to rely on them. The caps became something closer to a thinking partner: they tell me, with no diplomacy, when my mental model was sloppy.

The same idea, everywhere

Once you adopt the bet, it spreads. The size caps are the visible part, but the same principle shows up across the system:

The Markdown editor edits one block at a time. When you double-click on a section in the central viewer (KaKeKiKoKu Studio 1.5), you don’t open the whole resource — you open the section. You write inside its boundary, see its preview, save it, and close. The next block is a separate act. The atom is the unit of editing, not the document.

Relations point to blocks, not to words. A relation in Studio goes from one block to another block: section to subsection, description to section, subsection to subsection. There are no “link this paragraph to that paragraph” tricks, no “tag this word” gestures. If a connection is worth making, it is worth making at the level of an atomic unit with its own identity.

Images come in two flavors, and the difference is intentional. A Markdown image embedded inside a section is decoration — it illustrates the block that contains it, nothing more. An image with its own sidecar is a knowledge atom: it has a description, sections, relations, backlinks. The line between the two is exactly the line between “this belongs to a block” and “this is a block”. The same principle, projected onto images.

The left panel is becoming a navigator of blocks. In the next versions, Studio’s left panel stops listing files and starts listing the actual units of knowledge inside them: descriptions, sections, subsections. You navigate by atom, you connect by atom, you reason by atom.

Like Minecraft, but for AI reasoning

A friend told me the other day that Studio feels like the new Minecraft, but for AI reasoning. The line landed harder than I expected.

Minecraft works because the cube is the unit. Bounded, identical in nature, infinitely combinable. You don’t get to invent a half-cube to fit your particular wall — you adapt your wall to the cubes you have. And out of that constraint people have built castles, cities, working computers, entire universes. The cube is not the limit of Minecraft. It is what makes Minecraft possible.

Knowledge in Studio has the same shape. The block is the unit. You don’t extend it; you compose with it. And the consequence is the same: a finite shape that turns out to be the source of the expressiveness, not the obstacle to it. The discipline of the grid is what lets the thing get big.

I had not thought of it that way until that conversation. But I do now.

Why it works for an AI

An AI working with Studio receives the project as a map of bounded blocks with descriptions. It chooses which atoms to read in full, on demand. It writes inside one atom at a time. It compares two atoms when it needs to. Its context window is spent on what matters, not on swallowing 30,000 characters of prose to find the one paragraph that mattered.

That changes the quality of the reasoning. An atomic block is something the AI can hold in its head clearly. A 50-page document is something it can summarize, but not reason about with the same precision.

People sometimes ask whether Studio is just about saving tokens. It does save tokens, but that is a side effect. The real point is that bounded atoms preserve the shape of thought. The AI doesn’t just consume cheaper; it consumes better.

The discipline pays off

The first day with Studio, the caps feel like a wall. The second week, they feel like a hand on your shoulder. By the second month, you don’t notice them — because by then you already think in blocks.

That shift is the quiet outcome of the bet. You stop writing knowledge as if it were prose, and you start writing it as if it had structure, because it does. Your project becomes navigable. Your AI becomes useful in a new way. And the work you save in long conversations explaining context to your model is more than the discipline ever costs you.

Other tools optimize for unlimited writing. Studio optimizes for usable knowledge. Those are not the same thing, and the choice is on purpose.

If your plan doesn’t fit in a block, your plan needs splitting. Almost always, the split is the better plan.