Deployment record

Every Deployment Has Identity.

A Deployment Record answers what was deployed, where, why, from which configuration and versions, whether it succeeded, whether it was verified, and what evidence proves the result.

ARCHITECTURE / DEPLOYMENT PREVIEW

Prepared fields

deployment_iddeployment_typetarget_iddomain_idnamespace_idnode_idsurface_idsurface_manifest_idtemplate_idtemplate_versionconfiguration_idconfiguration_versionbusiness_record_idsinformation_record_idsgraph_context_versiondata_versionenvironmentrequested_byapproved_bystarted_atcompleted_atstatusverification_statusrelease_idprevious_release_idrollback_release_idtrace_idreceipt_idevidence_id

Field set is prepared, not yet backed by storage.

Deployment ID

DEP-US-MN-DUL-00000184

Example syntax only — not finalized. A deployment remains identifiable after the domain changes, the template changes, the surface changes, another release supersedes it, or a rollback occurs.

Manifest
Desired deployment state
Record
What actually happened
Receipt
Evidence of the reported result
Observation
Actual observed state

Deployment inspector

Select a record to inspect its full lineage

Identity, domain, geography, configuration, template, data, surface, release, pipeline, verification, observation, evidence, rollback, operations and audit.

Deployment records

Six illustrative records. No production deployment history is connected.

Deployment record

DEP-US-MN-DUL-00000184

Duluth City Node

PREVIEW · SUCCESSSIMULATED · VERIFIEDTARGET ENV · PRODUCTION

Identity

deployment_id
DEP-US-MN-DUL-00000184
deployment_type
SURFACE INSTANCE
target
Duluth City Node
environment
PRODUCTION
status
PREVIEW · SUCCESS

Domain

domain
Cityizz.com
namespace
NS-GEO-US-MN-DULUTH
purpose
SURFACE INSTANCE for Duluth City Node

Geography

country
USA
state
Minnesota
county
St. Louis County
city
Duluth
community
Canal Park
grid node
NODE-US-MN-DUL-014

Configuration

configuration_id
CFG-CITY-MN
configuration_version
v12
variables
brand · navigation · geography · features · search
policies
approval required · required verification · rollback rules

Template

template_id
TPL-CITY
template_version
v8

Data

data_sources
DATA PENDING — record sources not connected
business_records
BR-88213 · BR-88214
information_records
IR-11902
graph_context
GCTX-v6
data_version
DATA-v22

Surface

surface_manifest
SMF-CITY-0042
surface_instance
SRF-US-MN-DUL-CITY-001
surface_version
TPL-CITY v8

Plan

deployment_manifest_id
DMF-NODE-US-MN-DUL-014
plan_id
PLN-000184
current_release
REL-13
desired_release
REL-14
change_set
5 change · 1 add · 0 remove · 2 no change
blast_radius
MODERATE
rollback_target
REL-13
approval_requirement
HUMAN APPROVAL REQUIRED
risk_level
MODERATE
plan_status
PREVIEW

Release

release_id
REL-14
previous_release
REL-13
build_version
REL-14-build.3

Pipeline

PLANRESOLVE NAMESPACERESOLVE NODELOAD CONFIGURATIONLOAD TEMPLATELOAD RECORDS / DATALOAD GRAPH CONTEXTLOAD SURFACE MANIFESTVALIDATEBUILDAPPROVE RELEASEDEPLOYVERIFYOBSERVEREGISTER WITH GRIDREGISTER RELATIONSHIPSHAND OFF TO USA OS

Verification

verification_status
SIMULATED · VERIFIED
checks
15 defined checks (domain, surface, versions, records, graph)
results
PREVIEW — no live verification runner connected

Observation

observed_state
TPL-CITY v8 · CFG-CITY-MN v12
desired_state
TPL-CITY v8 · CFG-CITY-MN v12
drift
PREVIEW · IN SYNC

Evidence

deployment_receipt
RCP-000184
verification_evidence
EVD-000184
surface_observation
OBS-000184

Rollback

previous known-good release
REL-13
rollback availability
AVAILABLE

Operations

usa os status
OBSERVING
alerts
none
health
HEALTHY

Audit

requested_by
operator:architecture-preview
approved_by
policy:human-approval
started_at
2026-09-11 14:02:10Z
completed_at
2026-09-11 14:06:41Z

Change set — planned

What will change — DEP-US-MN-DUL-00000184
ObjectCurrentDesiredAction
Templatev7v8CHANGE
Configurationv11v12CHANGE
Business Recordv14v14NO CHANGE
Information RecordabsentIR-11902ADD
Graph Contextv5v6CHANGE
Surface Manifestv3v4CHANGE
Surface InstanceExistingExistingVERIFY
Grid NodeExistingExistingNO CHANGE
ReleaseREL-13REL-14CHANGE
ActionsADDCHANGEREMOVENO CHANGERECREATEVERIFY

Change result — after execution

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.

Blast radius

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
build log — DEP-US-MN-DUL-00000184
» trace           TRACE-20260911-000184
» manifest        DMF-NODE-US-MN-DUL-014
» namespace       NS-GEO-US-MN-DULUTH
» configuration   CFG-CITY-MN v12
» template        TPL-CITY v8
» surface         SRF-US-MN-DUL-CITY-001
» release         REL-14 (previous REL-13)
» plan            PLN-000184 (5 change · 1 add · 2 no change)
» stage           HAND OFF TO USA OS
» status          SUCCESS
» verification    VERIFIED
» drift           none observed

# architecture preview — evidence is simulated, not production output

Manifest → record

Manifest Defines Intent. Deployment Record Captures Execution.

  1. 01DEPLOYMENT MANIFESTDesired state
  2. 02VALIDATE
  3. 03BUILD
  4. 04DEPLOY
  5. 05DEPLOYMENT RECORDExecution
  6. 06VERIFY
  7. 07OBSERVATION
  8. 08ACTUAL STATE
  9. 09COMPARE
  10. 10IN SYNC or DRIFT DETECTED
  11. 11USA OS

Manifest Defines Intent.

Deployment Record Captures Execution.

Deployment manifest fields

deployment_manifest_idtargetdomainnamespacenodegeographyenvironmenttemplatetemplate_versionconfigurationconfiguration_versiondata_sourcesbusiness_recordsinformation_recordsgraph_contextsurface_manifestdependenciesdeployment_policyverification_policyrollback_policydesired_releasedesired_state
Open in console