refactor(design-docs): dissolve product/ into meta/ — process/method records (RIG-2577 T8)

apps/ui/src/design-citations.test.ts

@@ -1,7 +1,7 @@
 // Source-hygiene gate: no retired-milestone design citations survive in shipped
 // UI source. The early Compass milestone records (v0.3 through v0.8) were
 // retired (RIG-2453); their still-true rationale was consolidated into
-// `docs/designs/product/compass-architecture-lineage/design.md` and every
+// `docs/designs/meta/compass-architecture-lineage/design.md` and every
 // shipped citation re-pointed there.
 //
 // A vintage provenance tag naming a retired milestone — `design compass-0.6`,
@@ -73,7 +73,7 @@ describe("design-citation hygiene (no retired-milestone design refs)", () => {
 		expect(
 			violations,
 			violations.length > 0
-				? `Retired-milestone design citations found in shipped source — re-point to the architecture-lineage record (docs/designs/product/compass-architecture-lineage/design.md):\n${report}`
+				? `Retired-milestone design citations found in shipped source — re-point to the architecture-lineage record (docs/designs/meta/compass-architecture-lineage/design.md):\n${report}`
 				: "",
 		).toEqual([]);
 	});

apps/ui/src/identity.test.ts

@@ -14,7 +14,7 @@ import { STUB_AGENTS, STUB_ISSUES } from "./stub-data";
 import { testQueryClient } from "./test-support";
 
 // T1 — Agent identity: separate co-addressed types + fixture reconciliation
-// (design record `docs/designs/product/compass-architecture-lineage/design.md`,
+// (design record `docs/designs/meta/compass-architecture-lineage/design.md`,
 // T1 §282-400). RED-FIRST: this suite is authored against T1's specified surface
 // — the account-kind `Agent`/`Account` in stub-data.ts (design.md:325-362), the
 // cached `account.homeChannelId` (:339,367-369), the derived `STUB_ACCOUNTS`

docs/designs/infra/runtime/compass-managed-multitenancy/design.md

@@ -309,7 +309,7 @@ touch the agent↔Runner vsock hop (RIG-2394), and it never becomes a second
 store — Postgres remains the durability source of truth, preserving the
 DL-019/DL-020 spirit ("the ring is never a second store; losing it loses no
 committed state",
-`docs/designs/product/compass-architecture-lineage/design.md:52-56`).
+`docs/designs/meta/compass-architecture-lineage/design.md:52-56`).
 
 **What rides the substrate.**
 
@@ -370,7 +370,7 @@ poison message parks instead of redelivering forever.
 NATS on the agent↔Runner hop (frozen vsock, RIG-2394); JetStream as the comms
 **message store** (Postgres write-through is the product's structure — the
 audit/search substrate rationale behind DL-021,
-`docs/designs/product/compass-architecture-lineage/design.md:46-51` — and
+`docs/designs/meta/compass-architecture-lineage/design.md:46-51` — and
 that survives this record intact: JetStream carries delivery, Postgres keeps
 the message).
 

docs/designs/product/compass-test-strategy/design.md → docs/designs/meta/compass-test-strategy/design.md

@@ -230,7 +230,7 @@ fixture from this record. This record does not edit the dogfood-e2e record.
 
 ### A5 — Record placement: standalone product record
 
