Remove the Eco observe ward-kdl layer #821

New issue

Closed

opened 2026-07-09 17:15:54 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-09 17:15:54 +00:00

Member

Goal

Remove the ward-kdl ops eco observe / ward ops eco observe layer entirely.

Kai explicitly rejected the eco observe layer after the design discussion in ward#819. It was never a good idea to add, so do not preserve it as the model for role capability tiers.

Context

ward#819's advisor comment recommended keeping eco-observe as a model. That recommendation is wrong for implementation. The follow-up change should remove the layer rather than build new role semantics around it.

Known references to inspect and remove/update include:

.ward/ward-kdl/ward-kdl.eco-observe.guardfile.kdl
cmd/ward/execassets/ward-kdl.eco-observe.guardfile.kdl
docs/ward-kdl/ward-kdl.eco-observe.guardfile.md
docs/ward-kdl-surface.md
docs/FEATURES.md
docs that describe the director's live kai-server window through ward ops eco observe
any tests or generated docs that expect the observe surface

Scope

Remove the Eco observe guardfile/spec layer from the authored ward-kdl bundle.
Remove generated/embedded copies or regenerate them through the repo's normal ward-kdl path if that is how this repo maintains generated assets.
Remove or rewrite docs that advertise ward-kdl ops eco observe or ward ops eco observe.
Preserve unrelated Eco native/server surfaces unless the code proves they are coupled to observe and must be adjusted for the removal.
Preserve general agent observability, log draining, director surfaces, AWS/tailnet capability handling, and non-Eco docs unless they specifically depend on the Eco observe layer.
Update docs/FEATURES.md because this removes a shipped capability.

Acceptance

rg "eco observe|eco-observe|ward ops eco observe|ward-kdl ops eco observe" no longer finds active user-facing surface references, except historical issue links if they are intentionally retained and clearly not advertised as live behavior.
The Eco observe guardfile is gone from authored and embedded/generated assets.
Tests and generated docs no longer expect the observe surface.
ward exec test passes.
Repo validation expected for ward passes.

ward#819 - design issue whose advisor answer mentioned the layer.
ward#547 - original Eco observe/director live-window work, now being removed.

## Goal Remove the `ward-kdl ops eco observe` / `ward ops eco observe` layer entirely. Kai explicitly rejected the `eco observe` layer after the design discussion in ward#819. It was never a good idea to add, so do not preserve it as the model for role capability tiers. ## Context ward#819's advisor comment recommended keeping `eco-observe` as a model. That recommendation is wrong for implementation. The follow-up change should remove the layer rather than build new role semantics around it. Known references to inspect and remove/update include: * `.ward/ward-kdl/ward-kdl.eco-observe.guardfile.kdl` * `cmd/ward/execassets/ward-kdl.eco-observe.guardfile.kdl` * `docs/ward-kdl/ward-kdl.eco-observe.guardfile.md` * `docs/ward-kdl-surface.md` * `docs/FEATURES.md` * docs that describe the director's live kai-server window through `ward ops eco observe` * any tests or generated docs that expect the observe surface ## Scope * Remove the Eco observe guardfile/spec layer from the authored ward-kdl bundle. * Remove generated/embedded copies or regenerate them through the repo's normal ward-kdl path if that is how this repo maintains generated assets. * Remove or rewrite docs that advertise `ward-kdl ops eco observe` or `ward ops eco observe`. * Preserve unrelated Eco `native`/`server` surfaces unless the code proves they are coupled to observe and must be adjusted for the removal. * Preserve general agent observability, log draining, director surfaces, AWS/tailnet capability handling, and non-Eco docs unless they specifically depend on the Eco observe layer. * Update `docs/FEATURES.md` because this removes a shipped capability. ## Acceptance * `rg "eco observe|eco-observe|ward ops eco observe|ward-kdl ops eco observe"` no longer finds active user-facing surface references, except historical issue links if they are intentionally retained and clearly not advertised as live behavior. * The Eco observe guardfile is gone from authored and embedded/generated assets. * Tests and generated docs no longer expect the observe surface. * `ward exec test` passes. * Repo validation expected for ward passes. ## Related * ward#819 - design issue whose advisor answer mentioned the layer. * ward#547 - original Eco observe/director live-window work, now being removed.

coilyco-ops commented

2026-07-09 17:16:03 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-821 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T17:16:00Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#821 · branch issue-821 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-821 · ward v0.493.0 · dispatched 2026-07-09T17:16:00Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-821` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T17:16:00Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#821` · branch `issue-821` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-821` · ward `v0.493.0` · dispatched `2026-07-09T17:16:00Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-09 17:25:38 +00:00

remove eco observe ward-kdl layer

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 17:26:09 +00:00

Remove the Eco observe ward-kdl layer #822

coilyco-ops closed this issue

2026-07-09 17:30:02 +00:00

coilyco-ops commented

2026-07-09 17:30:26 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: pull-request-and-merge; review summary: skipped because review gate skipped by --skip-review / --no-review-gate
retrospective: removed the authored and embedded Eco observe layer, rewrote the docs, and fixed a flaky broker test that surfaced during validation.
confidence: high
surprises: ward exec test initially tripped on broker env leakage across tests, and golangci-lint wanted the wait condition lifted into the loop header.
follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped because review gate skipped by --skip-review / --no-review-gate retrospective: removed the authored and embedded Eco observe layer, rewrote the docs, and fixed a flaky broker test that surfaced during validation. confidence: high surprises: `ward exec test` initially tripped on broker env leakage across tests, and `golangci-lint` wanted the wait condition lifted into the loop header. follow-ups: none </details>