//The USA Deployment

Deployment plan

Know What Will Change Before It Changes.

A manifest states desired state. A plan states the difference between current state and desired state — the objects to add, change, remove or leave alone, their dependencies, and the blast radius of executing them.

ARCHITECTURE / DEPLOYMENT PREVIEW

Manifest → plan → deployment

Desired state is not a change set

  1. 01CURRENT STATEWhat exists now
  2. 02DESIRED STATE / DEPLOYMENT MANIFESTWhat should exist
  3. 03CALCULATE PLANDifference between the two
  4. 04DEPLOYMENT PLANThe changes required
  5. 05APPROVALApprove what will change
  6. 06DEPLOYMENTExecute the plan

Deployment plan

The Manifest describes the desired state. The Plan describes the changes required to move from the current state to the desired state.

plan_id
PLN-CITY-MN-DUL-0044
deployment_manifest_id
DMF-CITY-MN-DUL-0031
current_release
REL-13
desired_release
REL-14
objects_to_add
1 — Information Record binding IR-11902
objects_to_change
5 — template · configuration · graph context · surface manifest · release
objects_to_remove
0
objects_unchanged
2 — Business Record BR-88213 · Grid Node NODE-US-MN-DUL-014
template_changes
TPL-CITY v7 → v8
configuration_changes
CFG-CITY-MN v11 → v12
surface_changes
SMF-CITY-0042 v3 → v4
record_dependencies
BR-88213 · BR-88214 · IR-11902
graph_changes
GCTX-v5 → v6 · 1 new relationship
grid_changes
none — node already registered
namespace_changes
none — NS-GEO-US-MN-DULUTH unchanged
dependencies
13 declared dependency types
deployment_group
MN-CITY-NODES
rollback_target
REL-13
approval_requirement
HUMAN APPROVAL REQUIRED
risk_level
MODERATE
status
PREVIEW

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

Deployment diff

What Will Change?

Every planned object is shown with its current value, its desired value and the action required.

What will change?
ObjectCurrentDesiredAction
Templatev7v8CHANGE
Configurationv11v12CHANGE
Business Recordv14v14NO CHANGE
Information RecordabsentIR-11902ADD
Graph Contextv5v6CHANGE
Surface Manifestv3v4CHANGE
Surface InstanceExistingExistingVERIFY
Grid NodeExistingExistingNO CHANGE
ReleaseREL-13REL-14CHANGE
ActionsADDCHANGEREMOVENO CHANGERECREATEVERIFY

Dependency analysis

A deployment should know what it depends on before it runs

Dependencies are declared, resolved and checked before execution. Anything unresolved stops the plan.

Dependencies — what a deployment must know before it runs
DependencyExampleState
DomainCityizz.comPREVIEW
NamespaceNS-GEO-US-MN-DULUTHPREVIEW
Grid NodeNODE-US-MN-DUL-014PREVIEW
TemplateTPL-CITY v8PREVIEW
ConfigurationCFG-CITY-MN v12PREVIEW
Business RecordsBR-88213 · BR-88214DATA PENDING
Information RecordsIR-11902DATA PENDING
Graph ContextGCTX-v6PREVIEW
Surface ManifestSMF-CITY-0042PREVIEW
APIDeployment APIAPI PENDING
MarketplaceOutdoor Recreation nodeNOT CONNECTED
PublisherPublisher networkNOT CONNECTED
SearchSearch registrationPREVIEW
AI InterfaceAgent access policyNOT CONNECTED
Other deploymentsMN-CITY-NODES group membersPREVIEW

Blast radius

What Could This Change Affect?

A template change is rarely local. Blast radius describes the direct target, the deployment group and everything downstream that could be touched.

What could this change affect?

change
TPL-CITY v8
direct target
Duluth City Node
deployment group
MN-CITY-NODES
assessment
MODERATE
ScaleLIMITEDMODERATEWIDEUNKNOWN

These are architecture labels for dependency-aware deployment planning, not authoritative risk values.

Potentially affected
ObjectScopeState
Grid Nodes1PREVIEW
Surface Instances14PREVIEW
Business Records used by those surfacesUNKNOWNDATA PENDING
Graph relationshipsUNKNOWNPREVIEW
Marketplace relationshipsUNKNOWNNOT CONNECTED
Search surfacesUNKNOWNPREVIEW
Information routingUNKNOWNPREVIEW
USA OS observationsUNKNOWNNOT CONNECTED

Canary deployment

Test Small. Verify. Scale.

Dependency analysis and blast radius choose the canary target. Only verified, observed health expands the deployment group.

  1. 01CHANGEA new template or configuration version
  2. 02DEPENDENCY ANALYSISWhat does this depend on?
  3. 03BLAST RADIUSWhat could this affect?
  4. 04CANARY TARGETOne node first
  5. 05DEPLOYExecute the plan
  6. 06VERIFYEvidence required
  7. 07OBSERVEActual state
  8. 08HEALTHY?YES → expand group · NO → stop / review / rollback

Healthy?

YES → EXPAND DEPLOYMENT GROUP

NO → STOP / REVIEW / ROLLBACK

CHANGECANARYVERIFYOBSERVEEXPAND

Governance

Approve What Will Change

Approval is scoped to known objects, not to an abstract deployment.

Approve what will change
Approved objectValueMeaning
Deployment ManifestDMF-CITY-MN-DUL-0031Desired state
Deployment PlanPLN-CITY-MN-DUL-0044Required changes
Change Set5 change · 1 add · 2 no changeWhat will change
Blast RadiusMODERATEWhat could be affected
Rollback TargetREL-13Previous known-good release
Verification Policy15 checks requiredWhat must be proven

Approval does not approve “a deployment.” It approves a known manifest, plan, change set, blast radius, rollback target and verification policy.

Post-deployment change result

Planned vs Executed

What was expected to change, what actually changed, and what was subsequently observed.

PLANEXECUTEOBSERVE
Planned vs executed
ObjectPlanExecutionObservationResult
Templatev7 → v8v7 → v8v8PREVIEW · MATCHED PLAN
Configurationv11 → v12v11 → v12v12PREVIEW · MATCHED PLAN
Information RecordADD IR-11902ADD IR-11902presentPREVIEW · MATCHED PLAN
Graph Contextv5 → v6v5 → v6v6PREVIEW · MATCHED PLAN
Surface Manifestv3 → v4v3 → v4v4PREVIEW · MATCHED PLAN
ReleaseREL-13 → REL-14REL-13 → REL-14REL-14PREVIEW · MATCHED PLAN
Grid NodeNO CHANGENO CHANGEregisteredPREVIEW
Possible resultsMATCHED PLANPARTIALUNEXPECTED CHANGEFAILEDDRIFT DETECTEDPREVIEW

Planned, executed and observed values are architecture examples. No execution engine or observation runner is connected.

Canonical deployment model

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

INTENTPLANGOVERNEXECUTEPROVEOBSERVEOPERATE
  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