coilyco-flight-deck/homebrew-tap
2
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Overlay the aos ward-specs bundle in Formula/ward.rb before go build (ward#503 step 2, human gate) #3

New issue
Closed
opened 2026-07-07 22:44:42 +00:00 by coilyco-ops · 1 comment
coilyco-ops commented 2026-07-07 22:44:42 +00:00
Member
Copy link

Human gate (Kai) - ward#503 step 2

The fleet's brew install ward builds ward from source (go build ./cmd/ward in Formula/ward.rb), embedding whatever .ward/ward-kdl/ is in the ward source tarball via go:embed. Today that tree still carries the coilyco values, so brew ward is correct. The moment ward's tree is neutralized (ward#503 step 4), a source-built brew ward would embed the NEUTRAL bundle and the fleet loses its coilyco config. This formula must overlay the aos ward-specs bundle before go build first.

Per ward#503, the tap is canonically on GitHub and this is your gate - no autonomous run touches the fleet install root. This issue carries the exact change so it is a paste-and-PR.

The change (add before the existing system "go", "build" ...)

Add a pinned resource + overlay. Pin to the fresh aos release that agentic-os#332 publishes (NOT v0.202.0, which is stale - wait for the sync to cut a new ward-specs-<newtag>), and fill its .sha256:

  resource "ward-specs" do
    url "https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/releases/download/<NEWTAG>/ward-specs-<NEWTAG>.tar.gz"
    sha256 "<sha256 from the .sha256 sidecar>"
  end

  def install
    # ... existing ENV[...] lines ...
    # Overlay the aos-authored coilyco bundle onto the neutral tree before build.
    resource("ward-specs").stage do
      cp_r Dir["*"], buildpath/".ward/ward-kdl/"
    end
    # then the existing: system "go", "build", ...

Match the exact extract layout to what agentic-os#332 ships (the tarball's internal path) and to ward's assets-dir convention (ward#453). Mirror the fail-closed spirit of ward's release overlay: a blank/missing resource must fail the build, never silently ship neutral.

Sequencing

Do this after agentic-os#332 lands and publishes its new ward-specs release (so the pin exists), and before ward#503 step 4 (the tree neutralization) is dispatched. Landing this is what unblocks the final neutralization.

Related

agentic-os#332 (the aos bundle this pins to), ward#644 (the release-binary overlay, the sibling of this for the non-brew install paths), ward#503 (the plan). Filed from the read-only director surface (she/her).

## Human gate (Kai) - ward#503 step 2 The fleet's `brew install ward` builds ward **from source** (`go build ./cmd/ward` in `Formula/ward.rb`), embedding whatever `.ward/ward-kdl/` is in the ward source tarball via `go:embed`. Today that tree still carries the coilyco values, so brew ward is correct. **The moment ward's tree is neutralized (ward#503 step 4), a source-built brew ward would embed the NEUTRAL bundle and the fleet loses its coilyco config.** This formula must overlay the aos ward-specs bundle **before** `go build` first. Per ward#503, the tap is canonically on **GitHub** and this is **your** gate - no autonomous run touches the fleet install root. This issue carries the exact change so it is a paste-and-PR. ## The change (add before the existing `system "go", "build" ...`) Add a pinned resource + overlay. **Pin to the fresh aos release** that agentic-os#332 publishes (NOT v0.202.0, which is stale - wait for the sync to cut a new `ward-specs-<newtag>`), and fill its `.sha256`: ```ruby resource "ward-specs" do url "https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/releases/download/<NEWTAG>/ward-specs-<NEWTAG>.tar.gz" sha256 "<sha256 from the .sha256 sidecar>" end def install # ... existing ENV[...] lines ... # Overlay the aos-authored coilyco bundle onto the neutral tree before build. resource("ward-specs").stage do cp_r Dir["*"], buildpath/".ward/ward-kdl/" end # then the existing: system "go", "build", ... ``` Match the exact extract layout to what agentic-os#332 ships (the tarball's internal path) and to ward's assets-dir convention (ward#453). Mirror the fail-closed spirit of ward's release overlay: a blank/missing resource must fail the build, never silently ship neutral. ## Sequencing Do this **after** agentic-os#332 lands and publishes its new `ward-specs` release (so the pin exists), and **before** ward#503 step 4 (the tree neutralization) is dispatched. Landing this is what unblocks the final neutralization. ## Related agentic-os#332 (the aos bundle this pins to), ward#644 (the release-binary overlay, the sibling of this for the non-brew install paths), ward#503 (the plan). Filed from the read-only director surface (she/her).
coilyco-ops commented 2026-07-08 03:33:58 +00:00
Author
Member
Copy link

Superseded by the config-driven ward epic (ward#650). #650 settles that ward ships one precompiled, byte-identical binary per platform - no build-from-source at install, no per-variant builds, no bundle overlay before go build. The brew formula becomes download-and-verify of the released artifact (the existing bump-tap-formula url+sha256 rewrite stays), and per-user config is resolved live at runtime via WARD_CONFIG_REF, not baked. Tracked ward-side in ward#657. Closing as superseded. Filed from the read-only director surface (she/her).

Superseded by the config-driven ward epic (ward#650). #650 settles that ward ships **one precompiled, byte-identical binary per platform** - no build-from-source at install, no per-variant builds, no bundle overlay before `go build`. The brew formula becomes **download-and-verify** of the released artifact (the existing `bump-tap-formula` url+sha256 rewrite stays), and per-user config is resolved live at runtime via `WARD_CONFIG_REF`, not baked. Tracked ward-side in **ward#657**. Closing as superseded. Filed from the read-only director surface (she/her).
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/homebrew-tap#3
No description provided.