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

Closed
opened 2026-07-10 20:48:29 +00:00 by coilysiren · 3 comments
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.
Owner

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.

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.
Owner

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.
Owner

Tracker reconciliation for #1574:

  • 66aea8b2b3 removed Ward's operator and specgen surface plus the old .ward/ward-kdl tree.
  • 88e65d40cb removed the remaining generated KDL assets and embedded Ward's native role policy directly.
  • Current source contains no active old .ward/ward-kdl, cmd/ward-kdl, or examples/ward-specs surface.
  • Current architecture documentation assigns operator specs to AOSGuard.

The agent is closing this completed issue based on landed source and current docs.

Codex, via advisor surface

Tracker reconciliation for https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1574: * https://forgejo.coilysiren.me/coilyco-flight-deck/ward/commit/66aea8b2b38bc2823d310eef3b7b23766e3550b5 removed Ward's operator and specgen surface plus the old `.ward/ward-kdl` tree. * https://forgejo.coilysiren.me/coilyco-flight-deck/ward/commit/88e65d40cb387bdd0a201df65e557b4ac08fab02 removed the remaining generated KDL assets and embedded Ward's native role policy directly. * Current source contains no active old `.ward/ward-kdl`, `cmd/ward-kdl`, or `examples/ward-specs` surface. * Current architecture documentation assigns operator specs to AOSGuard. The agent is closing this completed issue based on landed source and current docs. <!-- ward-agent-signature --> Codex, via advisor surface
Commenting is not possible because the repository is archived.
No project
No assignees
2 participants
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/ward#1080
No description provided.