Add composable semantic capabilities for warded roles

coilyco-ops commented

2026-07-09 18:26:49 +00:00

Member

Context: implementation follow-up from #819 and prerequisite cleanup for #817. The consult recommendation and Kai's correction settled on composable semantic capabilities rather than hard-coded role-only permission tiers.

Scope:

Add a ward-owned semantic capability vocabulary: read, project-management, engineering, ops, and admin.
Treat the current named roles as default presets over those capabilities, not as the only possible role model.
Encode the default presets:
- advisor = read
- qa = read
- director = read + project-management
- engineer = read + engineering
- ops = read + ops, once the ops role itself lands
Keep admin as a human/operator aggregate special case, not part of the normal agent baseline.
Separate the capability model from ward-kdl surface tiers. KDL keeps owning guarded edge surfaces, ward owns capability semantics and role behavior.
Add tests covering default role capability resolution and custom composition where the current config surface can support it.

Non-goals:

Do not add the full warded ops role here.
Do not grant broad live-write bundles to existing roles.
Do not perform the full AWS/kubectl/SigNoz bundle split unless a small helper is required for the capability resolver.

Acceptance:

Role capability resolution is explicit and tested.
Existing advisor, qa, director, and engineer behavior remains compatible with the new defaults.
Docs explain the semantic capability names and the KDL edge-surface boundary.
ward exec test passes.

Closes #819 when landed.

Context: implementation follow-up from #819 and prerequisite cleanup for #817. The consult recommendation and Kai's correction settled on composable semantic capabilities rather than hard-coded role-only permission tiers. Scope: * Add a ward-owned semantic capability vocabulary: `read`, `project-management`, `engineering`, `ops`, and `admin`. * Treat the current named roles as default presets over those capabilities, not as the only possible role model. * Encode the default presets: * advisor = read * qa = read * director = read + project-management * engineer = read + engineering * ops = read + ops, once the ops role itself lands * Keep `admin` as a human/operator aggregate special case, not part of the normal agent baseline. * Separate the capability model from ward-kdl surface tiers. KDL keeps owning guarded edge surfaces, ward owns capability semantics and role behavior. * Add tests covering default role capability resolution and custom composition where the current config surface can support it. Non-goals: * Do not add the full `warded ops` role here. * Do not grant broad live-write bundles to existing roles. * Do not perform the full AWS/kubectl/SigNoz bundle split unless a small helper is required for the capability resolver. Acceptance: * Role capability resolution is explicit and tested. * Existing advisor, qa, director, and engineer behavior remains compatible with the new defaults. * Docs explain the semantic capability names and the KDL edge-surface boundary. * `ward exec test` passes. Closes #819 when landed.

coilyco-ops added the

headless

P1

labels

2026-07-09 18:26:49 +00:00

coilyco-ops referenced this issue

2026-07-09 18:26:53 +00:00

Design warded role capability tiers before adding ops #819

coilyco-ops commented

2026-07-09 18:28:35 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-09T18:28:33Z). 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#846 · branch issue-846 · harness codex · workflow pull-request
Run: engineer-codex-ward-846 · ward v0.493.0 · dispatched 2026-07-09T18:28:33Z
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-846` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T18:28:33Z). 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#846` · branch `issue-846` · harness `codex` · workflow `pull-request` - **Run:** `engineer-codex-ward-846` · ward `v0.493.0` · dispatched `2026-07-09T18:28:33Z` - **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 pull request that will close it,

2026-07-09 18:47:32 +00:00

Add composable semantic capabilities for warded roles #854

coilyco-ops commented

2026-07-09 18:51:00 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: pull-request; review summary: skipped: review gate skipped by ~/.ward/config.yaml default

Implemented composable semantic capabilities for warded roles, kept KDL edge surfaces separate, and added tests for default presets plus custom composition.

confidence: high
surprises: golangci-lint flagged cap as a builtin collision in the new helper
follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: pull-request; review summary: skipped: review gate skipped by ~/.ward/config.yaml default Implemented composable semantic capabilities for warded roles, kept KDL edge surfaces separate, and added tests for default presets plus custom composition. confidence: high surprises: golangci-lint flagged cap as a builtin collision in the new helper follow-ups: none </details>

coilyco-ops commented

2026-07-09 20:12:17 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-09T20:12:16Z). 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#846 · branch issue-846 · harness codex · workflow direct-to-main
Run: engineer-codex-ward-846 · ward v0.522.0 · dispatched 2026-07-09T20:12:16Z
Comment thread: 1 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-09T18:51:00Z)
- stripped: @coilyco-ops (2026-07-09T18:28:35Z)

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

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-846` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T20:12:16Z). 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#846` · branch `issue-846` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-ward-846` · ward `v0.522.0` · dispatched `2026-07-09T20:12:16Z` - **Comment thread:** 1 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T18:51:00Z) - stripped: @coilyco-ops (2026-07-09T18:28:35Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.522.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-09 20:23:41 +00:00

merge: integrate main and preserve semantic capabilities

coilyco-ops closed this issue

2026-07-09 20:23:41 +00:00

coilyco-ops commented

2026-07-09 20:24:14 +00:00

Author

Member

WARD-OUTCOME: done

details

workflow: pull-request; review summary: skipped (review gate skipped by ~/.ward/config.yaml default)

Retrospective: merge repair was straightforward after integrating current main.
Confidence: high.
Surprise: origin/main advanced while landing, so the branch needed a second sync before push.
Follow-ups: none.

WARD-OUTCOME: done <details><summary>details</summary> workflow: pull-request; review summary: skipped (review gate skipped by ~/.ward/config.yaml default) Retrospective: merge repair was straightforward after integrating current main. Confidence: high. Surprise: origin/main advanced while landing, so the branch needed a second sync before push. Follow-ups: none. </details>

coilyco-ops referenced this issue

2026-07-09 20:27:38 +00:00

Add composable semantic capabilities for warded roles #854

coilysiren referenced this issue

2026-07-14 15:27:09 +00:00

director should emit colorized, space buffered, visually distinct messages about the categories of actions its performing on startup #1283

Rows
Columns

Add composable semantic capabilities for warded roles #846