You have owned several phones. Different makes, different models, different carriers. Your number is the same one you had years ago.

At some point — possibly without noticing — you moved from one carrier to another and kept the number. The new SIM arrived. You put it in the phone. Your contacts still reached you. Your bank’s two-factor codes still arrived. The number travelled with you, not with the carrier.

This is not obvious. For most of telecommunications history it was not possible. Your number was your carrier’s number, assigned by them, revoked when you left. Switching carrier meant losing your number — meant telling every contact, every service, every person who had ever called you that you had a new number. The migration tax was enormous. Many people paid above-market prices for years rather than face it.

Then number portability legislation arrived and changed the structure of the problem permanently.

The Two Layers

Your phone number is your semantic identity. It is the stable name that other people and other systems use to reach you. It is on your business card, in your contacts, tied to your bank, your delivery services, your two-factor authentication. It is you in a way your SIM card never was.

Your SIM card, your phone, and your carrier are the Gutenberg layer — the physical infrastructure that carries your identity. The SIM is a piece of hardware that encodes your connection to a specific network. The phone is a device that reads the SIM and connects to the network. The carrier is the infrastructure that routes the calls and the data.

These two layers — your semantic identity and the Gutenberg infrastructure — were coupled by default. The carrier assigned the number. The number lived in the carrier’s systems. When you left, the number stayed.

Number portability legislation forced a separation. The number became yours. The carrier became a replaceable infrastructure provider. The SIM changed. The phone changed. The number did not.

The External Resolver

What made this possible is an external resolver — a system that maps your semantic identity (the number) to the current Gutenberg address (which carrier’s infrastructure to route the call to) independently of either side.

When you port your number from one carrier to another, the external resolver is updated: this number now routes to this carrier. Every call to your number goes through the resolver first. The resolver looks up the current Gutenberg address and routes accordingly. The caller does not know or care which carrier you are using. They dial the number. The resolver handles the rest.

This is DNS for phone numbers. A hostname maps to an IP address via DNS. A phone number maps to a carrier’s infrastructure via the number portability resolver. The semantic identity is stable. The Gutenberg address can change. The resolver bridges them.

Without the external resolver, your number is locked to the carrier that issued it — the way a URI is locked to the system that minted it, with no DNS or redirect to fall back on. A URL has DNS underneath it and 30x redirects above it, so it is only partially locked — the host can change, the old URL can forward to the new one. An email address is locked to the provider that issues it in the same fuller sense: move providers and the address itself stops working, unless you own the domain. With the external resolver, the semantic identity travels freely across Gutenberg infrastructure. You move to the next iceberg. The number comes with you.

Moore’s Law Made the Media Transitions Inevitable

The same pattern — semantic identity surviving Gutenberg transitions — played out across every media format of the last forty years. But here Moore’s Law was the engine, not legislation.

CD → MP3 → iPod → Spotify. The music (semantic layer) never changed. Bohemian Rhapsody is the same performance on vinyl, CD, MP3, and Spotify stream. What changed was the Gutenberg carrier — and Moore’s Law kept making each successive carrier cheaper, smaller, and faster until the previous one became unnecessary.

  • CD: physical carrier, 700MB, required a disc drive, could not be searched or browsed at scale
  • MP3: format-free encoding, music separated from physical carrier, files on a hard drive
  • iPod: better Gutenberg device for the files — 1,000 songs in your pocket. The semantic layer (your music library) survived the hardware transition because the files were the resolver artifact, not the disc
  • Spotify: streaming bandwidth finally cheap enough that even the file became unnecessary. The Gutenberg layer (network infrastructure) crossed a threshold — fast enough, cheap enough, ubiquitous enough — that owning the local copy became optional

Each transition was a Gutenberg improvement crossing a threshold. The semantic layer (the music, the library, the taste) was portable across each transition because the format (MP3, AAC) was the external resolver — a stable encoding that any device could read, independent of the specific Gutenberg carrier it came from.

DVD → download → Netflix followed the same arc. Storage got cheap enough that downloading a film became practical. Then bandwidth got cheap enough that streaming became better than downloading. The film (semantic layer) never changed. The Gutenberg threshold kept moving.

Apple Understood the Interface Problem

