Skip to content

docs(concepts): tighten managed-boundary naming rule + capability-vs-product-end-state (RIG-3153) - #839

Merged
mattwilkinsonn merged 1 commit into
mainfrom
compass-obs/managed-boundary-naming-rule
Sep 3, 2026
Merged

docs(concepts): tighten managed-boundary naming rule + capability-vs-product-end-state (RIG-3153)#839
mattwilkinsonn merged 1 commit into
mainfrom
compass-obs/managed-boundary-naming-rule

Conversation

@rigel-mintaka

@rigel-mintaka rigel-mintaka commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

This PR is part of a stack containing 2 PRs:

  1. main
  2. "docs(concepts): tighten managed-boundary naming rule + capability-vs-product-end-state (RIG-3153)" (this PR)
  3. docs(infra): design Compass self-host runner + adoption strategy (RIG-3070) #804

The public compass repo must not carry the managed product's end-state or rollout, and must never name or point at the private repo as a place. Tighten the ratified convention:

  • self-host-and-managed.md: ban repo place-pointers (was: explicitly permitted "the private monorepo"); add the capability-vs-product-end-state rule (managed capability in the core is fine, framed as core capability; the managed product's end-state/rollout stays out).
  • oss-core-managed-boundary: scrub place-pointers from framing, boundary-test No-branch, and examples-table column (-> "managed plane, out of tree").

Pairs with skill://compass-managed-boundary (the agent trigger).

Spec-impact: none. Refs RIG-3153

Co-authored-by: Matt Wilkinson matt@rigel.build

…product-end-state (RIG-3153)

The public compass repo must not carry the managed product's end-state or rollout, and must never name or point at the private repo as a place. Tighten the ratified convention:

- self-host-and-managed.md: ban repo place-pointers (was: explicitly permitted "the private monorepo"); add the capability-vs-product-end-state rule (managed capability in the core is fine, framed as core capability; the managed product's end-state/rollout stays out).
- oss-core-managed-boundary: scrub place-pointers from framing, boundary-test No-branch, and examples-table column (-> "managed plane, out of tree").

Pairs with skill://compass-managed-boundary (the agent trigger).

Spec-impact: none. Refs RIG-3153

Co-authored-by: Matt Wilkinson <matt@rigel.build>
@linear-code

linear-code Bot commented Sep 2, 2026

Copy link
Copy Markdown

RIG-3153

@trunk-io

trunk-io Bot commented Sep 2, 2026

Copy link
Copy Markdown

😎 This pull request was merged.

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

Compass engineering docs preview: https://compass-obs-managed-boundary.compass-eng-docs.pages.dev

Deployed from compass-obs/managed-boundary-naming-rule at 52be604.

Changed pages:

@mattwilkinsonn
mattwilkinsonn marked this pull request as ready for review September 3, 2026 01:14
@mattwilkinsonn
mattwilkinsonn self-requested a review as a code owner September 3, 2026 01:14
@mattwilkinsonn
mattwilkinsonn merged commit 2625040 into main Sep 3, 2026
15 checks passed
@mattwilkinsonn
mattwilkinsonn deleted the compass-obs/managed-boundary-naming-rule branch September 3, 2026 01:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants