docs(observability): scrub managed-boundary place-pointers from the observability record and concepts docs (RIG-3247) - #1117
Merged
Conversation
…bservability record and concepts docs (RIG-3247)
…managed-plane vocabulary (RIG-3247) Review found a place-pointer that survived the first pass in a file the PR already edits: the Global Constraints bullet read "is private-monorepo, named + deferred". The first sweep's grep pattern used a literal space, so the hyphenated form was invisible to it. Also normalizes two "private plane"/"private-plane" tier descriptors to "managed-plane" (the term the rest of the record uses), and gives "tracked there too" an explicit antecedent now that the place-pointer it referenced is gone. Co-authored-by: Matt Wilkinson <matt@rigel.build>
|
😎 Merged directly without going through the merge queue, as the queue was empty and the PR was up to date with the target branch - details. |
rigel-mintaka
marked this pull request as ready for review
September 11, 2026 20:40
|
Compass engineering docs preview: https://compass-obs-rig-3247-boundar.compass-eng-docs.pages.dev Deployed from Changed pages: |
mattwilkinsonn
approved these changes
Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scrubs managed-boundary place-pointers from this lane's share of RIG-3247. Public-repo prose must never name the private repo nor point at it as a place (
docs/concepts/self-host-and-managed.md); deferrals say that something is managed-plane and out of scope, never where it is designed.What changed
Four files, prose only. Every technical claim is preserved — the reframe drops the where-pointer and keeps the what.
docs/designs/observability/compass-observability-architecture/design.mddocs/concepts/tokens-and-billing.mddocs/concepts/README.mdAGENTS.mdAGENTS.mdis the highest-visibility instance in the repo: an always-on front-door file injected into every compass agent's context.Deliberately not touched
RIG-3247 lists sites that state the ban rather than violate it. All four remain untouched, confirmed against the pushed diff:
docs/concepts/self-host-and-managed.md— the canonical statement of the convention.docs/designs/agent/compass-per-agent-overrides/design.md— states the rule.docs/designs/server/compass-gateway-oauth-enrollment/design.md— compass-server's lane, and contains its own rule statement. Its 3 sites are left for that owner.tools/orion-ref-gate/**— the gate's detection token and fixtures; editing them breaks a fail-closed check.Review
One adversarial pass, reviewer verified genuine and read-only before its findings were used. High 1, medium 0, low 3 — all four fixed in the second commit, each reproduced at source first.
The high was mine and is worth naming: a place-pointer survived in a file this PR already edits (
is private-monorepo, named + deferred, Global Constraints). My first-pass census greppedprivate monorepowith a literal space, so the hyphenated form was invisible to it.orion-ref-gateonly matches the literal repo name, so nothing downstream would have caught it — exactly the reviewer-enforced gap the convention doc describes.Re-running with
private[- ](monorepo|repo|plane)also shows the issue's recorded inventory is incomplete repo-wide —microvm-v2b-guest-supervisor-exec.mdandcompass-manager-role-taxonomy/design.mdcarry hyphenated hits nobody has logged. Those are other lanes' files; filed back to RIG-3247 rather than swept here.Verification
root:markdownlint— 0 errorsdesign-ledger-gate— OK, 318 ledger rows, 133 record headers validorion-ref-gate:check— passroot:ci— 4 tasks pass (39 biome warnings are pre-existing intools/TypeScript, byte-identical on untouched main)private[- ](monorepo|repo|plane)|designed therein all four filesThe record is
Status: Draft, so these are in-place edits; no ledger amendment is required.Closes RIG-3247 for the observability + concepts scope.