What arrives

A layer everyone runs on, held by one builder. Compute, connectivity, payment, identity, a model that every service calls: each can become a place where one person or a small circle decides who may use it. The builder may have earned it fairly. The problem is not the success; it is that access can be withdrawn at will and there is nowhere else to go.

What must exist first

Essential-layer duties, and a second provider able to connect.

  1. The three tests, published. Dependence, no route-around, and personal discretion, applied by rule, so a layer knows when duties attach.
  2. Four duties. Access by rule, continuity, open interfaces so a second provider can connect, and no turning the layer into a public authority.
  3. Attachment at renewal. Duties added when the public inputs the layer depends on come up for renewal, not by seizure.
  4. A second provider. Public or private, kept able to carry real load (routability).
  5. The builder keeps the company. Title, returns, and operating decisions stay with the builder.

Why it is cheaper first

Building an alternative after lock-in means competing with what everyone uses. Open interfaces cost little to require while a layer is young and several builders compete. Once one has won, every service, habit, and contract is built around its particular design, and a second provider starts from nothing. Duties attached early are a condition of growth; duties attached late look like punishment.

Readiness states

State What it looks like
Started essential-layer tests written into law; open-interface requirements on a first layer
In place duties attached at renewal for each qualifying layer; a second provider connected
Tested a provider outage or withdrawal survived by switching to the second provider

What to start now

List the layers that already pass two of the three tests. Require open interfaces in public procurement now. Fund or keep a second provider for each layer public services depend on.

Where it is worked out