KB-3D66
O8A live-execution wiring authoring (Contabo) — 07-deploy-update-decision
4 min read Revision 1
dieu44iu-cutterv0.6o8alive-execution-wiringauthoringsandbox-proofcontabo
O8A Report 07 — Deploy / update decision
- macro:
v0.6-o8a-live-execution-wiring-authoring - date_utc: 2026-05-21 · host:
vmi3080463(Contabo) - gate covered: G6 deploy / update decision
1. Decision
promote_o8a_into_deployed_tree_now: NO
deliverable: staging package + a deploy command-package for a reviewed
follow-up macro
deployed_tree_iu-cutter-v0.6: UNTOUCHED (proven §3)
v0.4_skeleton: UNTOUCHED
execution_enabled: False (unchanged)
2. Rationale
- SSOT discipline. The KB-pinned source of truth is the developer
Mac repo at HEAD
6625f76(O5/O6 rulings); Contabo receives reviewed deploys. Promoting O8A code straight into the Contabo deployed tree would put Contabo ahead of SSOT — the exact anti-pattern O5 risk R-12 guards against. O8A code must first land in the Mac SSOT repo, then deploy. - Artifact verifiability. The deployed
iu-cutter-v0.6matches itsDEPLOY-MANIFEST(artifact shab2c11e5…) and was O7-certified. Editing it in place breaks that verifiable identity. - Authoring ≠ deployment. O8A is an authoring + sandbox-proof macro. Deployment is correctly a separate macro with its own command-review (the established pattern — O6/O6B).
- No urgency.
execution_enabledstaysFalse; nothing live can run regardless of where the O8A code sits. There is no operational pressure to promote now.
3. Deployed-tree integrity proof
$ diff -rq iu-cutter-v0.6 iu-cutter-v0.6-o8a-staging --exclude=__pycache__
→ only the 9 O8A files differ/are-new; every other file is identical.
DEPLOY-MANIFEST.txt sha256 = dd787b064ea9cb3dbd34a29c636ef3fcbc723ee1377c1262864d3f17d7995d76
The deployed tree is the unchanged baseline; all O8A edits live in
iu-cutter-v0.6-o8a-staging/.
4. Deploy command-package (for the follow-up macro)
macro: O8A_DEPLOY_LIVE_WIRING (high; reviewed command-package)
precondition:
- O8A authoring ruled PASS by GPT
- O8A code reconciled into the Mac SSOT repo (new commit on top of
6625f76) — the canonical landing, then a fresh artifact + manifest
change_set (9 files):
modified: orchestrator/__init__.py, orchestrator/runner.py,
orchestrator/phases/{backup,cut_leg_a,leg_b_record,
write_verify,lifecycle_enact}.py
new: orchestrator/live_execution.py,
tests/test_orchestrator_o8a_live_wiring.py
deploy_method:
- git archive the new SSOT HEAD → scp → tar extract → mv promote
(identical to the O6B deploy method), side-by-side, kill-switch OFF
post_deploy_assertions:
- __execution_enabled__ == False
- __live_wiring__ == "O8A-..." (or milestone bumped at ratify)
- python3 -m unittest discover -s tests → 394/394 PASS
- import smoke: live_execution.LiveExecutionAdapter present
rollback:
- restore the prior iu-cutter-v0.6 tree from a timestamped pre-state
copy; code-only, no service, no DB change
forbidden (unchanged): no execution_enabled flip; no service restart;
no production mutation; no push to a public remote
5. Staging artifact
/opt/incomex/dot/iu-cutter-v0.6-o8a-staging/ ← the O8A deliverable
cutter_agent/orchestrator/live_execution.py ← new seam module
cutter_agent/orchestrator/{__init__,runner}.py ← modified
cutter_agent/orchestrator/phases/*.py ← 5 modified
tests/test_orchestrator_o8a_live_wiring.py ← new proof
o8a-reports/01..08-*.md ← this KB package
Whole-macro rollback: rm -rf /opt/incomex/dot/iu-cutter-v0.6-o8a-staging
— survey + isolated authoring only; nothing else on the host changed.
G6 = decision delivered. Do not promote in this macro; deploy is a separate reviewed macro after SSOT reconciliation.