The USA Grid
How One Local Internet is distributed across the United States.
One Record. Many Destinations.
See how one authoritative record can be distributed across many legitimate destinations in the American implementation of One Local Internet.
- Where is the American implementation distributed?
- Status is stated, never assumed.
- National architecture ≠ national deployment.
What is the Grid?
The Grid is governed distribution: one authoritative object, held in one place, appearing on many destinations because each appearance has a legitimate reason to exist. The model itself is defined by TheLocalGrid.com. This site does not restate it — it shows where that model has actually reached inside the United States.
TheLocalGrid.com
The Grid model itself.
Authoritative object
One record. There is only ever one, and it is never copied.
Legitimate placement
A recorded reason for that object to appear on a particular destination.
Configured destination
A destination the system knows and is able to publish to.
Public address
An address a visitor can open, where the experience is actually produced.
Follow the Grid
One real object in the running system, traced to the destinations it actually appears on. Every destination below is read live, and none is added to make the picture fuller.
One record is not twenty-three records.
When one article appears on twenty-three destinations, that is one authoritative article holding twenty-three destination-specific placements. Change the article and there is still one article. The Grid distributes placements; it does not manufacture duplicates, mirrors or separate independent records.
Nothing here is synchronized, replicated or pushed to a copy. An object is published to a destination, placed on it, and available at an address — those are the only claims this page makes.
Configured. Published. Public.
Configured, published and public are three different states and are never added together. A destination existing is not a destination carrying anything, and carrying something is not the same as a visitor being able to reach it.
Configured
The destination exists in the system and can be published to.
Published
Real content holds at least one legitimate placement there.
Public
A visitor can actually open the address and reach the experience.
This page does not count connected domains.
Whether a domain points here is held outside this application, so it cannot honestly be read as a live figure. A configured destination, a registered address, a publication or a past validation are none of them evidence that a domain resolves today. That has to be checked separately, and it is not claimed here.
Every surface listed here is deployed: this application resolves its address and serves its experience. The list is read from the running hostname resolver, so a name that is merely owned, registered or planned does not appear. What this page cannot check is whether each address is currently pointed at the application by its registrar — that is a domain connection, held outside the system, and it is not claimed here.
National architecture ≠ national deployment.
National reach here is assembled out of state, county and city destinations rather than announced from the top. The architecture for that assembly exists across all fifty states. The deployment does not, and this page says which is which every time it shows a number.
A national network built locally.
United States → State → County → City
One shared geography sits underneath all of it. USAizz, Stateizz, Countyizz and Cityizz are experiences over that shared model — none of them owns geography, and none of them holds a separate list of places.
Destination families
These are the real families the running system publishes to, shown as distribution patterns. This is not a list of owned names, and owning a name is not a destination.
Operation, then distribution
Why a placement is allowed to exist belongs to TheUSAOS.com. This page only asks where it ended up.
The OS establishes legitimate operation.
TheUSAOS.com
The Grid distributes the resulting placement.
Stack
What the implementation is made of.
Platform
What people can do.
OS
Why and how a publication legitimately operates.
Grid
Where that publication appears.
Network
How destinations relate to each other.
Surfaces
What people actually experience.
Explore the architecture
OneLocalGrid.com
Inventory — what is connected.
TheLocalGrid.com
Architecture — how the Grid fits together.
LocalGridNetwork.com
Relationships — how destinations relate to each other.
TheUSAStack.com
What the American implementation is made of.
TheUSAPlatform.com
What people and organizations can do.
TheUSAOS.com
How a publication is governed and operated.
TheLocalSurfaces.com
The experiences people can use.
USAizz.com
The national view of the shared geography.
Stateizz.com
State-level discovery.
Countyizz.com
County-level discovery.
Cityizz.com
City-level discovery.
What this site is not
- Not a second Grid model. The model is TheLocalGrid's; this is where it reaches inside the United States.
- Not an inventory. OneLocalGrid.com lists what is connected.
- Not a network topology. LocalGridNetwork.com explains how destinations relate.
- Not a surface catalogue. TheLocalSurfaces.com describes the experiences.
- Not a marketplace network, and not a directory of owned domain names.
- Not an API, not an AI system, not an agent layer and not a knowledge graph.
- Not a synchronization engine. Distribution is governed placement, not replication.
- Not a claim of national coverage. Most configured destinations carry nothing at all.