Design the composition between specgen ward commands and defined at the user level vs the platform level #1114

New issue

Open

opened 2026-07-11 20:10:27 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-07-11 20:10:27 +00:00

Owner

The problem

The access control patterns of forges and issue trackers is confusing

Proposed change

For a safe given forge action, like say issue lookup, an agent should have (in essence) 3 ways to access that info

the broker passing in relevant issue info on launch. This is currently less sophisticated than I would like but feature complete from the POV of this issue
The kdl config for that agents role responsibility definition (ex: project mgmt) should attach a spengen guard files that attach to ward. So ward < stuff > issue view
The kdl specgen the user hand rolls should grant that permission as well

The relation between these 3 things is currently unclear to me. And I'm not even sure we even do thing 2 yet? At minimum we should document this

Alternatives considered

No response

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 The access control patterns of forges and issue trackers is confusing ### Proposed change For a safe given forge action, like say issue lookup, an agent should have (in essence) 3 ways to access that info 1. the broker passing in relevant issue info on launch. This is currently less sophisticated than I would like but feature complete from the POV of this issue 2. The kdl config for that agents role responsibility definition (ex: project mgmt) should attach a spengen guard files that attach to ward. So `ward < stuff > issue view` 3. The kdl specgen the user hand rolls should grant that permission as well The relation between these 3 things is currently unclear to me. And I'm not even sure we even do thing 2 yet? At minimum we should document this ### Alternatives considered _No response_ ### 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.