Skip to content

docs(design): record RIG-2336 forks-reversal OQ rulings (amendment) - #450

Merged
mattwilkinsonn merged 1 commit into
mainfrom
compass-repo/rig-2336-oq-resolutions
Aug 21, 2026
Merged

docs(design): record RIG-2336 forks-reversal OQ rulings (amendment)#450
mattwilkinsonn merged 1 commit into
mainfrom
compass-repo/rig-2336-oq-resolutions

Conversation

@rigel-mintaka

Copy link
Copy Markdown
Contributor

The frozen forks-reversal record (PR #434, merged 9d48f9a) shipped with its two
load-bearing Open Questions unresolved — the pre-freeze ruling gate did not run
before merge. A frozen record is never edited in place (skill://design: no
folding-in after merge; a later change adds a new record), so this amendment
records the binding rulings that supersede the frozen record's OQ1 and OQ2.

  • OQ1 (oh-my-pi): CONSUME a Rigel-tagged npm release — cut a Rigel-owned tagged
    npm release of the coding-agent package and repoint the credential-denylist
    generator to consume it. A third shape distinct from the frozen record's
    recommended "drop + upstream npm" and its "github: repo pin" fallback; the
    denylist tracks a Rigel-cut release. Shapes L3.
  • OQ2 (raw nix run sites): INSTALL the fork tools, pinned. The six raw-CLI sites
    that bypass devenv.lock install the fork devenv + skopeo-nix2container from the
    lockfile-pinned github:RigelBuild/ input and invoke by explicit name — no
    raw nix run path:... / <rev> literal remains. Pin lives in one place (the
    lockfile); dissolves the drift problem rather than gating it with a wrapper
    flake or a CI assert. Shapes L1/L2.

OQ3 (non-load-bearing) and L0a/L0b/L4 unchanged from the frozen record.

Refs RIG-2336

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

@linear-code

linear-code Bot commented Aug 21, 2026

Copy link
Copy Markdown

RIG-2336

@rigel-mintaka
rigel-mintaka force-pushed the compass-repo/rig-2336-oq-resolutions branch from 5581758 to a01a69e Compare August 21, 2026 05:04
@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown

Compass engineering docs preview: https://compass-repo-rig-2336-oq-res.compass-eng-docs.pages.dev

Deployed from compass-repo/rig-2336-oq-resolutions at aa5f12f.

Changed pages:

The frozen forks-reversal record (PR #434, merged 9d48f9a) shipped with its two
load-bearing Open Questions unresolved — the pre-freeze ruling gate did not run
before merge. A frozen record is never edited in place (skill://design: no
folding-in after merge; a later change adds a new record), so this amendment
records the binding rulings that supersede the frozen record's OQ1 and OQ2.

- OQ1 (oh-my-pi): CONSUME a Rigel-tagged npm release — cut a Rigel-owned tagged
  npm release of the coding-agent package and repoint the credential-denylist
  generator to consume it. A third shape distinct from the frozen record's
  recommended "drop + upstream npm" and its "github: repo pin" fallback; the
  denylist tracks a Rigel-cut release. Shapes L3.
- OQ2 (raw nix run sites): INSTALL the fork tools, pinned. The six raw-CLI sites
  that bypass devenv.lock install the fork devenv + skopeo-nix2container from the
  lockfile-pinned github:RigelBuild/<fork> input and invoke by explicit name — no
  raw `nix run path:...` / `<rev>` literal remains. Pin lives in one place (the
  lockfile); dissolves the drift problem rather than gating it with a wrapper
  flake or a CI assert. Shapes L1/L2.

OQ3 (non-load-bearing) and L0a/L0b/L4 unchanged from the frozen record.

Refs RIG-2336

Co-authored-by: Matt Wilkinson <matt@rigel.build>
@rigel-mintaka
rigel-mintaka force-pushed the compass-repo/rig-2336-oq-resolutions branch from a01a69e to aa5f12f Compare August 21, 2026 05:12
@mattwilkinsonn
mattwilkinsonn merged commit 85aab90 into main Aug 21, 2026
4 checks passed
@mattwilkinsonn
mattwilkinsonn deleted the compass-repo/rig-2336-oq-resolutions branch August 21, 2026 16:24
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