# Sovereign Evolution 3 — deployment preflight for eaf8d4fa

**Result: PREFLIGHT HALTED. No production target exists for this change, so nothing was deployed.**
Production was not touched; no confirmation was requested for a deploy that would not do what it claims.

## 1. What eaf8d4fa changes

`cain/mcp_proxy.py` (+16 lines; later commits touching the file: bfe0637e opt-in Landlock wiring) plus 7 test files.
The diff contains nothing unrelated. Required tests: CI gate 275 passed (local) and 275 passed (clean checkout of
bfe0637e); broad run 1209 passed, 0 failed (61 files).

## 2. Where `cain/mcp_proxy.py` runs in production: nowhere (verified 2026-10-12)

| Check | Observed |
|---|---|
| Live gateway (blue :8088 pid 584495, green :8098 pid 579818, started 03:47/03:46Z from deploy/20261012T034805Z = bf225092) | imports `cain.mcp_proxy` only in `cain_cluster._check_local_mcp_subsystem` (a node self-check that instantiates the class) and in `adversarial_engine` self-tests. No route passes customer traffic through it. Hosted `/mcp` uses `cain/continuum/hosted_pipeline.py` + the carve-out guard stack instead. |
| systemd units / docker containers / processes on this host | none runs `create_mcp_proxy_app` or `StdioMCPProxy` |
| Served SDK (`platform-gateway/frontend/cainstudio-0.2.0…0.6.0.whl`) | does **not** contain `cain/mcp_proxy.py` |
| `cain_trust` wheels (`dist/cain_trust-2.0.0`, `4.0.0`) | contain `cain/mcp_proxy.py` (stale), but are **not distributed**: `https://cainstudio.online/…/cain_trust-4.0.0…whl` 404, `https://mcpgate.online/…` 404, `https://pypi.org/pypi/cain-trust/json` 404 |

Conclusion: the "affected live path" described in Evolution 2 does not exist. A gateway rolling deploy would leave
customer-facing MCP decisions unchanged. It **would** ship other sessions' committed changes since bf225092
(Evolution 15 mission-control modules, `cain/action_commit/reference_monitor.py`,
`cain/execution_chain/hosted_stages.py`). It would also re-ship 9 uncommitted gateway files, although those bytes
are already running: each was modified 00:15–00:32Z, before the 03:46/03:47Z starts.

## 3. Rolling deploy dry run (no changes)

`python3 scripts/ops/rolling_deploy.py --who cain-studio-platform-46 --why "…" --dry-run` → exit 3, **REFUSED**:
9 uncommitted files are reachable from `main.py` (`cain/exfiltration/trifecta_guard.py`,
`cain/mcpgate_guard_stack_hosted.py`, `platform-gateway/{cain5/intelligence_gateway,cain_ecosystem_pages,devx,fabric_control_plane,main,portal,webhooks}.py`).
They are not mine. Shipping them requires `--allow-uncommitted` with owner approval.

## 4. Deployment manifest (prepared, NOT executed)

| Field | Value |
|---|---|
| Revision | HEAD containing eaf8d4fa + bfe0637e (gateway deploys the working tree; the deploy tags a commit) |
| Target | gateway blue + green via `scripts/ops/rolling_deploy.py` |
| Effect on MCPGate customer traffic | **none** (section 2) |
| Prerequisites | owners commit or explicitly approve the 9 uncommitted files; -82/-17 confirm their committed changes may ship |
| Health criteria | `curl -s https://<3 domains>/health` 200 from both instances, repeated ≥6× per domain; `/api/v1/mcpgate/guard-stack/hosted-status` installed |
| Rollback revision | bf225092 (tag deploy/20261012T034805Z): `git checkout` that tag's files is NOT safe on a shared tree; rollback = redeploy the previous tag through `rolling_deploy.py` after restoring the tree, which needs the other sessions' agreement |
| Rollback readiness | **not verified**: the script has no `--rollback` mode, and the tree is shared by 5 sessions |

## 5. What would actually put eaf8d4fa in production (owner decision)

MCPGate reaches customers only if its code is distributed or run as a service. That conflicts with the
code-stays-secret directive if it means shipping source. Options:
- (a) run MCPGate as a hosted proxy service on mcpgate.online, so the code stays private;
- (b) publish a compiled or obfuscated SDK, which is still distribution;
- (c) keep MCPGate unreleased and say so publicly.

Until one of these is chosen, the honest production status for eaf8d4fa is **NOT APPLICABLE / NO PRODUCTION PATH**,
not "pending deploy".
