0001 — Redesign rocky-hq into a superproject

• Date: 2026-05-02
• Status: Accepted
• Supersedes: none (first decision in this repo)
• Partially superseded by: 0002-rename-fleet-to-hearth.md — renames SS-08 FLEET → HEARTH and commits Phase 3 to KAHN's transitions schema. Body of this decision is preserved verbatim (append-only convention, MR-7); read 0002 alongside.

Context

rocky-hq was scaffolded as a single-feature Python prompt-queue tool ("ralph wiggum") under docs/specs/2026-05-02-rocky-design.md. A separate Next.js operations-and-modelling centre (@rocky/ops) had been developed under devarno-cloud/rocky with seven shipped subsystems (VTM Pass). The two share the name "Rocky" but had no integration path. PETROVA's long-term goal of mandating one Rocky per onboarded project required a single coherent surface.

Decision

Pivot rocky-hq from a Python project root into a superproject mirroring devarno-cloud's shape. The Next.js console is lifted in as a submodule (Phase 2), the existing Python tool becomes the RALPH submodule (Phase 3), and a new Go-based FLEET submodule provides per-workspace CAIRNET+LORE provisioning (Phase 5). Identity stays tenanted in Airlock; OSS distribution is first-class via a LocalAuth adapter and a LocalDocker driver; Polar.sh entitlements gate cloud-only tiers.

Full design: docs/specs/2026-05-02-rocky-system-redesign.md.

Consequences

• The original RALPH spec (docs/specs/2026-05-02-rocky-design.md) is not superseded — it remains the authoritative spec for SS-07 RALPH and travels with the Python code into the ralph/ submodule in Phase 3.
• This repo's CLI consumers (anyone running rocky run from a clone of rocky-hq) must continue to work through Phases 1–2; the move into a submodule lands in Phase 3 with an installation-path migration note in the README.
• PETROVA's petrova-hq/registry.yaml schema needs an integrations_applicability.rocky field; that schema change is a separate PETROVA decision.

References

• Spec: docs/specs/2026-05-02-rocky-system-redesign.md
• Original RALPH spec: docs/specs/2026-05-02-rocky-design.md
• Pattern reference: devarno-cloud/docs/decisions/0001-control-plane-bootstrap.md