Skip to content

Runbooks

Operational instructions are target-specific. Every runbook states exact identity, authorization, write scope, readback, rollback and evidence level.

Deployment Is Not Cutover

Treat these as separate claims:

source committed
artifact built
artifact installed
process active
/release identity matches
/health is live
/ready dependencies pass
route externally exposed
writer/default route changed
target-role journey accepted
Phase accepted

A successful process deployment proves none of the later claims by itself.

Logistics Workspace Web Verification

After a separately approved New-System runtime deployment, run the following checks on the deployment host or in an approved network environment. The working directory of the command is the repository root. A Git-only delivery is separate from a runtime deployment, and this section does not authorize build, restart or operational access:

node new-system/scripts/release/verify-deployment.mjs \
  --origin=http://127.0.0.1:3000 \
  --expected-release=<exact-git-or-artifact-release-id> \
  --expected-environment=<qa|production> \
  --output=.generated/release/deployment-verification.json

The verifier requires matching /release, /health and /ready identities, no-store responses, exact release/environment values, liveness and non-degraded readiness. A failure blocks release promotion.

Logistics Workspace runs from /. For the local port-3000 Web runtime, follow the repository Local Web Runtime contract: use the existing com.ctc.new-system-web user service, then verify /health and /ready. Do not start a second terminal-bound listener. Git delivery and service/release effects remain governed by Project Operations.

Additionally verify, when the deployed capability requires them:

  • exact DB identity and additive migration/readback;
  • UUID/null/duplicate/orphan/mismatch reconciliation;
  • file-storage root existence, permissions and cleanup;
  • actual C1/C2 login and normal/negative journeys;
  • rollback to the previous artifact or isolated-service stop;
  • Legacy fallback and absence of unintended route/writer cutover.

Reverse proxy, external route, default route, writer cutover and Legacy retirement require a separately authorized transition/** packet. They are not owned by a numbered Product phase merely because a process was deployed.

Isolation, Recovery And Telemetry

Operational Readiness owns the source regression commands, opt-in isolated composition restore drill, redacted diagnostics/performance baseline and explicit remaining target-role, policy and full-recovery requirements. A source PASS does not close them.

Source: new-system/docs/runbooks/README.md — ctc repository · This page is an English translation of the source document.