The Local Core · Capabilities & Demonstration
Connected infrastructure, not a collection of websites
The Local Core is the shared system behind every Local and USA site: one set of records, one geography, one review process and one approval history. Each capability below is labelled by what actually works today.
Capability scorecard
Read live with visitor-level access. No traffic, engagement, impressions or reach figures are shown because they are not validated.
17
capabilities
5
capabilities
5
capabilities
1
capabilities
3
Verified business records (public, non-demonstration)
…
Live publication destinations of those records — not network reach
126
Records currently classified as approved U.S. states, counties and cities (non-U.S. records excluded)
6
Operational workflows (4 complete, 2 partial)
Verified means a claim was approved through review by a different account from the one that submitted it; no one approves their own. Places count only listed U.S. records — pending places and non-U.S. records are excluded. Destinations are the sites where the verified records are currently published. Implemented means a capability works with real records. It does not mean it has been independently audited; no capability on this page has had an external audit.
Live demonstration
Explore a Real Business Record
See how one business connects to identity, places, verification, governance, distribution, and visibility.
Includes Northland Advertising LLC, which is affiliated with the platform owner and disclosed as such on the journey page.
Capability architecture
Choose a group. Owning or connecting a domain never, by itself, makes a capability Implemented.
The Local Infrastructure
ImplementedThe single shared system underneath every connected Local and USA site.
- Today:
- One backend, one set of records and one approval history serve all sites connected to this system.
- Evidence:
- Connected Local and USA surfaces read the same records and rules.
- Domain:
- thelocalinfrastructure.com
- Limitations:
- The explanation page describes the system; it is not a separate product.
The Local Database
ImplementedStores each business, organization, place and story once.
- Today:
- Records with access rules; visitors read only what is public.
- Evidence:
- Public pages use visitor-level reads; private fields stay restricted.
- Domain:
- thelocaldatabase.com
- Limitations:
- Some reference tables are intentionally public-read and recorded as approved exceptions.
The Local Graph
ImplementedApproved relationships between records and places.
- Today:
- Organization-to-organization and organization-to-place relationships.
- Evidence:
- Only approved relationships are public.
- Domain:
- thelocalgraph.com
- Limitations:
- The number of approved relationships is still small.
Local Internet Registry
ImplementedLooks up any record by its permanent public reference.
- Today:
- Public registry and Open Records pages.
- Evidence:
- Registry and Open Records pages are live.
- Domain:
- localinternetregistry.com
- Limitations:
- A separate Domain & Capability Registry is planned, not built.
The Local Grid
ImplementedA start page that organizes the network's properties.
- Today:
- Grid start page linking to connected properties.
- Evidence:
- Grid start page is live.
- Domain:
- thelocalgrid.com
- Limitations:
- A navigation view only; it holds no data of its own.
One shared core, two branded families
The Local and USA families read the same records, places and approvals. Each keeps its own branding and pages.
Local experiences
Public front door of the Local family; hosted separately from this system.
Served by the shared core; explains it (this site).
State, local and Informed sites served by the shared core, showing approved placements. Some owned domains are not connected.
Shared Core
- Business and organization records
- Identity and registry
- Geographic relationships
- Verification and governance
- Publication and distribution
- Search and navigation
USA experiences
TheUSAInternet.com
Planned national entrance. Not connected to the shared core and not served by it today.
Connected; served by the shared core.
Connected USA sites served by the shared core over the same records.
Explore How The Local Core Works
- 1
A business establishes its record
ImplementedThe business is added once and receives a permanent public reference.
- 2
Identity and geography connect
ImplementedThe record attaches to approved Census-based places and approved relationships.
- 3
Verification and governance decide what is supported
PilotClaims are approved by a different account from the submitting account. Account separation does not establish independent human review. Destination approval decides eligibility.
Partially implemented — the full eligibility rule is under validation.
- 4
Approved information reaches confirmed destinations
ImplementedRecords appear only on destinations with an approved, active placement.
- 5
Search and navigation help people find it
ImplementedPublic search and the Navigator lead to published information.
- 6
Measurement and intelligence provide insight
PilotOwner Intelligence offers rule-based guidance; audience measurement is not yet validated.
Partially implemented — no audience or engagement figures are shown.
No transactions are simulated. Steps marked Pilot work only in part.
Operational workflows
- Add a business or organization · Complete
- Claim a record with review by a separate account · Complete
- Editorial review and publication · Complete
- Destination-specific placement approval · Partial — The full publishing eligibility rule is still under validation.
- Manual placement withdrawal with permanent history · Complete — Automatic withdrawal is Blocked.
- Governed creation of new places · Partial — Non-U.S. addresses can still create mis-typed places; a correction is designed, not applied.