//The USA Deployment

The deployment layer of The USA Stack

The USA Deployment

From Architecture to Infrastructure.

A deployment architecture designed to turn namespaces, domains, nodes, templates, records, data and Surface Manifests into verifiable national-to-local digital infrastructure.

Open Deployment ConsoleExplore Deployment PipelineExplore The USA Stack
ARCHITECTURE / DEPLOYMENT PREVIEWNo automated production deployment engine is connected.
DEFINECONFIGUREBUILDDEPLOYVERIFYOBSERVEOPERATE

The primary question

How does the architecture become deployed infrastructure?

Stack

Design.

Deployment

Build.

OS

Operate.

define → configure → build → deploy → verify
$ usa deploy --target NODE-US-MN-DUL-014 --release REL-14
» resolve namespace     NS-GEO-US-MN-DULUTH        ok
» load configuration    CFG-CITY-MN v12            ok
» load template         TPL-CITY v8                ok
» load records          BR-88213, IR-11902         ok
» load graph context    GCTX-v6                    ok
» load surface manifest SMF-CITY-0042              ok
» validate                                         ok
» calculate plan        PLN-000184  5 change 1 add ok
» build                 REL-14                     ok
» approve release       policy:human-approval      ok
» deploy                SRF-US-MN-DUL-CITY-001     ok
» verify                15 checks                  preview
» receipt               RCP-000184                 issued
» handoff               THE USA OS                 observing

# architecture preview — command output is illustrative

Signature deployment pipeline

From strategic domain to operated surface instance

One chain of versioned objects connects a domain in the portfolio to a verified, observed digital experience registered in the Grid and the Graph.

  1. 01STRATEGIC DOMAINPortfolio asset
  2. 02NAMESPACEIdentity + purpose
  3. 03PURPOSEWhat it is for
  4. 04GEOGRAPHYNational → local
  5. 05NODEGrid position
  6. 06CONFIGURATIONVersioned settings
  7. 07TEMPLATEVersioned structure
  8. 08DATA / RECORDSBusiness + information
  9. 09GRAPH CONTEXTRelationships
  10. 10SURFACE MANIFESTExpression definition
  11. 11BUILDPackage a release
  12. 12DEPLOYChange state
  13. 13VERIFYEvidence required
  14. 14SURFACE INSTANCEThe deployed thing
  15. 15GRID + GRAPHRegister
  16. 16OBSERVEActual state
  17. 17USA OSOperate
INTENTPLANGOVERNEXECUTEPROVEOBSERVEOPERATE

Intent → Plan → Govern → Execute → Prove → Observe → Operate

  1. 01INTENTDeployment Manifest
  2. 02PLANDeployment Plan + Diff + Dependencies + Blast Radius
  3. 03GOVERNPolicy + Approval
  4. 04EXECUTEDeployment Record
  5. 05PROVEReceipt + Verification Evidence
  6. 06OBSERVEActual State
  7. 07OPERATEThe USA OS

Where deployment sits

Each layer of The USA Stack has one job

Deployment creates and updates deployed instances. It does not define the architecture, and it does not operate what it produced.

LayerRoleResponsibility
THE USA STACKDesignDefines the architecture.
THE USA PLATFORMParticipateProvides participation and management.
THE USA GRIDConnectDefines the network and where nodes exist.
THE USA GRAPHRelateDefines entities and relationships.
THE USA INFORMATIONInformStructures information in the network.
THE USA SURFACESExpressDefines where information is expressed.
THE USA DEPLOYMENTBuildCreates and updates deployed instances.
THE USA OSOperateObserves and operates deployed infrastructure.
THE USA INTERNETExperienceThe national-to-local experience.

Deployment at scale

One architecture. Many deployments. Many local experiences.

Reusable templates × structured records × geographic configuration × namespace definitions × graph context is what separates a system from building thousands of unrelated websites by hand.

One architecture

  • ×Reusable Templates
  • ×Structured Records
  • ×Geographic Configuration
  • ×Namespace Definitions
  • ×Graph Context

Many deployments

Deployment groups target node families — all state nodes, all Minnesota city nodes, a template family, a vertical, a domain cluster — with batched, canary or rolling strategies under policy.

Many local experiences

Each deployment produces a Surface Instance with identity, evidence and lineage, registered to the Grid and Graph and handed to The USA OS.

Build the System Once.

Configure It Locally.

Deploy It Repeatedly.

Architecture preview. This does not imply that portfolio domains have been automatically deployed.

Existing portfolio / network foundation

2,900+

strategic domains

100+

marketplace nodes

7,000,000+

existing listings

50 states

geographic domain networks

Multiple

deployed prototypes

These are Local Internet Holdings portfolio and network assets. They are not infrastructure currently controlled by The USA Deployment.

From Architecture to Infrastructure.

The USA Deployment is designed to transform namespaces, nodes, templates, records, data and Surface Manifests into verifiable national-to-local digital infrastructure.

DEFINECONFIGUREBUILDDEPLOYVERIFYOBSERVEOPERATE
Open Deployment ConsoleExplore The USA StackExplore The USA Internet