Skip to content
THE LOCAL GRIDHow the Local Grid fits together.

The Local Grid · part of One Local Internet

HOW DOES THE LOCAL GRID FIT TOGETHER?

The Local Grid connects shared records and information to many local experiences across geography, subjects and specialized destinations.

One Record. One System. Many Surfaces.

WHAT THE GRID IS NOT

Domains are addresses into experiences. The Grid is the architecture that lets shared records, information and capabilities reach those experiences.

Not a separate internet

The Grid is part of One Local Internet, not a parallel one.

Not a collection of independent websites

The experiences are surfaces over one shared system, not sites maintained one by one.

Not a separate database

No record is recreated to appear somewhere. There is one record layer.

Not a domain portfolio

Domains are addresses into experiences. The Grid is the architecture that lets shared records reach them.

THE ARCHITECTURE

Read top to bottom. Each layer does one job, and none of them duplicates another.

  1. Layer 1Authoritative records and information

    A business, place, article, offer or event, held once.

  2. Layer 2Shared platform

    The capabilities every experience reads and writes through.

  3. Layer 3Operating rules and workflows

    Claiming, verification, review and publication, governed the same way everywhere.

  4. Layer 4The Local Grid

    The connections that carry a governed record to the places it legitimately belongs.

  5. Layer 5Local surfaces

    The experiences a person actually opens.

  6. Layer 6People and businesses

    Someone finds the business; the business manages one record.

ONE RECORD, MANY SURFACES

  1. Step 1
    One Record

    Authoritative, held once, owned by the business.

  2. Step 2
    Governed publication

    Each placement records the reason it legitimately belongs there.

  3. Step 3
    The Local Grid

    The connection between the record and the destination.

  4. Step 4
    Many legitimate surfaces

    The same record, presented in each context.

An authoritative Business Record is not recreated for every site, and an Event, Offer or Article does not need another database row merely because it appears elsewhere. A surface is never on its own a reason to publish something.

Conceptual illustration, not production data. No business, count or placement below is read from the system.

One Business Record
  • A state surface
  • A city surface
  • A storefront surface
  • A business discovery surface
  • A subject surface

Still one Business Record.

FOLLOW SOMETHING THROUGH THE GRID

Choose an authoritative object and see the kinds of surface it can legitimately reach. The surfaces named are read from the same running system TheLocalSurfaces catalogues, and are representative rather than exhaustive.

One authoritative record, claimed and verified by the business.

Held once
A Business Record
Through
Governed publication → the Grid

Each placement records the reason it belongs there.

Reaches
5 kinds of surface
Geographic surfaces
Business and storefront surfaces
Discovery surfaces
Subject and intent surfaces
Featured and promotional surfaces

The full list of experiences lives on TheLocalSurfaces.com, not here.

HOW IT EXPANDS GEOGRAPHICALLY

  1. Level 1
    United States

    National discovery.

  2. Level 2
    States

    State discovery.

  3. Level 3
    Cities and regions

    City discovery.

  4. Level 4
    Local experiences

    What is actually near someone.

Geography is held once, by the existing place system. The Grid does not define states, counties or cities, and no experience here holds a geography of its own.

INFORMATION ON THE GRID

  1. Step 1
    Authoritative article or guide

    Written once, held once.

  2. Step 2
    Publication

    Recorded with the reason it belongs on a destination.

  3. Step 3
    The Local Grid

    Carries it to the destinations it was published to.

  4. Step 4
    Information surfaces

    TheLocalInformation and other legitimate information experiences.

The information itself lives on TheLocalInformation.com and the other information surfaces — never duplicated here.

WHAT THE NETWORK ACTUALLY MEASURES

Deployed addresses
402

Hostnames this application resolves and serves, including www forms and alternate names for the same experience.

Deployed surfaces
377

Distinct experiences behind those addresses. Several addresses can share one.

User-facing surfaces
354

Deployed surfaces that present records to people, excluding explanation and routing pages such as this one.

Surface kinds
10

Categories of experience the shared system currently powers.

Configured destinations
284

Rows in the Surface Registry — places a record can legitimately be published to. Some deployed surfaces are ways in and hold no registry row.

Externally DNS-verified domains
Not measured

Not measured. Whether a registrar currently points a name at this application is held outside the system, so it is not counted or inferred here.

Every figure above is counted from the running system when this page rendered, and each says what it counts. A configured destination is not evidence that a domain resolves here, and an owned name is not evidence that anything is deployed.

Strategic name

Held in the namespace, not deployed. Not part of the Grid until it is.

Configured destination

A registry row a record can be published to. Configured does not mean its registrar currently points here.

Deployed surface

An experience this application serves at its own address.

EACH LAYER HAS ONE JOB

  1. Step 1
    Namespace

    Defines roles.

  2. Step 2
    Platform + OS

    Provide capabilities and operating rules.

  3. Step 3
    Grid

    Connects deployment.

  4. Step 4
    Surfaces

    Deliver experiences.

The Namespace Company

Why do these names exist and what role does each hold?

The Local Platform

What capabilities does the system provide?

The Local OS

How are those capabilities governed and operated?

The Local Grid

How does the Local Grid fit together?

One Local Grid

What is connected?

The Local Surfaces

What user-facing experiences exist?

One Local Internet

What is the ecosystem these belong to?

An authoritative object may legitimately appear on several surfaces. Which URL, domain or surface should be canonical for indexing is still an open policy question, and the Grid does not decide it.

CARRIED FORWARD

Retained

The Grid is a set of relationships, not a collection of domains

Retained — it is the correct idea and it is now the whole page.

One data layer, shared services, many surfaces

Retained, and it is the production architecture rather than a diagram.

Geographic architecture repeating from national to local

Retained, pointing at the existing geography rather than a new one.

The Local Grid explains the network; One Local Grid explains one business's place in it

Retained, sharpened, and now tested.

Not carried forward

2,900+ strategic domains, 100+ marketplace nodes, 7M+ existing listings

Internal inventory figures from a separate site. Nothing here can verify them, so they are not published as network facts.

Seven named grids, including a Visibility Grid and an Agentic Grid

APIs, MCP endpoints, agents and machine-to-machine discovery are not operating capabilities of this system today.

The Listing → Presence → Visibility → Business Record progression and its scores

Not the record model that runs here, and no visibility or record score exists. Records are claimed, verified and published.

Marketplace nodes as a network class

The current destination model has no marketplace object. Subject and intent surfaces are the honest equivalent, and they are catalogued by TheLocalSurfaces.

Corporate portfolio, sale, lease and licensing messaging

Local Internet Holdings may be named as the company behind the ecosystem; this page's job is explaining the Grid.

WHERE THIS SITS

How does the Local Grid fit together? is the only question this page answers. One Local Internet is the ecosystem the Grid belongs to.

OneLocalInternet.comOneLocalGrid.com — what is connectedTheLocalSurfaces.com — the catalogTheNamespaceCompany.com