Skip to main content

​
The Literacy of AI Era

Every technological era introduces a structural pattern. Those who understand it build the systems. Those who don’t, use them.

​
The Pattern of Each Era

Each transition felt overwhelming at the time. Then it became obvious. “Files and folders” was once a new concept. Now five-year-olds understand it. “Client-server” was once specialized knowledge. Now it’s a whiteboard interview question. “Containers and Kubernetes” was once DevOps magic. Now it’s infrastructure 101. “AI organizing AI” is the next one. It feels new now. It will feel obvious soon. The question is whether you understand it before or after it becomes standard.

​
What Changed in 2025

Before 2025, AI was a tool. You talked to one AI. It helped you.
Simple. One direction. One layer. The literacy was prompting — how to ask clearly. After 2025, AI became a network. AIs talk to AIs. They form teams. They spawn sub-teams. They operate across machines.
The literacy is no longer “how to talk to AI.” It’s “how AI talks to AI, and how to design that conversation.”

​
The Two Levels of Understanding

​
Level 1: User

You don’t need to know that 15 agents across 3 machines worked on it. You don’t need to know that research was parallel and implementation was sequential. You don’t need to know that one agent spawned its own sub-team. This is fine. This is using a car without understanding the engine. Most people will stay here. That’s okay.

​
Level 2: Designer

This is designing the engine. You need to understand:
  • Parallel vs sequential: when to fan out, when to converge
  • Model routing: which AI for which task, and why
  • Isolation: worktree for file safety, sandbox for process safety
  • Recursion: when a worker should become an orchestrator
  • Distribution: which machine for which workload
  • Failure: what happens when a provider goes down
This is the ASURA-SENJU pattern. This is the literacy.

​
The Fractal

The core insight is recursive:
This is a fractal. The same pattern at every level. Once you see it, you see it everywhere:
  • A company CEO delegates to VPs. VPs delegate to managers. Managers delegate to engineers.
  • A conductor leads sections. Section leaders lead musicians. Each musician interprets their part.
  • A function calls functions. Those functions call functions. Each function has its own scope.
The AI version:
  • An ASURA dispatches SENJU workers. Workers become ASURAs. They dispatch their own workers.
The pattern is always the same. The depth changes. Understanding this fractal means you can design AI systems at any depth. Without understanding it, you’re stuck at depth 1 — one AI doing one thing.

​
What the Literate Person Sees

An illiterate person sees:
A literate person sees:
Both got the same result. One understands what happened. The other doesn’t. The one who understands can:
  • Optimize the pipeline (fewer workers where it doesn’t help)
  • Debug failures (which phase broke, which agent failed)
  • Design new pipelines for new problems
  • Teach others to do the same

​
The Vocabulary

Like every literacy, this one has vocabulary: You don’t need all of these to start. “ASURA orchestrates, SENJU executes, any SENJU can become ASURA” covers 80% of it.

​
Where to Start

Each step is a connector.json. Each step builds on the previous. The tool teaches the literacy.

​
The Bet

Every era’s literacy seemed optional at first and essential in retrospect.
This is the bet connector.json is making. Not that everyone will need this literacy — but that everyone who builds with AI will.