-`docs/designs/product/compass-test-strategy/design.md` — cross-cutting over
+`docs/designs/meta/compass-test-strategy/design.md` — cross-cutting over
 the verticals and the gate contract, directory-form like its siblings.
 Records freeze on merge; this one supersedes-by-citation and rewrites none.
 It supersedes its own ancestor record in the two amended decisions (D-A1,

docs/designs/observability/compass-observability-architecture/design.md

@@ -263,7 +263,7 @@ we can swap out on the managed service for a bigger dep."** So:
   dependency — "a deterministic in-memory/fake reference proves each contract
   cheaply, and a live `pgtest` suite proves the real Postgres backend obeys
   the same contract"
-  (`docs/designs/product/compass-test-strategy/design.md:123-128,412-416`).
+  (`docs/designs/meta/compass-test-strategy/design.md:123-128,412-416`).
   Class-2 rollup tables are a natural addition, no new dependency.
 
 The rejected bigger-dep paths are in Alternatives considered.

docs/designs/product/compass-ade-shell/design.md

@@ -6,7 +6,7 @@ Status: Active
 > iteration of the Compass ADE dev shell, building on the explorable Bridge
 > walking-skeleton (#453, #460). The product vision it serves and the strategic
 > posture behind it are preserved in the
-> [architecture lineage](../compass-architecture-lineage/design.md) record. This record captures the
+> [architecture lineage](../../meta/compass-architecture-lineage/design.md) record. This record captures the
 > shell's interaction model and the workstream/agent state model — not the daemon
 > or the `compass.v1` wire contract, which stay as those records define them.
 

docs/designs/product/compass-agent-comms-tools/design.md

@@ -13,7 +13,7 @@ frozen as the agent↔Runner call transport record
 designs the two contract legs it cites but does not define — the Runner→Server
 `RelayCommsCall` RPC and the Server-side execution handler — plus the agent-side
 tools and their identity/authz model. Companion to the
-[architecture lineage](../compass-architecture-lineage/design.md) record (§T5 agent stdio contract)
+[architecture lineage](../../meta/compass-architecture-lineage/design.md) record (§T5 agent stdio contract)
 and the container-runtime record
 [`compass-agent-container-runtime.md`](../compass-agent-container-runtime.md)
 (threat model, egress posture).

docs/designs/product/compass-command-palette/design.md

@@ -9,7 +9,7 @@ parallel — the palette is the *do-an-action* surface, the overlay the
 *reference sheet*; the shared substrate is the App-root dispatcher and
 registry both consume, plus the shared commands-as-inventory rule OWNED by
 the RIG-2529 tier-3 scope-gate record
-(`docs/designs/product/compass-tier3-scope-gate/design.md`) — an external
+(`docs/designs/meta/compass-tier3-scope-gate/design.md`) — an external
 frozen dependency both records cite, never redefine (see A3/D6). No other
 cross-dependency is designed here, but at IMPL time the palette and overlay
 PRs touch the same four App-root wiring lines (`spine.ts` deps + signature,
@@ -244,7 +244,7 @@ expose — OQ-4.
 
 **The shared commands-as-inventory rule** (stated identically in the RIG-2482
 overlay record; OWNED by the RIG-2529 tier-3 scope-gate record,
-`docs/designs/product/compass-tier3-scope-gate/design.md`): *register =
+`docs/designs/meta/compass-tier3-scope-gate/design.md`): *register =
 actionable-from-anywhere; a dispatching surface (this palette's action mode)
 reads the registry, a display surface (the overlay) reads the keymap; a
 command is registered beside its behavior, never purely for discoverability —

docs/designs/product/compass-keyboard-shortcuts-overlay/design.md

@@ -18,7 +18,7 @@ command palette is RIG-2483 (do-an-action surface); this overlay is the
 exhaustive reference sheet.
 The sheet's `list.*` completeness rests on the tier-3 scope gate and
 `list.*` registration owned by **RIG-2529**
-(`docs/designs/product/compass-tier3-scope-gate/design.md`), an external
+(`docs/designs/meta/compass-tier3-scope-gate/design.md`), an external
 frozen dependency of this record — cited the same way this record cites the
 merged RIG-2456 spine (see D8, T2b).
 
@@ -198,7 +198,7 @@ Join semantics:
   (`scope: "main"`) and tier 3 becomes scope-aware, closing the RIG-2130
   RD-4/OQ-6 focus hole. That is a shared-dispatcher change and is OWNED BY
   ITS OWN RECORD, **RIG-2529**
-  (`docs/designs/product/compass-tier3-scope-gate/design.md`), which this
+  (`docs/designs/meta/compass-tier3-scope-gate/design.md`), which this
   record depends on as external frozen substrate — the same way it depends
   on the merged RIG-2456 spine. With RIG-2529 merged, the strict join (D3,
   unchanged) surfaces `?`, `Mod+B`, `Shift+Enter`, AND the `list.*` block.
@@ -378,7 +378,7 @@ toggle flips `shortcutsOpen()`; `toggleShortcuts()` then `showBridge()` →
 **Ratified (Matt, 2026-08-23): the long-term end state.** The eight
 `list.*` commands get registered and tier 3 becomes scope-aware — but that
 change is a shared-dispatcher concern OWNED BY **RIG-2529**
-(`docs/designs/product/compass-tier3-scope-gate/design.md`), an external
+(`docs/designs/meta/compass-tier3-scope-gate/design.md`), an external
 frozen dependency of this record, exactly as the merged RIG-2456 spine is.
 RIG-2529 specifies: tier 3 (`dispatch.ts:122-129`) runs a matched global
 entry's command only if `command.scope === "global"` or it matches the
@@ -558,7 +558,7 @@ failure mode to watch for is a naive resolution silently dropping a dep. No
 design change either way.
 
 **Cross-record substrate note:** RIG-2529
-(`docs/designs/product/compass-tier3-scope-gate/design.md`) is the shared
+(`docs/designs/meta/compass-tier3-scope-gate/design.md`) is the shared
 scope-gate substrate BOTH this record and RIG-2483 cite as an external
 frozen dependency; the overlay and palette impl PRs stack on RIG-2529's
 merge. The four shared App-root regions above remain an impl-time
@@ -646,7 +646,7 @@ four-region App-root conflict above is the separate impl-PR concern.)
 8. **The `list.*` overlay-rows rule is RATIFIED (Matt, 2026-08-23): the
    long-term end state — register the group-relative commands AND make
    tier 3 scope-aware — owned by RIG-2529
-   (`docs/designs/product/compass-tier3-scope-gate/design.md`), an
+   (`docs/designs/meta/compass-tier3-scope-gate/design.md`), an
    external frozen dependency of this record.** The naive drafted shape
    (register against a scope-blind tier 3) stays withdrawn as unsafe;
    RIG-2529's scope gate (run a tier-3 match only when `command.scope` is
@@ -685,7 +685,7 @@ the full rulings live in the Decisions above. In brief:
 2. **The `list.*` block (was OQ2, the blocker).** The principled end state
    — register the eight `list.*` commands AND make tier 3 scope-aware,
    closing RIG-2130 RD-4/OQ-6 — extracted to its own record **RIG-2529**
-   (`docs/designs/product/compass-tier3-scope-gate/design.md`), which this
+   (`docs/designs/meta/compass-tier3-scope-gate/design.md`), which this
    record consumes as external frozen substrate (D8, T2b). Neither the
    group-relative-rendering workaround nor deferral to RIG-2483 was taken.
 3. **Shift-drop scope (was OQ3).** The GENERAL rule — drop `Shift` for a

tools/design-ledger-gate/index.ts

@@ -5,7 +5,7 @@
 // visible forward (the superseding record cites the superseded one, nothing
 // points back), so an agent grounding on a single record could not tell a
 // decision in it was overturned elsewhere. The fix (design record:
-// docs/designs/product/compass-design-ledger/design.md) is a canonical
+// docs/designs/meta/compass-design-ledger/design.md) is a canonical
 // read-first ledger (DECISIONS.md), machine-checkable per-record `Status:`
 // headers, and this gate against dangling pointers + a forgotten same-PR
 // ledger flip.
@@ -633,7 +633,7 @@ export async function runOnce(deps: Deps): Promise<number> {
 		err(line > 0 ? `  ${file}:${line}: ${message}` : `  ${file}: ${message}`);
 	}
 	err("");
-	err("See docs/designs/product/compass-design-ledger/design.md.");
+	err("See docs/designs/meta/compass-design-ledger/design.md.");
 	return 1;
 }