Skip to content

The USA Stack

How The Local Internet is assembled across the United States.

One shared foundation. Many experiences. How is The Local Internet assembled across the United States?

TheLocalInternetStack.com

Defines the architecture.

The model

TheUSAStack.com

Shows that architecture operating across the United States.

The American implementation

The seven layers

The Stack explains architecture, not a universal lifecycle. Nothing is required to pass through every layer in order, and no object is copied to move between them.

  1. Surfaces

    Surfaces and experiences

    The experiences a person actually opens, each one a presentation of the shared system.

    • Geographic, discovery, business, information, offer, event, review and subject experiences
    • Deployed at their own addresses by one application
    TheLocalSurfaces.com
  2. Grid

    The Grid

    The connections that carry a governed object to every destination it legitimately belongs to.

    • Configured destinations in the Surface Registry
    • Placements connecting one object to many destinations
    • Geographic and subject distribution
    TheLocalGrid.com
  3. Workflows

    Operating workflows

    How those capabilities are actually run: the lifecycles, queues and rules applied the same way everywhere.

    • Record lifecycle from submission to publication
    • Claim and verification workflows
    • Review queues and approval
    • Expiration and effective dating
    TheLocalOS.com
  4. Platform

    Platform capabilities

    The shared capabilities every experience reads and writes through, rather than rebuilding.

    • Search and discovery
    • Publication
    • Owner management of a record
    • Promotion and featuring
    • Measurement
    TheLocalPlatform.com
  5. Governance

    Governance

    Who may change what, and why anything is published. Every placement records the reason it legitimately belongs where it appears.

    • Claiming and ownership
    • Verification and review
    • Publication basis recorded for each placement
    • Permissions and effective dates
    • Demonstration policy keeping non-production content out of public view
    TheLocalOS.com
  6. Shared Structure

    Shared structure

    The one geography, the one category system and the relationships and identity that let every object be found in context.

    • One geographic model: country, state, county, city
    • One category and subject model
    • Identity and duplicate resolution across records
    • Relationships between records, places and information
  7. Records

    Records and information

    The authoritative objects the system holds once: a business, a place, an organization, an article, an event, an offer, a review.

    • Business Records, held once and owned by the business
    • Places and organizations
    • Articles and guides
    • Events, offers and reviews
    OneBusinessRecord.com
  • No knowledge graph. The system holds reviewed relationships between records, and says only that.
  • No public API layer. One read-only feed of published Business Records exists; there is no write access of any kind.
  • No search, AI or agent layer. Nothing here answers questions, maintains records or acts on its own.
  • No citation, visibility or MCP infrastructure. Those capabilities do not exist in this system.

The geographic spine

One shared geographic structure, not four independent geographic databases. USAizz, Stateizz, Countyizz and Cityizz are four entry points into the same governed places.

National architecture is not national deployment.

The architecture is designed at the national level. The current deployment is intentionally sparse: a place, a destination and a publication only exist here when they actually exist in the running system. Nothing on this page implies coverage of every U.S. county, city or business.

Follow the Stack

Two real objects in the running system, shown moving through the architecture. If the system changes, this page changes with it.

Follow a Business Record

The article shows that the Stack distributes one object without copying it. The business record shows that the Stack is not merely an article-distribution architecture.

Explore the architecture

Each of these answers a different question. The USA Stack explains how they fit into the national implementation; it does not reproduce them.

National experiences

Stack, Grid, Network, Surfaces

Stack
Layers.
Grid
Distribution.
Network
Relationships.
Surfaces
Experiences.
USA Stack
The national implementation.

What this site is not

  • Not a second architecture. The layers shown here are the same layers TheLocalInternetStack defines.
  • Not a directory, marketplace or listings database.
  • Not a portfolio of domain names. Owning a name is not a capability.
  • Not a claim of nationwide coverage. What exists today is shown exactly as it is.
  • Not a copy of the discovery experiences. Countyizz, USAizz, TheUSAInformation and LocalInternetSearch keep their own jobs.