Ten times as many songs needed a different interface. This is the insight Apple had that the record industry missed.

A CD collection of 500 albums was navigable by a human browsing a shelf. A digital library of 5,000 albums was not navigable by the same interface. The Gutenberg layer had changed (hard drives replaced shelves) but the semantic interface (browse, find, play) needed to change with it. The resolver between “I want to hear this” and “here is the audio” needed to be redesigned for the new scale.

iTunes and the iPod scroll wheel were that redesign. Not just a better CD player — a new resolver interface for a semantic layer that had scaled beyond what the old interface could handle.

Apple also forced the record industry to accept unit pricing per song and per album — a Use-Pull correction to the record industry’s Def-Push bundling model. The record industry had decided that the album was the semantic unit. Users had always known the song was. Apple made the resolver (iTunes Store) operate at the song level. The industry resisted and then accepted when the Use signal (sales) was unambiguous.

Then Spotify arrived with all-you-can-listen at the price of one album per month — the next threshold. When the Gutenberg layer (streaming infrastructure) became cheap enough, owning individual songs became unnecessary. The semantic layer (your taste, your library, your listening history) could travel without owning any Gutenberg artifacts at all.

Google did the same for the web. Ten times as many pages needed a different resolver. Yahoo’s directory was the right interface for thousands of pages. PageRank was the right resolver for billions. The web (semantic layer) stayed the same. The resolver had to scale.

Amazon did the same for retail and infrastructure. Prime abstracted the Gutenberg delivery cost behind a semantic membership. AWS abstracted the Gutenberg infrastructure (servers, networking, storage) behind semantic API calls. In both cases the resolver — the layer that maps semantic intent to Gutenberg execution — was redesigned for a scale the old model could not handle.

What Still Does Not Have a Resolver

The phone number has one. The music file format was one. But many semantic identities are still locked to their Gutenberg carriers.

Your music library. Your Spotify playlist does not port to Apple Music. Your listening history, your liked songs, your curated playlists — all locked to Spotify’s infrastructure. The songs themselves are available on both platforms. The semantic layer (your relationship with the music, your taste as expressed in years of listening) has no external resolver. Switch platforms and start over.

Your bank account number. IBAN standardised the format. It did not deliver portability. Switch banks and your account number changes. Every direct debit, every salary payment, every standing order must be updated. The number portability model that transformed mobile telecoms has not been applied to retail banking — not for technical reasons but because the banking lobby has successfully resisted it.

Your social graph. Your followers on one platform do not follow you on another. The connections — the semantic layer of who knows you and who you follow — are locked to each platform’s infrastructure. ActivityPub is the attempt to build the external resolver for social identity, making the handle (@rinie@mastodon.social) portable across implementations. Adoption is growing but slowly.

Your game progress. Your save files may or may not survive a console generation. The semantic investment (the hours, the achievements, the story progress) has no guaranteed resolver across hardware transitions. Xbox backward compatibility is the closest thing to one.

In each case the pattern is the same. The Gutenberg layer keeps improving — better streaming, better hardware, better infrastructure. The semantic layer (your identity, your history, your relationships) wants to travel. The missing piece is the external resolver that separates the two.

The Resolver Is the Infrastructure of Freedom

Number portability did not arrive because carriers wanted it. It arrived because regulators mandated it — because the market would not deliver the external resolver voluntarily when carriers benefited from the coupling.

The general lesson: wherever the Gutenberg layer is improving but the semantic layer is locked to an old carrier, the missing piece is an external resolver. Sometimes the market builds it (iTunes, Spotify, AWS). Sometimes regulation mandates it (number portability, EU roaming). Sometimes it is still missing (bank account portability, social graph portability, music library portability).

Your next phone will be a different make on a different carrier. Your number will not change. That transition is seamless because someone built — and legislation mandated — the external resolver that made it possible.

The same transition should be seamless for your bank account, your music library, your social graph, and your game progress. The Gutenberg layer is already good enough. The resolver is what is missing.

This post is part of the Gutenberg/Semantic series. Related: Your Music Survived Six Formats on semantic identity versus Gutenberg carrier, Your Email Address Is Hostage on building your own resolver, and UUIDs Are Not Names on why the resolver must be external.