1. The network that rewrites itself

William Gibson’s Neuromancer returns because the image is exactly right: a dense network of consoles and intelligences finding paths through a global web without a central map. The desktop is not cyberspace, but its cells form a network with a similar need. If one link fails, if one cell disappears, if one new cell is inserted, the remaining cells must find a way to keep talking.

This entry wonders what it would mean if the desktop could reconfigure its own network topology.

2. The current assumption

So far the desktop has been imagined as a weak federation of cells. Each cell has identity, resources, and responsibilities. The network is planned on the ground: which cell talks to which, over which interface, with what failover. Reconfiguration is possible, but it is a ground-commanded event. A human or an uploaded script decides the new topology and pushes it down.

Self-reconfiguring network topology breaks that assumption. The cells themselves discover neighbors, evaluate link health, and choose new routes.

3. What changes

Self-reconfiguration would change several things:

  • Failure becomes a local event. A failed cell or cable is routed around before ground notices.
  • Insertion becomes plug-and-play. A new cell announces itself and is integrated automatically.
  • The network becomes harder to predict. Ground no longer holds the full routing table in advance.
  • The software burden shifts from configuration to policy. Instead of specifying routes, operators specify rules: what must never happen, what is preferred, what requires approval.

4. Why this is worth wondering about now

The desktop does not need self-reconfiguring networks on day one. But the interfaces and protocols chosen now will either support it or block it. If every cell has a fixed address and every route is hard-coded, autonomy becomes impossible. If the cells speak a discovery protocol and support multiple physical paths, autonomy becomes a software upgrade.

5. What this changes

  • Self-reconfiguring network topology is identified as a long-term capability, not an immediate requirement.
  • The wondering arc will explore what it changes, what it needs, and whether the desktop should design for it.
  • The next entry will look at the consequences in more detail.