# Findings on the relay spec, revision 6

| Revision-5 finding | Disposition | Reason |
|---|---|---|
| R5-1 — P2 — Rotation has no cutover path for externally managed TCP routes | **Closed** | Enable refuses routes without config delivery. Externally supervised TCP routes establish cutover through `carlos relay adopted --host`, recorded against the issued identities. Routes lacking cutover block retirement and are named by status. The retirement bound remains `max(rotation + 28h, latest cutover + 4h)`. |

Evidence: §5’s [enable prerequisite](/home/paulca/amadan.net/carlos/platform/.claude/worktrees/media-roadmap-spec/docs/superpowers/specs/2026-09-07-relay-stun-turn-design.md:475) and [cutover and retirement procedure](/home/paulca/amadan.net/carlos/platform/.claude/worktrees/media-roadmap-spec/docs/superpowers/specs/2026-09-07-relay-stun-turn-design.md:567).

Reviewed commit `fccd93f8d1bcedc4187ed6b91e35e1a5e8293b05`, treating Paul’s six rulings as fixed and applying the requested stage-spec threshold. Checked the prior findings, parent roadmap, suite doctrine, referenced code, and [Pion v4.1.4’s API](https://pkg.go.dev/github.com/pion/turn/v4@v4.1.4) and authentication source. All three cryptographic test-vector values reproduce.

**No new or remaining P1 or P2 problems found.** No R6 findings to report. The stated mechanisms are sufficient for an implementation plan.

No files were changed; no live TURN or EC2 tests were run.

**Verdict: accept.**