The chain-producing machine
Three parts, one path.
Figure 23 — AI proposes, a human approves, the machine executes.
The console is where a chain is declared: name, currency unit, EVM identifier, validator count, and the switches. The AI layer takes a sentence of description and returns a structured blueprint with reasons and warnings. The operator takes the declaration and raises a real chain.
That order is the invariant part of the design. The blueprint carries reasons and warnings precisely so the approver has grounds to refuse; a proposal that does not state its own weaknesses cannot be approved, only believed or disbelieved. A system that lets AI raise infrastructure with the approval step removed is not bolder, it is merely unauditable.
The AI path is optional and may be absent: when the service is not configured, the interface says so clearly and the manual form works as usual. Alongside it comes a disclosure rule: anything not yet genuinely wired carries an illustrative label, and the label is only removed after end-to-end verification, not before.
Three gates of "self-service"
The phrase is used loosely in this industry, so here it is split into three levels with explicit conditions.
| Gate | Meaning | Requires |
|---|---|---|
| Per organisation | The operating team raises chains for customers on request | Operator and console suffice |
| Self-service with accounts | Outsiders raise their own chains | User accounts, and a requirement that every chain has an owner instead of a shared write permission |
| Per individual | Any person, one sentence, one chain | Additionally: cheap enough, and shared identity becomes a product |
In short: AI here is not a feature bolted on. It is the cheapest way to bring designing a chain below the threshold that requires an infrastructure engineer — without losing the person who is accountable.