05 - Post-Deploy Checks

O6 · doc 5 of 8 · 2026-05-21 · Gates G4 + G5.

1. Status: NOT EXECUTED — transitively blocked by G3

G4 (runtime skeleton) and G5 (import / py_compile / tests / status) operate on a deployed v0.6 artifact. Because G3 did not deploy anything (doc 04 — GAP-O6-SOURCE), there is no artifact to skeleton or check.

G4_runtime_skeleton:
  status: NOT EXECUTED
  /var/lib/cutter/{runs,batches,locks}: NOT created (host left untouched)
  orchestrator.* config: NOT written
  secrets written: NONE
  rationale: provisioning empty runtime dirs without code serves nothing;
             a clean BLOCKED leaves the host 100% unmodified so rollback
             is a true no-op. The skeleton plan is held in doc 03 §7.

G5_post_deploy_checks:
  status: NOT EXECUTED
  py_compile:      n/a — no v0.6 tree present
  import test:     n/a
  unit tests:      n/a — cannot run 366/366 without the code
  orchestrator status / milestone: n/a

2. What IS known about the readiness of these checks

The checks themselves are well-defined and known-safe (doc 03 §5); only the artifact is missing:

environment_ready:
  python: 3.12.3 on Contabo  → adequate for the v0.6 code
  test_runner: pytest/unittest available
baseline_expectation (from KB SSOT):
  tests: 366/366 PASS  (O4 ruling)
  execution_enabled: False
once GAP-O6-SOURCE is resolved, G5 is expected to be a low-risk pass —
it is import/compile/test only, with no mutation.

3. Production-mutation check

production_mutation_during_O6: NONE
db_writes:                     NONE
.env / secret writes:          NONE
service start/restart:         NONE

4. G4 / G5 result

G4: NOT EXECUTED (blocked upstream; host untouched by design)
G5: NOT EXECUTED (blocked upstream; no artifact to check)
no production mutation; no host mutation