The USA OS
How One Local Internet operates across the United States.
See how records, decisions, publication and governance operate across the American implementation of One Local Internet.
Platform = Participate.
The capabilities the system provides.
OS = Operate.
The rules, workflows and decisions that govern them.
TheLocalOS.com
Defines the operating model.
The operating model
TheUSAOS.com
Shows that operating model running across the United States.
The American implementation
Recorded state and governed decision
Nothing here watches the network and acts on its own. Something changes because a person with the authority to decide made a decision, and that decision was recorded: which object it concerned, what state existed, what was decided, what basis supported it, which destination it affected, and what history remains afterwards.
One system. Independent states.
A record is not one status. These are separate governed facts, and none of them implies another. An object can exist without being claimed, be claimed without being verified, be verified without being published anywhere, and be published without being promoted.
Exists
An authoritative record is held for this object.
Claimed
Someone asked to take responsibility, and that request was decided.
Verified
The information was checked and accepted by review.
Published
The object appears on a specific destination, for a recorded reason.
Promoted
A separate, separately approved arrangement is in effect.
- Record ≠ Claim
- Claim ≠ Verification
- Verification ≠ Publication
- Publication ≠ Promotion
- Publication ≠ Destination
- Destination ≠ Address
- Configured ≠ Published
Why is this published here?
A placement is not legitimate merely because it exists. Every placement carries at least one recorded reason, and a placement can rest on more than one reason at the same time.
Authoritative object
Placement on one destination
Publication basis
Reason A
Reason B
- One placement can hold Reason A and Reason B at the same time.
- If Reason A is revoked while Reason B still stands, the placement remains published.
- Only when no legitimate reason remains does publication cease.
This is not a description of an intention. The rule is enforced in the data: a placement is withdrawn when it no longer has a standing basis, not when a single reason is withdrawn.
What actually ends, and how
Promotion expiry
A promotion runs for a defined period and then ends.
Content expiry
Content that carries an end date stops being current at it.
Publication-reason revocation
A reason can be withdrawn; publication ends only when no reason remains.
Dated placement expiry is not currently operating. The end-date columns exist, but no placement carries an end date today, so this page does not claim that placements expire automatically by date.
Governed decisions
These figures are read from the running system when this page renders, and they appear only where a number demonstrates an operating rule. They are not a measure of network size — TheUSAStack.com owns the national deployment measurements.
Request ≠ Approval. A claim is a request, and someone other than the requester decides it.
Claimed does not mean verified. Verification is its own state, decided separately.
Publication ≠ Promotion, and paying for a promotion never decides it.
Product
A defined promotion product exists.
Request
An owner asks for it.
Credit where applicable
Where credit is used, it is held rather than spent.
Independent decision
Someone else approves or declines, and the decision is recorded.
Activation when approved
Only an approved request becomes a live promotion.
Expiry
The promotion ends at its defined end.
Not every request follows every step — credit applies only where credit is used, and a declined request never activates. Declines are part of the record, not an exception to it.
The operating workflows
Inherited from The Local OS, not redefined here. Each one already runs in production.
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
Follow the Workflow
Two real objects in the running system. Each state shown below is read from the system, and no missing history is filled in.
Decisions leave a history
Decisions leave a history. The system holds not only today's state but the evidence of how it came to exist.
National operating architecture is not national deployment.
The same operating rules apply at every level of the shared geography. The USA OS does not own that geography and does not add to it — and nothing here implies that every state, county or city is deployed.
Explore the system
Each of these answers a different question. The USA OS explains how the rules operate; it does not reproduce them.
Stack, Platform, OS, Grid, Network, Surfaces
- Stack
- Structure.
- Platform
- Capabilities.
- OS
- Operation.
- Grid
- Distribution.
- Network
- Relationships.
- Surfaces
- Experiences.
What this site is not
- Not a second operating system. The workflows shown here are the ones The Local OS already defines.
- Not an operations console. There is no health panel, node status, deployment status or synchronization here, because none of that exists in this system.
- Not an AI operating system and not an automation console. No agent detects anything, decides anything or acts on its own.
- Not an API platform. There is no write access of any kind, and no graph.
- Not a marketplace and not a portfolio of domain names. Owning a name is not a capability.
- Not a measure of network size. Numbers appear here only where they demonstrate an operating rule.