Operations · Promotion and operability
Every deployment names the exact artifact, contract revision, state boundary, and public proof
The promotion path runs the full gate battery at an exact commit, builds one schema-pinned image, releases that named artifact into an isolated environment, and proves health, identity, mutation, and reads through the public edge before promotion.
Operations · Promotion and operability
Every deployment names the exact artifact, contract revision, state boundary, and public proof
The promotion path runs the full gate battery at an exact commit, builds one schema-pinned image, releases that named artifact into an isolated environment, and proves health, identity, mutation, and reads through the public edge before promotion.
What this view establishes
The architectural commitments
- A release is named by both code and contract revision, so an operator can prove what every machine actually runs.
- Staging and production isolate database, bucket, credentials, and posture while sharing the promoted artifact.
- Internal health is insufficient: promotion evidence must traverse the same public edge and credential path as a real client.
- Customer-owned releases and dedicated/shared deployment choices are described in the customer delivery and deployment business-case views; local proof and hosted acceptance are distinct.
Environment/artifact matrix and promotion strip
Promotion strip
One artifact, explicit gates
- 01Exact Git headverifiesFull gate battery
- 02Full gate batterypermitsEnvironment approval
- 03Environment approvalbuildsGateway image
- 04Gateway imagetagged onceArtifact tag
- 05Artifact tagcontract smokeEphemeral testing
- 06Artifact tagreleasesStaging
- 07Stagingpromotes same tagProduction
Exact artifact
Exact Git head
Clean source commit selected for promotion
Full gate battery
Generation, Swift, gateway, worker, web, stack and apps
Environment approval
Manual promotion keeps release authority explicit
Gateway image
Code, schema closure and domain kernels built together
Artifact tag
g<commit>-s<schema revision> names the release
Environments
Release proof
Directed relationship matrix
Blank cells mean no promotion or reporting relationship is claimed in this view.
| From ↓ / to → | Ephemeral testing | Staging | Production | Structured telemetry | Public edge smoke | Release ledger |
|---|---|---|---|---|---|---|
| Artifact tag | 05 implemented | 06 observed | · | · | · | 10 implemented |
| Staging | · | · | 07 planned | 08 implemented | 09 observed | · |
Connections and evidence
Open the 10-relationship source key
Numbers set an explanatory reading order. They do not measure runtime timing.
Connections and evidence
Open the 10-relationship source key
- 01implemented
Exact Git head→Full gate battery
verifies
- 02implemented
Full gate battery→Environment approval
permits
- 03implemented
Environment approval→Gateway image
builds
- 04implemented
Gateway image→Artifact tag
tagged once
- 05implemented
Artifact tag→Ephemeral testing
contract smoke
- 06observed
Artifact tag→Staging
releases
- 07planned
Staging→Production
promotes same tag
- 08implemented
Staging→Structured telemetry
reports
- 09observed
Staging→Public edge smoke
proved through edge
- 10implemented
Artifact tag→Release ledger
records
Connections and evidence
10 directed, source-backed relationships
Numbers set an explanatory reading order. They do not measure runtime timing.
- 01implemented
Exact Git head→Full gate battery
verifies
- 02implemented
Full gate battery→Environment approval
permits
- 03implemented
Environment approval→Gateway image
builds
- 04implemented
Gateway image→Artifact tag
tagged once
- 05implemented
Artifact tag→Ephemeral testing
contract smoke
- 06observed
Artifact tag→Staging
releases
- 07planned
Staging→Production
promotes same tag
- 08implemented
Staging→Structured telemetry
reports
- 09observed
Staging→Public edge smoke
proved through edge
- 10implemented
Artifact tag→Release ledger
records
What this view establishes
The architectural commitments
- A release is named by both code and contract revision, so an operator can prove what every machine actually runs.
- Staging and production isolate database, bucket, credentials, and posture while sharing the promoted artifact.
- Internal health is insufficient: promotion evidence must traverse the same public edge and credential path as a real client.
- Customer-owned releases and dedicated/shared deployment choices are described in the customer delivery and deployment business-case views; local proof and hosted acceptance are distinct.
Follow the live system
Move from explanation to inspection
The Atlas is static and source-backed. The Observatory shows authenticated environment state.
13 repository sources behind this view
.github/workflows/deploy.yml.github/workflows/gates.ymlcompose.testing.yamldeploy/fly/gateway-admin.shdeploy/fly/gateway-production.tomldeploy/fly/gateway-staging.tomldocs/deployment.mddocs/operability-g0.mdgateway/Dockerfilegateway/src/neostory_gateway/telemetry.pyscripts/ci-local.shscripts/edge-smoke.shscripts/test-env.sh