Remove the KDL specs that keep getting added back by engineers #1080

New issue

Open

opened 2026-07-10 20:48:29 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-10 20:48:29 +00:00

Owner

The problem

#1060

There's several (I think) issues about removing them

Proposed change

Alternatives considered

Before filing

I searched existing issues and this is not a duplicate.
This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

### The problem https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1060 There's several (I think) issues about removing them ### Proposed change // ### Alternatives considered // ### Before filing - [x] I searched existing issues and this is not a duplicate. - [x] This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

coilyco-ops added the

headless

labels

2026-07-14 06:50:12 +00:00

coilyco-ops added this to the warded control plane coherence milestone

2026-07-15 05:14:54 +00:00

coilyco-ops commented

2026-07-15 06:55:29 +00:00

Member

Release triage note from Kai on 2026-07-15: headless carry is valid. Remove stale or generated KDL specs that keep being restored, and add a guardrail, generation rule, or doc/test note that prevents engineers from adding them back.

coilyco-ops commented

2026-07-15 07:16:33 +00:00

Member

WARD-TRIAGE: warded control plane coherence milestone

This issue is part of the warded control plane coherence sprint. The release thesis is to make warded feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run.

For this sprint, headless means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.

WARD-TRIAGE: warded control plane coherence milestone This issue is part of the `warded control plane coherence` sprint. The release thesis is to make `warded` feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run. For this sprint, `headless` means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.