# CAIN-42 × TALOS: Residual Risks & Production Blockers
## Evolution 5 — Operation Double Sovereign

---

### 1. Residual Security Risks

1. **In-Process Gateway Execution:**
   - The platform gateway (`platform-gateway/main.py`) executes tool calls in-process. While `TalosGovernedCommandRunner` is available as a library and tested in `cain/talos/`, hosted API endpoints do not yet spawn Landlock child workers.
2. **Missing Remote Hosted CI:**
   - The repository has no configured remote (`git remote -v` is empty). All tests have been executed locally. A remote hosted CI pipeline is mandatory before production release.
3. **Absence of Production MCPGate Routing:**
   - Production customer traffic arriving at `https://cainstudio.online` does not traverse the MCPGate boundary proxy.
4. **Single-Node SQLite Durability:**
   - Replay protection relies on local SQLite WAL. An adversary with root/storage access can delete or modify the database file. Distributed multi-region deployments require BFT consensus or an external Byzantine notary.
5. **Lack of Independent Third-Party Human Review:**
   - The entire implementation and verification suites have been conducted by AI agents and internal developers. No external third-party human security audit has taken place.

---

### 2. False-Positive & Operational Risks

1. **Overly Restrictive Landlock Paths:**
   - If an agent tool requires reading dynamic libraries outside `/usr`, `/lib`, or the Python prefix, Landlock returns `PermissionError`. Resource scopes must explicitly enumerate necessary path dependencies.
2. **Clock Drift Between CAIN & TALOS:**
   - If server clocks drift beyond `clock_tolerance_seconds` (default 5s), valid envelopes may be rejected with `INDETERMINATE` (future-issued) or `EXPIRED`. NTP synchronization is required.
3. **UDP & Raw Socket Egress:**
   - Landlock ABI 8 restricts filesystem operations and TCP connect/bind. UDP sockets are not restricted by Landlock ABI 8 and require seccomp or network namespace isolation.

---

### 3. Production Release Blockers

| Blocker ID | Description | Remediation Required | Status |
|:---|:---|:---|:---:|
| `BLK-01` | Git remote not configured; no hosted CI run. | Configure remote origin, push branch, run GitHub Actions. | **BLOCKED** |
| `BLK-02` | Hosted gateway tool calls run in-process. | Route gateway tool calls through `TalosGovernedCommandRunner`. | **BLOCKED** |
| `BLK-03` | Live customer traffic does not route via MCPGate. | Wire Traefik/Kubernetes ingress to MCPGate boundary proxy. | **BLOCKED** |
| `BLK-04` | No external independent human security audit. | Commission third-party audit firm for cryptographic verification. | **BLOCKED** |

**Conclusion:** The local software development gate is **PASS**, but the production release gate is strictly **BLOCKED**.
