How We Work
Question → Architecture → Prototype → Experiment → Learn → Build → Deploy. A method for exploring ideas before they become products or infrastructure.
Question
Start with a fundamental question.
Architecture
Design a potential system.
Prototype
Make the idea visible.
Experiment
Test assumptions.
Learn
Document what works and what doesn't.
Build
Develop promising concepts further.
Deploy
Move mature ideas into the broader Local Internet ecosystem.
Local Entity → Action
The central flow each experiment tests a layer of, with the prototypes exploring it.
- 01 — Local entity
- 02 — Business Record
- 03 — Local Graph
- 04 — Citable information
- 05 — Visibility
- 06 — Machine access / MCP
- 07 — AI agent
- 08 — Action
- Geography
- Publishing
- Marketplaces
- Local surfaces
- Business operations
- Structured data
- Citations
From Listings to Records
What Could 7 Million Self-Placed Listings Become?
These are not 7 million verified Business Records.
The research question is what could happen if existing listing information could progressively become more structured, claimable, verifiable, connected and machine-readable.
None of the problems beside these stages are solved. They are the research agenda.
- 7M+ self-placed listingsWhat is actually in the data?
- NormalizeWhat information can be normalized?
- Entity resolutionHow accurately can duplicate entities be resolved?
- StructureWhat structure is worth imposing before verification?
- ClaimWhat information requires owner verification?
- VerifyWhat makes a Business Record authoritative?
- EnrichWhat information should AI be allowed to infer?
- Business RecordHow should provenance be recorded?
- Local GraphHow should conflicting information be handled?
- Local surfacesHow should freshness be measured?
- Search + AI + agentsWhat should remain human-controlled?
A Real Network to Experiment With
Local Internet Holdings already operates a network of marketplace and local discovery properties. That existing network creates a potential testbed for exploring structured listings, Business Records, entity relationships, geographic discovery, publishing and machine-readable local information.
The environment exists. It is described here as a potential experimental environment, not as work already carried out across the network.
Domains as Nodes
Can strategically organized domains become functional endpoints inside a larger information architecture?
Domain → Node → Network → Infrastructure
2,900+ strategic domains is an owner-provided portfolio metric. It does not imply that every domain is deployed, developed or in use.
- Domain
- Specialized purpose
- Structured data
- Shared entity model
- Connected graph
- Network node
- Human + machine experience
How We Think
- 01Separate hypothesis from evidence.
- 02Prototype before overbuilding.
- 03Make architecture visible.
- 04Document what doesn't work.
- 05Keep humans in control of authoritative business information.
- 06Distinguish structured facts from AI inference.
- 07Treat geography as context, not just navigation.
- 08Build for people and machines.
- 09Don't confuse deployment with validation.
- 10Ask better questions before claiming answers.
Where the Lab Sits in the Ecosystem
This is conceptual architecture. It does not describe a legal corporate structure beyond what has been established.
- 01 — OwnLocal Internet Holdings
- 02 — ExploreLocal Internet Labs
- 03 — TestPrototypes
- 04 — ServeLocal Internet Group
- 05 — OperateThe Local Engine
- 06 — ConnectThe Local Graph
- 07 — InfrastructureThe Local Grid
- 08 — DistributeLocal Grid Network
- 09 — DiscoverThe Local Internet