ward#503 step 4: neutralize .ward/ward-kdl + drop the release fail-safe (blocked on aos#332 + tap#3) #645

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

ward#503 step 4 - the final flip (BLOCKED, do not dispatch until prerequisites land)

Neutralize ward's tracked bundle so ward carries zero coilyco/personal config, sourcing its deployment surface entirely from the aos-authored ward-specs bundle at build.

Blocked on (both must land first, or this breaks the fleet)

agentic-os#332 - aos homes ward's complete current bundle and publishes a fresh ward-specs release, so the overlay is a live no-op (aos no longer lags ward).
coilyco-flight-deck/homebrew-tap #3 - the brew formula overlays that aos release before go build. Until this lands, a source-built brew ward from a neutralized tree ships neutral.

Both build sites (release.yml via ward#644, tap via #3) must overlay before the tree goes neutral. This is the ward#503 no-op-then-flip invariant.

Do (once unblocked)

Replace ward's .ward/ward-kdl/ coilyco values with the neutral examples/ward-specs/ bundle (reverse-overlay the neutral bundle, then make build-ward-kdl / re-derive the embeds + golden), so TestExampleBundleHasNoCoilycoValues covers the shipped tree.
Remove the release.yml fail-safe revert added in ward#644 (4dd986d): once aos is authoritative and current, the "restore ward's committed embeds when aos lags" path is obsolete and must go, or the neutral tree can never actually ship. Keep the fail-closed coilyco-coupling assertion on the overlaid (aos-sourced) bundle.
Confirm a release build produces byte-identical coilyco binaries sourced from aos, with a neutral tree.

ward#644 (step 3, the release overlay + the fail-safe this removes), agentic-os#332, homebrew-tap#3, ward#503, ward#453. Filed from the read-only director surface (she/her).

## ward#503 step 4 - the final flip (BLOCKED, do not dispatch until prerequisites land) Neutralize ward's tracked bundle so ward carries **zero** coilyco/personal config, sourcing its deployment surface entirely from the aos-authored ward-specs bundle at build. ## Blocked on (both must land first, or this breaks the fleet) 1. **agentic-os#332** - aos homes ward's complete current bundle and publishes a fresh `ward-specs` release, so the overlay is a **live no-op** (aos no longer lags ward). 2. **coilyco-flight-deck/homebrew-tap #3** - the brew formula overlays that aos release before `go build`. Until this lands, a source-built brew ward from a neutralized tree ships neutral. Both build sites (release.yml via ward#644, tap via #3) must overlay **before** the tree goes neutral. This is the ward#503 no-op-then-flip invariant. ## Do (once unblocked) - Replace ward's `.ward/ward-kdl/` coilyco values with the neutral `examples/ward-specs/` bundle (reverse-overlay the neutral bundle, then `make build-ward-kdl` / re-derive the embeds + golden), so `TestExampleBundleHasNoCoilycoValues` covers the shipped tree. - **Remove the release.yml fail-safe revert** added in ward#644 (`4dd986d`): once aos is authoritative and current, the "restore ward's committed embeds when aos lags" path is obsolete and must go, or the neutral tree can never actually ship. Keep the fail-closed coilyco-coupling assertion on the **overlaid** (aos-sourced) bundle. - Confirm a release build produces byte-identical coilyco binaries sourced from aos, with a neutral tree. ## Related ward#644 (step 3, the release overlay + the fail-safe this removes), agentic-os#332, homebrew-tap#3, ward#503, ward#453. Filed from the read-only director surface (she/her).

coilyco-ops added the

interactive

labels

2026-07-07 22:44:42 +00:00

coilyco-ops referenced this issue

2026-07-08 03:32:51 +00:00

Config-driven ward: the fs.FS-at-launch config-resolve seam (#650-1, foundational) #653

coilyco-ops referenced this issue

2026-07-08 03:33:46 +00:00

[epic] Config-driven ward: one precompiled binary, personal config resolved live from a git ref (supersedes the build-variant matrix) #650

coilyco-ops commented

2026-07-08 03:33:46 +00:00

Author

Member

Superseded by the config-driven ward epic (#650). #650 drops the build-time overlay entirely: there is no reverse-overlay of a neutral bundle at build and no release.yml fail-safe to remove, because config is resolved live from a git ref rather than baked at build. This issue's intent - ward's tree carries zero coilyco/personal config, with a safe baked neutral default - lands in #653 ("keep the baked neutral default"). Its mechanism (build overlay + tap from-source, blocked on homebrew-tap#3) is dropped. Closing as superseded. Filed from the read-only director surface (she/her).

Superseded by the config-driven ward epic (#650). #650 drops the build-time overlay entirely: there is no reverse-overlay of a neutral bundle at build and no release.yml fail-safe to remove, because config is resolved **live from a git ref** rather than baked at build. This issue's **intent** - ward's tree carries zero coilyco/personal config, with a safe baked neutral default - lands in **#653** ("keep the baked neutral default"). Its **mechanism** (build overlay + tap from-source, blocked on homebrew-tap#3) is dropped. Closing as superseded. Filed from the read-only director surface (she/her).

coilyco-ops closed this issue

2026-07-08 03:33:47 +00:00