# Icebox — retired code (recoverable, not destroyed) Per issue #75 (consolidate to a single harness), the routing-pod path was removed from the live tree. It is **preserved and recoverable**, not deleted without trace. ## What was iceboxed (2026-07-01, issue #75) | Path | Why | |------|-----| | `cmd/routing/` | The routing MCP-server binary; every skill call was wrapped through the broken pass-rate router (`wrap(skillName)`). | | `internal/routing/` | Router / Fetcher / Policy / pass-rate. Signal is survivorship-biased and unusable as-is (infra#174). | | `internal/skills/{review,debug,retrospective,trainer,project}/` | Skill handlers usable **only** through `cmd/routing` (verified: each imported solely by `cmd/routing`). | | `Dockerfile.routing` | Built `cmd/routing` exclusively. | | `.gitea/workflows/cd.yml` (routing steps only) | Removed the routing image build + infra image-bump + Flux-wait/rollout-verify for routing; **ingestion build/deploy is unchanged**. | ## Why The live minimal harness is `cmd/hyperguild` + `brain-mcp` (+ `gitea-mcp` available) — that is what ran the infra#170 loop-1 experiment (routing/injection machinery off) and closed it twice. `cmd/hyperguild` has **zero** transitive dependency on `internal/routing` or `cmd/routing`'s packages (it imports only `internal/tier`). The routing pass-rate signal is being retired, not resurrected (fresh start, per infra#174). ## How to recover Everything above is preserved at commit `00e5f62` under: - **tag** `icebox/cmd-routing-2026-07-01` - **branch** `icebox/cmd-routing` ```bash # inspect git checkout icebox/cmd-routing-2026-07-01 # restore specific packages onto a branch git checkout icebox/cmd-routing-2026-07-01 -- cmd/routing internal/routing \ internal/skills/review internal/skills/debug internal/skills/retrospective \ internal/skills/trainer internal/skills/project Dockerfile.routing ``` ## Deliberately NOT touched here (separate scope) - **Live k8s routing deployment** (`infra` repo, `k3s/apps/routing/`) still runs its last image; CD no longer rebuilds/redeploys it. Tearing down that deployment is a separate infra-repo task. - **`internal/skills/{brain,org,sessionlog}/`** — kept per #75; already had no importer (orphaned before this cut), harmless, compile + test green. - **`config/supervisor/{review,debug,retrospective,trainer-*}.md`** — routing skill prompts, now orphaned data; left in place (not code, no build impact).