catalog roles mislabels the personality meld as "boundary:" #322

Closed
opened 2026-08-23 22:28:30 +00:00 by coilyco-ops · 1 comment
Member

Observed

agent-compose catalog roles (v2.39.0) prints the role's personality meld under the label boundary:.

platform // role-platform // Build and land the foundational software the rest of the estate is built on. // boundary: tenacious, grounded // color: #9c8b31
devrel // role-devrel // Turn real portfolio work and audience evidence into accurate content, respectful conversations, and informed commitments. // boundary: warm, outward // color: #f7ab5d

tenacious, grounded, warm, and outward are personality slugs. They are not boundaries.

Expected

The real boundaries for a role are the four boundary-* slugs the identity card carries, for example boundary-suggest-external-comms, boundary-modify-live-backend, boundary-seek-external-validation, boundary-build-foundational-software.

The field should read meld: or personality:, whichever matches the vocabulary the rest of the CLI uses.

Why it matters

The two concepts do different work. A personality tunes attention and voice, a boundary governs who is allowed to take an action. Printing one under the other's name teaches the wrong model to every reader of this command, and it is the first surface a newcomer hits.

Found while scripting a terminal demo that runs catalog roles on camera.

Scope

One label string. No data change.

## Observed `agent-compose catalog roles` (v2.39.0) prints the role's personality meld under the label `boundary:`. ``` platform // role-platform // Build and land the foundational software the rest of the estate is built on. // boundary: tenacious, grounded // color: #9c8b31 devrel // role-devrel // Turn real portfolio work and audience evidence into accurate content, respectful conversations, and informed commitments. // boundary: warm, outward // color: #f7ab5d ``` `tenacious`, `grounded`, `warm`, and `outward` are personality slugs. They are not boundaries. ## Expected The real boundaries for a role are the four `boundary-*` slugs the identity card carries, for example `boundary-suggest-external-comms`, `boundary-modify-live-backend`, `boundary-seek-external-validation`, `boundary-build-foundational-software`. The field should read `meld:` or `personality:`, whichever matches the vocabulary the rest of the CLI uses. ## Why it matters The two concepts do different work. A personality tunes attention and voice, a boundary governs who is allowed to take an action. Printing one under the other's name teaches the wrong model to every reader of this command, and it is the first surface a newcomer hits. Found while scripting a terminal demo that runs `catalog roles` on camera. ## Scope One label string. No data change.
Author
Member

Fixed on main in 89b81ae.

The label now reads personalities:, picked over meld: because it matches the personalities JSON field on the role item and the catalog personalities subcommand, which is the vocabulary the rest of the CLI already uses.

platform // role-platform // Build and land the foundational software. // personalities: tenacious, grounded // color: #9c8b31

The format string moved into catalogRoleLine so it could be asserted, and TestCatalogRoleLineLabelsThePersonalityMeld now fails if the word boundary returns to that line. No data change, and docs/skill-catalogues.md never quoted the text form so it needed no edit.

just test green.

Fixed on `main` in `89b81ae`. The label now reads `personalities:`, picked over `meld:` because it matches the `personalities` JSON field on the role item and the `catalog personalities` subcommand, which is the vocabulary the rest of the CLI already uses. ``` platform // role-platform // Build and land the foundational software. // personalities: tenacious, grounded // color: #9c8b31 ``` The format string moved into `catalogRoleLine` so it could be asserted, and `TestCatalogRoleLineLabelsThePersonalityMeld` now fails if the word `boundary` returns to that line. No data change, and `docs/skill-catalogues.md` never quoted the text form so it needed no edit. `just test` green.
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#322
No description provided.