The infrastructure behind the Local Internet.

Architecture

Identity → Data → Relationships → Distribution → Surfaces → Discovery → Action

1. 1Identity
   LocalInternetRegistry.com

   Each business exists once as a Business Record, with Listed, Claimed and Verified as separate states. A public registry service built on these records is still developing.

   Operational foundation
2. 2Data
   TheLocalDatabase.com

   Locations, services, service areas, categories, offers, events and publications are structured facts attached to the record.

   Operational
3. 3Relationships
   TheLocalGraph.com

   Reviewed relationships between records, places, categories, organizations and content are stored today, in the same shared database. There is no separate graph database or graph engine.

   Operational foundation
4. 4Distribution
   TheLocalGrid.com

   Eligibility says where a record may appear; publication is a separate, reviewed decision. Nothing publishes automatically.

   Operational
5. 5Surfaces
   TheLocalSurfaces.com

   State, county, city and topic sites read the same record; none keeps a copy.

   Operational
6. 6Discovery
   TheLocalStart.com · LocalInternetSearch.com

   Task-first routing and search over published records.

   Operational
7. 7Action
   LocalBusinesses.ai

   Owners act in the Business Control Center; recommendations are deterministic and read-only.

   Operational

Operational:

Functioning in the current system.

Operational foundation:

The records and rules exist today; the broader capability is still developing.

Emerging:

Partly in place, not yet a complete capability.

Conceptual:

Future architecture, not implemented.

TheLocalCore.com — front door and system orientation.

Still developing

What exists today, and what does not yet

• Outside connectors — partner data can be brought in through a reviewed import today, but there are no live connectors or automatic syncs with outside systems.
• Public registry lookups — published records can be browsed and searched on public sites today, but there is no public registry service or open data access by record identifier.
• Relationship-chain querying — the system stores reviewed relationships today. It does not use a separate graph engine for arbitrary multi-hop relationship queries.
• Generative AI — not used. Owner recommendations today are deterministic rules over recorded activity and are read-only.

One system

• Core is the front door.
• Infrastructure explains the architecture.
• Platform provides the shared capabilities.
• Registry identifies it.
• Database describes it.
• Graph connects it.
• Grid distributes and connects it.
• Surfaces present it.
• Start and Search help people discover it.
• Business tools help owners act on it.

TheLocalCore.com is the system front door. These pages explain parts of the same system; they are not separate applications or separate databases.