The Local OS
HOW THE LOCAL INTERNET OPERATES.
The operating layer of The Local Internet: the record lifecycle, claim and review workflows, verification, publication decisions and basis, placement lifecycle, promotion workflows, permissions and governance that run every surface on the network.
The Local OS owns no business data. It is the set of rules and workflows that decide what happens to a record, who may act on it, where it may appear, and when that ends.
PLATFORM AND OS
What capabilities does The Local Internet provide?
Records, geography, publication, discovery, claims, verification, promotion, search and local experiences.
How does The Local Internet operate those capabilities together?
The lifecycles, workflows, rules and governance that decide what happens to a record, who may act on it, where it may appear and when that ends.
One system, two readings. The platform is the set of capabilities; the OS is how those capabilities are operated together. Neither is a separate database.
THE OPERATING LOOP
One authoritative record exists.
Someone claims responsibility for it.
Another party decides, with a recorded reason.
A basis is recorded and a placement is made.
Surfaces present it where it belongs.
Placements and promotions end on a defined date.
One Record. One System. Many Surfaces. The loop runs on the same record every time — nothing is duplicated to move it through a workflow.
WHAT THE OS OPERATES
Each workflow below already runs in production. Every link opens the experience that implements it.
Record lifecycle
One authoritative Business Record moves through defined states. It is never copied to create a second version of the same business.
- Created
- →Pending review
- →Reviewed
- →Published
- →Maintained
Claim workflow
An owner asks to take responsibility for an existing record. Claiming is a request, not a grant — management rights follow the decision, not the request.
- Claim submitted
- →Evidence recorded
- →Independent review
- →Approved or declined
Review workflow
Claims, records, content and promotion requests are reviewed independently. No one approves their own submission.
- Submitted
- →Queued
- →Reviewed by another party
- →Decision recorded with reason
Verification
Verification is a separate step from claiming and is never granted automatically. A record can be claimed without being verified.
- Listed
- →Claimed
- →Verified
Publication decisions and basis
Nothing is published because a category or a state matched. Every publication carries a recorded basis explaining why that record legitimately belongs on that destination.
- Eligibility assessed
- →Basis recorded
- →Decision made
- →Published or refused
Placement lifecycle and expiration
A placement is a relationship with a beginning and an end. Placements end on a defined date rather than lingering indefinitely.
- Placed
- →Active
- →End date reached
- →Ended
Promotion workflow
Promotion is requested, reviewed independently and then runs for a defined period. Paying for a promotion never bypasses review.
- Requested
- →Credit held
- →Independent review
- →Approved or declined
- →Runs
- →Ends
Permissions
Who may read, edit, publish or promote a record is decided by the record's own ownership and membership — enforced in the data, not in the interface.
- Visitor
- →Signed-in user
- →Owner of a claimed record
- →Reviewer
Governance and provenance
Decisions are recorded with a reason and kept. Where information came from, and who decided what, stays inspectable.
- Action taken
- →Reason recorded
- →History retained
- →Inspectable
Destination rules
Each destination defines what it carries — geography, subject, kind of content. A record appears there only when it satisfies those rules.
- Destination defines scope
- →Record assessed against it
- →Placement allowed or refused
Surface delivery
The same record is presented differently on a state site, a city page, a subject site or a search result. Presentation varies; the record does not.
- Record
- →Placement
- →Surface presentation
- →Consumer discovery
NATIONAL TO LOCAL
Geographic discovery is one shared geography read by many surfaces — not independent directories, and never a reason on its own to publish a record.
CARRIED FORWARD
The earlier Local OS site described a national-to-local information network built from structured records. That idea was right and is now the production architecture.
National → State → County → City
Retained, and already running: USAizz, Stateizz and Cityizz open the same shared geography, down to county and city pages.
Information exists as structured records; pages are generated from them
Retained, and the founding rule here: one record, one system, many surfaces. No page holds its own copy.
The operating system for local
Retained as the role of this address — the operating layer, not a separate product with its own data.
Sections of that earlier site that were demonstration content without a production system behind them are not carried forward. What is shown here is what actually runs.
WHERE THE OS SITS
- The Local InternetThe overall ecosystem.
- OneBusinessRecord.comAuthoritative records and identity.
- TheLocalPlatform.comShared platform capabilities.
- TheLocalOS.comOperating workflows, rules and orchestration.You are here
- OneLocalGrid.comThe connected network of destinations and surfaces.
- TheNamespaceCompany.comHow the domains themselves are organized into named roles.
- USAizz → Stateizz → CityizzGeographic discovery over the same records.
This is a way of reading one architecture, not six systems. Business owners who want to find, claim and manage their own record can do that at OneLocalPlatform.com.