docs(agent): design portable operating guidance for Compass (RIG-3903) - #1316
Open
rigel-mintaka wants to merge 4 commits into
Open
rigel-mintaka wants to merge 4 commits into
rigel-mintaka wants to merge 4 commits into
Conversation
Compass carries role prompts and a few operational skills, but its portable operating guidance is incomplete and the useful parts of the existing corpus assume a specific human, forge, tracker, and flat-peer mesh. Record the porting approach: keep procedures in skills and hard invariants in short rules, stay provider-neutral in the core with adapters at the edges, preserve the supervisor/owner/manager tree and async channels, and carry a compact survival kernel through the existing prompt/config delivery seam. The two load-bearing choices (kernel carrier, first-wave adapter scope) are open questions pending the operator decision in RIG-3904.
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
|
Compass engineering docs preview: https://compass-agent-rig-3903-porta.compass-eng-docs.pages.dev Deployed from Changed pages: |
Three findings from the review of #1316. high: the record named the private monorepo six times in a PUBLIC repo, which `tools/orion-ref-gate` fails closed on. Rewritten to "the source wave" throughout, and the boundary is now a Global Constraint naming the gate so the next author sees it. high: the record ignored the merged `compass-batteries-included` record (RIG-1738, DL-140..DL-147), which already froze how this corpus is adapted into Compass skills/rules. Now cited in Problem/Intent, with a new rejected alternative stating the manifest is not reopened: DL-141/DL-142 placement stands and DL-143 owns the exclusion set this extends. medium: the kernel-carrier question asked which carrier to build when one already exists. `config-reader.ts:402-439` globs flat `rules/*.md` and short-circuits SDK rule discovery via `createAgentSession({ rules })`, and `never-merge.md` already carries `alwaysApply: true`. Approach, plan, and task now ride that seam; the question narrows to the one thing still ungrounded — whether always-apply rules re-apply after an in-session compaction — to be settled by reading the SDK compaction path before any seam is designed. Gates: orion-ref-gate clean, rumdl clean, design-ledger-gate OK.
Eight findings from round 2 of the review of #1316. The high one is routed, not fixed. high (routed): the kernel content list walks into the hazard DL-144/BC-7 exists to prevent, and the record never cited it. DL-144 rules that every forwarded always-apply rule self-scopes by role, because the task executor forwards parent rules into subagents but not customTools — it names hold-your-lane, decision-authority and own-your-issue as actively wrong there, and three of the six sketched kernel items are exactly those Manager-only affordances. BC-6 also binds: one rule carrying six invariants is the shape it forbids. This is a design call, so it goes to the operator as RIG-3926 with three options; Approach now marks the list unsettled and the record carries it as a third load-bearing question gating the kernel. medium: the sole-injected-set claim was false at the live callsite. main in cli.ts composes fleet with checkout-discovered rules (fleet least-prominent) rather than passing the mounted set alone; corrected, and the conclusion that the carrier exists survives. medium: replaced a path:line citation with symbol-plus-quote form, per planning-evidence — a frozen record must not carry a decaying line range. medium: narrowing four sites left a fifth contradicting them; the role-prompt alternative no longer asserts reinjection as settled. medium: the gate claim was overstated and its ban ambiguous. orion-ref-gate is a push/schedule backstop, absent from a docs-only PR affected closure, and cannot catch a tokenless path citation; the bullet also appeared to ban the word "operator" one line before requiring it. medium: two DL-143 mis-citations. Adapt-dont-fork is BC-2; DL-143 is the eight-artifact exclusion set, which a later record cites rather than extends in place. low: rules discovery is readdir plus extension filter over .md and .mdc, not a flat .md glob. Gates: rumdl clean, design-ledger-gate OK, orion-ref-gate clean.
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
1 participant
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.
Compass carries role prompts and a few operational skills, but its portable
operating guidance is incomplete and the useful parts of the existing corpus
assume a specific human, forge, tracker, and flat-peer mesh.
Record the porting approach: keep procedures in skills and hard invariants in
short rules, stay provider-neutral in the core with adapters at the edges,
preserve the supervisor/owner/manager tree and async channels, and carry a
compact survival kernel through the existing prompt/config delivery seam. The
two load-bearing choices (kernel carrier, first-wave adapter scope) are open
questions pending the operator decision in RIG-3904.
Ledger-impact: none. This record freezes no decision yet — both its load-bearing questions (kernel carrier/compaction, adapter scope) plus the DL-144/BC-7 kernel-content question are open, the last routed to the operator as RIG-3926. The DL rows land when those resolve.