Apply the approved role-personality compatibility matrix #42

Closed
opened 2026-07-23 05:58:20 +00:00 by coilyco-ops · 2 comments
Member

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:

  • director: bold, grounded, diplomatic
  • advisor: reflective, curious, candid
  • pm: warm, meticulous, curious
  • designer: imaginative, playful, warm
  • engineer: curious, grounded, meticulous
  • qa: meticulous, candid, playful
  • ops: protective, grounded, reflective
  • sales: charming, energetic, warm
  • social: quirky, playful, optimistic
  • customer-success: nurturing, diplomatic, optimistic

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

  • The embedded source contains all ten roles.
  • Every role names exactly the approved three personalities in the approved order.
  • Seats contain no personality field or default.
  • Tests assert the complete role set and compatibility matrix without duplicating tunable configuration into unrelated test fixtures.
  • Person-contract documentation reflects the ten-role matrix and the separation between roles, seats, and personalities.
  • docs/FEATURES.md reflects the materially expanded embedded person source.
  • ward exec test passes.
  • The commit closes this issue and lands on canonical main.
## 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: * director: bold, grounded, diplomatic * advisor: reflective, curious, candid * pm: warm, meticulous, curious * designer: imaginative, playful, warm * engineer: curious, grounded, meticulous * qa: meticulous, candid, playful * ops: protective, grounded, reflective * sales: charming, energetic, warm * social: quirky, playful, optimistic * customer-success: nurturing, diplomatic, optimistic 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 * The embedded source contains all ten roles. * Every role names exactly the approved three personalities in the approved order. * Seats contain no personality field or default. * Tests assert the complete role set and compatibility matrix without duplicating tunable configuration into unrelated test fixtures. * Person-contract documentation reflects the ten-role matrix and the separation between roles, seats, and personalities. * docs/FEATURES.md reflects the materially expanded embedded person source. * `ward exec test` passes. * The commit closes this issue and lands on canonical main.
Author
Member

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: done ✅ <details><summary>details</summary> 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. </details>
Author
Member

WARDED_WORKFLOW: reservation-released

release details

Run finished with WARDED_WORKFLOW: done ✅.

ward container reap released container engineer-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

<!-- ward-agent-reservation-released --> WARDED_WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARDED_WORKFLOW: done ✅`. `ward container reap` released container `engineer-codex-agent-compose-42` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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/agent-compose#42
No description provided.