Apply the approved role-personality compatibility matrix #42
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#42
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
#10
Decision source
Kai approved the complete matrix in #21. Each role owns a curated set of three compatible personalities. Seats remain personality-neutral, and no per-seat default exists.
What to build
Update the embedded person source with the complete ten-role roster and these personality choices:
Designer and customer-success should carry the organizational purpose already specified by agentic-os#602. Existing seats stay unchanged. Do not add seats for roles that have no approved harness names.
Scope boundary
This slice records role policy only. Do not invent favorite colors, personality prose, skill bodies, seat defaults, harness policy, permissions, or Ward changes. Personality definitions that have not landed yet may remain visibly pending through the existing roster behavior.
Acceptance criteria
ward exec testpasses.WARDED_WORKFLOW: done ✅
details
Review: skipped — the in-container review gate was intentionally skipped because the temporary Ward default is pending brokered QA.
workflow: merge-remote-main; review summary: skipped (temporary Ward default pending brokered QA)
Retrospective: Felt straightforward: a focused policy update with direct compatibility coverage.
Confidence: high.
Surprises: documentation caps required concise contract prose.
Follow-ups: land pending personality definitions separately.
WARDED_WORKFLOW: reservation-released
release details
Run finished with
WARDED_WORKFLOW: done ✅.ward container reapreleased containerengineer-codex-agent-compose-42(--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs--override-reservation.— Codex, via
ward agent