Audit and remove remaining baked coilyco fleet configuration from ward

coilyco-ops commented

2026-07-22 08:41:47 +00:00

Member

Ward still carries multiple product/fleet-specific defaults and config overlays that make the runtime behave like Kai's fleet is the product default instead of one selected deployment bundle.

This came up after discovering that a director Codex surface launched from ward's embedded fleet overlay (gpt-5.5 / high) instead of the selected agentic-os/.ward/roles.kdl overlay (gpt-5.6-sol / xhigh), filed narrowly as #1497. The broader concern is that there is still a backlog of custom/coilyco configuration in ward itself that should be ripped out or made explicitly external.

Observed local evidence from /substrate/ward:

.ward/ward-kdl/ward-kdl.fleet.kdl and cmd/ward/fleetassets/fleet.generated.kdl embed per-role model tuning, including director Codex gpt-5.5 / high.
.ward/ward-kdl/ward-kdl.defaults.kdl still names forgejo.coilysiren.me/coilyco-flight-deck/ward, trusted owner coilysiren, and coilysiren/* GitHub repo policy.
README says ward ships defaults for forgejo.coilysiren.me and coily-owned orgs.
docs/config-source.md says runtime WARD_CONFIG_REF affects edge/operator surfaces but core agent control-plane paths can fall back to baked defaults.
docs/FEATURES.md still records that runtime bundles do not own the core control plane.
Open related slices include #1495 (Tailscale removal), #1487 (trust gate evaluation/removal), #1489 (set WARD_CONFIG_REF via user config), #1497 (role overlay mismatch), and #1070 (remove runtime reliance on ward specgen).

Goal:

Audit active source, embedded assets, tests, generated docs, and user-facing docs for remaining baked coilyco/fleet-specific assumptions. Produce and begin executing a removal plan that makes ward product-neutral by default, with Kai/coilyco specifics living in the selected runtime bundle, infrastructure, or deployment config.

Acceptance:

Inventory every remaining active baked coilyco/custom config path, including whether it is runtime behavior, docs-only, test fixture, example-safe placeholder, or generated artifact.
Decide which defaults may remain as neutral examples and which must move behind WARD_CONFIG_REF, user config, infrastructure, or explicit CLI flags.
File focused child issues for chunks that should not be landed in one PR.
Implement the first safe removal slice if one is obvious and low-risk.
Make the docs explain the intended config source contract without implying that ward's embedded fleet overlay is authoritative over the selected bundle.
Do not break generic warded launches or the existing release path while removing coilyco-specific assumptions.

This is intentionally broader than #1497; that issue can repair the immediate Codex director model mismatch while this one drains the remaining custom-config backlog.

Ward still carries multiple product/fleet-specific defaults and config overlays that make the runtime behave like Kai's fleet is the product default instead of one selected deployment bundle. This came up after discovering that a director Codex surface launched from ward's embedded fleet overlay (`gpt-5.5` / `high`) instead of the selected `agentic-os/.ward/roles.kdl` overlay (`gpt-5.6-sol` / `xhigh`), filed narrowly as #1497. The broader concern is that there is still a backlog of custom/coilyco configuration in ward itself that should be ripped out or made explicitly external. Observed local evidence from `/substrate/ward`: - `.ward/ward-kdl/ward-kdl.fleet.kdl` and `cmd/ward/fleetassets/fleet.generated.kdl` embed per-role model tuning, including director Codex `gpt-5.5` / `high`. - `.ward/ward-kdl/ward-kdl.defaults.kdl` still names `forgejo.coilysiren.me/coilyco-flight-deck/ward`, trusted owner `coilysiren`, and `coilysiren/*` GitHub repo policy. - README says ward ships defaults for `forgejo.coilysiren.me` and coily-owned orgs. - `docs/config-source.md` says runtime `WARD_CONFIG_REF` affects edge/operator surfaces but core agent control-plane paths can fall back to baked defaults. - `docs/FEATURES.md` still records that runtime bundles do not own the core control plane. - Open related slices include #1495 (Tailscale removal), #1487 (trust gate evaluation/removal), #1489 (set WARD_CONFIG_REF via user config), #1497 (role overlay mismatch), and #1070 (remove runtime reliance on ward specgen). Goal: Audit active source, embedded assets, tests, generated docs, and user-facing docs for remaining baked coilyco/fleet-specific assumptions. Produce and begin executing a removal plan that makes ward product-neutral by default, with Kai/coilyco specifics living in the selected runtime bundle, infrastructure, or deployment config. Acceptance: - Inventory every remaining active baked coilyco/custom config path, including whether it is runtime behavior, docs-only, test fixture, example-safe placeholder, or generated artifact. - Decide which defaults may remain as neutral examples and which must move behind `WARD_CONFIG_REF`, user config, infrastructure, or explicit CLI flags. - File focused child issues for chunks that should not be landed in one PR. - Implement the first safe removal slice if one is obvious and low-risk. - Make the docs explain the intended config source contract without implying that ward's embedded fleet overlay is authoritative over the selected bundle. - Do not break generic warded launches or the existing release path while removing coilyco-specific assumptions. This is intentionally broader than #1497; that issue can repair the immediate Codex director model mismatch while this one drains the remaining custom-config backlog.

coilyco-ops referenced this issue

2026-07-22 08:44:36 +00:00

Codex engineer launch fails when prompt begins with dash-prefixed pre-flight text #1499

coilyco-ops referenced this issue

2026-07-22 08:59:26 +00:00

Remove embedded local harness model defaults #1504

coilyco-ops commented

2026-07-22 08:59:38 +00:00

Author

Member

Focused child issue filed for the local-harness slice: #1504. Kai clarified Ward should not embed a Goose/Opencode model default at all, because a local model name is deployment-local and must come from selected bundle/user config/explicit override or fail closed.

Focused child issue filed for the local-harness slice: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1504. Kai clarified Ward should not embed a Goose/Opencode model default at all, because a local model name is deployment-local and must come from selected bundle/user config/explicit override or fail closed.

coilyco-ops referenced this issue

2026-07-23 05:00:17 +00:00

Scope the GitHub authority exception to coilysiren/coilysiren, not coilysiren/* #1520

~~coilyco-ops referenced this issue 2026-07-23 06:51:40 +00:00~~

Remove the last kubectl policy residues after the operator split #1528

coilyco-ops commented

2026-07-23 17:47:40 +00:00

Author

Member

Rescue review found no engineer-authored audit work to preserve.

Run boundary - Ward v0.785.0 passed the dash-prefixed prompt without a separator, so Codex exited with a usage error before the model launched. Ward #1499 owns that launch-path defect and is closed.
Repository state - the engineer produced no source analysis, inventory, diff, commit, branch, pull request, or verification.
Durable state - the existing thread already preserves the useful follow-through in #1504 and the decision that Ward must not embed a Goose or Opencode model default.
Redispatch - a new engineer must start from the current ticket and current Ward after the stale reservation is cleared.

Rescue review found no engineer-authored audit work to preserve. * Run boundary - Ward v0.785.0 passed the dash-prefixed prompt without a separator, so Codex exited with a usage error before the model launched. Ward #1499 owns that launch-path defect and is closed. * Repository state - the engineer produced no source analysis, inventory, diff, commit, branch, pull request, or verification. * Durable state - the existing thread already preserves the useful follow-through in #1504 and the decision that Ward must not embed a Goose or Opencode model default. * Redispatch - a new engineer must start from the current ticket and current Ward after the stale reservation is cleared.

coilyco-ops commented

2026-07-28 08:58:57 +00:00

Author

Member

WARD-WORKFLOW: reservation-released

release details

Run never started. ward container reap released container engineer-codex-ward-1498 (--harness codex): it exited without launching the agent (smoke-test death, ward#222/#264/#595), so it did no work and the launch intent it took is retracted. Nothing is running on this issue. It needs re-dispatch. A ward agent director re-queues it automatically. A manual ward agent retry no longer needs --override-reservation.

— Codex, via ward agent

WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run never started. `ward container reap` released container `engineer-codex-ward-1498` (`--harness codex`): it exited without launching the agent (smoke-test death, ward#222/#264/#595), so it did no work and the launch intent it took is retracted. Nothing is running on this issue. It needs re-dispatch. A `ward agent director` re-queues it automatically. A manual `ward agent` retry no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-29 03:23:24 +00:00

Remove flexible roles and KDL runtime configuration from Ward #1615

coilyco-ops added the

labels

2026-07-29 03:47:16 +00:00

coilyco-ops closed this issue

2026-07-29 06:04:44 +00:00