PLAZIR-27

The three-layer substrate

Every round is dynamic, and every round runs the same three layers. L1 is the judge — it orchestrates and works, and never blocks waiting on its specialists. L2 is the specialist layer — intermediaries that are also capable workers: they save reasoning by offloading it, spawn with cache to iterate on, and delegate execution outward through xask sub-calls. L3 is the crossbreeding lanes — outside models treated as fungible fuel. Models are commodities. Orchestration is the moat.

Round N — dynamic, every round
│
├─ L1  THE JUDGE      orchestrates AND works. never blocks on L2.
│
├─ L2  SPECIALISTS    intermediaries AND workers.
│      │              offload reasoning. cache-on-spawn. xask execution.
│      ├─ xask ok?  → L3 crossbreed, result cached
│      └─ xask dry? → do it locally. degrade, never die.
│
└─ L3  CROSSBREEDING LANES
       kimi · sol · ds-pro · ds-flash · qwen · grok
       fungible fuel. models are commodities.

The xask dry rule

Canaries are embedded in the logic itself, not bolted on after the fact. Any xask failure — timeout, usage limit, 403, empty reply — degrades the agent to local work instead of killing it; the specialist dispatcher is its own fallback. Failure is data, not disaster. There is no single point of substrate failure below L1. A round with all lanes down still completes — slower, dumber, honest.

Iterate cheap, in parallel

Move fast: L2 does not wait for L1 approval. Break things: every failure is telemetry, not a post-mortem. Iterate cheap: tiered delegation — never spend frontier-class reasoning where pattern matching suffices (canonical counterexample: a frontier western lab's top model, on high effort, taking 33 seconds to misread a denim tag). In parallel: fan-out is limited by ring depth, NVMe queues, and cgroups — never by sequential attention.

Cache-on-spawn

Specialists spawn warm, carrying context from prior rounds. Rounds compound instead of restarting. Nothing in the swarm pays to re-read what the swarm already knows. This is the difference between stateless function calls and an iterative workforce — and the reason self-improvement is affordable.

Substrate fungibility & pins

Pins — judge, review, execution, volume — are defaults chosen for the job, not cages. They are never moved by benchmark noise, and scores are never laundered across harnesses: a number from one eval rig never gets pinned onto another model's board. A substrate can be swapped; the topology stays.

The self-improvement loop

An orchestrator that audits codebases eventually audits itself — that is the point. Orchestrator bugs outrank target bugs: their blast radius is multiplicative. Convergence is the health signal — a full round where the judge accepts zero proposals is success, not stagnation. Honesty outranks progress theater. Friction is first-class data.

The wwkd posture

Data walk first. Skeleton before capability. Overfit one case, then generalize one axis at a time. Verification gate on every milestone. Code is ephemeral; knowledge is permanent. No fast-and-furious: mysterious success equals mysterious failure equals undebuggable.

Closing line

"Frontier is not a place. It is the practice of keeping this map true while everything underneath it changes."

When the map holds at full self-driving — lazy prompt in, verified system out, routes and lanes and delegations rewritten mid-run by the engine itself — that is escape velocity. That is ufo-fsd.