mathiasandClaude Opus 4.8
fb59c390e2
Consolidate to the hyperguild-alone harness that ran the infra#170 loop-1
experiment (cmd/hyperguild + brain-mcp; routing/injection machinery off).
Verified cmd/hyperguild has zero transitive dep on internal/routing or
cmd/routing's packages (imports only internal/tier). Removed the routing
path, which is dormant from the live session (.mcp.json wires only brain-mcp)
and entangled with the survivorship-biased pass-rate router (infra#174).
Iceboxed (recoverable at tag icebox/cmd-routing-2026-07-01 / branch
icebox/cmd-routing, commit 00e5f62):
- cmd/routing/, internal/routing/
- internal/skills/{review,debug,retrospective,trainer,project}/
(each imported solely by cmd/routing — verified)
- Dockerfile.routing
- cd.yml: routing image build + infra bump + Flux-wait/rollout-verify
(ingestion build/deploy unchanged)
Kept: cmd/hyperguild, ingestion/, internal/tier (used by cmd/hyperguild +
skills/org), internal/skills/{brain,org,sessionlog} (per #75; already orphaned).
Regression: root module 21→14 pkgs (−7 = exactly the removed set, no other
breakage); ingestion 24/24 unchanged. See ICEBOX.md. Refs #75, infra#170, #174.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
50 lines
2.4 KiB
Markdown
50 lines
2.4 KiB
Markdown
# 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).
|