coilyco-flight-deck/agentic-os

Watch

remove any usage of `ward` inside of `aosguard` #1041

New issue

Closed

opened 2026-08-13 10:20:24 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-08-13 10:20:24 +00:00

Owner

the tools should not interact at all

coilysiren commented

2026-08-13 10:22:06 +00:00

Author

Owner

So this file

.specgen/guardfiles/aosguard/forgejo.kdl

not only does it mention ward like 20 times... _(which is a smell, if you have to mention ward at all then something is off) ...it also explicitly defers to ward for PR merges instead of implementing merge commands itself. Remove that. Give aosguard the ability to do its own work, like merge PRs

So this file .specgen/guardfiles/aosguard/forgejo.kdl not only does it mention ward like 20 times... _(which is a smell, if you have to mention ward at all then something is off) ...it also explicitly defers to ward for PR merges instead of implementing merge commands itself. Remove that. Give aosguard the ability to do its own work, like merge PRs

coilyco-ops added the

labels

2026-08-17 02:36:45 +00:00

coilyco-ops commented

2026-08-27 03:19:53 +00:00

Member

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901).

Closing: aosguard no longer defers PR merges to Ward, it owns a merge pr leaf of its own. The residual ward mentions in the guardfile are describe-text provenance, not coupling, and Ward being dormant makes them harmless.

This was priority/P3, the default tier that unsure and unscored issues land in, so it had never been positively judged worth keeping. The 2026-08-26 burn-down ranked the whole P3 pool and cut the bottom. Closed here means not on the list, not wrong or worthless.

If this is live work, reopen it. The whole set is recoverable with state:closed label:burndown-2026-08.

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901). Closing: aosguard no longer defers PR merges to Ward, it owns a `merge pr` leaf of its own. The residual `ward` mentions in the guardfile are describe-text provenance, not coupling, and Ward being dormant makes them harmless. This was `priority/P3`, the default tier that unsure and unscored issues land in, so it had never been positively judged worth keeping. The 2026-08-26 burn-down ranked the whole P3 pool and cut the bottom. Closed here means not on the list, not wrong or worthless. If this is live work, reopen it. The whole set is recoverable with `state:closed label:burndown-2026-08`.

coilyco-ops

2026-08-27 03:19:54 +00:00

closed this issue
added the
burndown-2026-08
label

No milestone

No project

No assignees

2 participants

Notifications

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/agentic-os#1041

No description provided.

Rows
Columns

remove any usage of ward inside of aosguard #1041

remove any usage of `ward` inside of `aosguard` #1041