From 03fabf62f6dc6ece3c00292b976898161c95d48f Mon Sep 17 00:00:00 2001 From: mintaka Date: Sat, 12 Sep 2026 17:06:06 -0400 Subject: [PATCH] docs(observability): drop a bare locative introduced by the last scrub (RIG-3183) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The previous commit replaced "it lives in the PRIVATE MONOREPO ... adopted THERE" with "... is adopted there". That still points at an unnamed place — the same construction as "designed there", which the boundary rule bans by name. Removing the repo name fixed the naming half and left the pointing half. Now: "any big-scale analytics dep, if ever, is a managed-plane adoption, not this repo's and not now." States which plane owns it without a locative. Swept the family repo-wide (designed|built|adopted|handled|implemented| decided|specified|tracked|maintained|configured|deployed|solved|owned + there). Two other hits, both fine: the rule quoting itself, and compass-batteries- included:410 whose "there" refers to compass PR #1089, a public in-repo artifact. Co-authored-by: Matt Wilkinson --- .../compass-observability-architecture/design.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/designs/observability/compass-observability-architecture/design.md b/docs/designs/observability/compass-observability-architecture/design.md index 39dad973..e5872685 100644 --- a/docs/designs/observability/compass-observability-architecture/design.md +++ b/docs/designs/observability/compass-observability-architecture/design.md @@ -187,8 +187,8 @@ OSS core never stores: - **Class 3 — cross-tenant managed analytics (whole managed service, for Rigel).** PostHog-scale product analytics across ALL tenants is where a ClickHouse-class OLAP genuinely belongs — a managed-plane concern, out of - scope here. Any big-scale analytics dep, if ever, is adopted there, not in - this repo and not now. + scope here. Any big-scale analytics dep, if ever, is a managed-plane + adoption, not this repo's and not now. With the classes separated, the store question resolves cleanly — Decision D1.