Give roles 1 name + pronoun pair, no variance per harness #209

New issue

Closed

opened 2026-08-06 01:19:48 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-08-06 01:19:48 +00:00

Owner

Outcome

Give each role one canonical agent name and pronoun pair. Harness seats become routing selectors and may retain channel or tier metadata, but may not redefine identity.

Migration

Use the first previously declared Core seat identity as the canonical role identity:

Engineer - opal engineer, she
Director - fabled director, she
QA - opal tester, she
DevOps - fabled SRE, she
Designer - opal product designer, she
Portfolio Strategist - fabled strategist, she
Content Creator - opal content creator, she
AI Engineer - opal AI engineer, she

External packages retain legacy per-seat identity compatibility when they do not declare role-level identity.

Acceptance

Core role KDL authors one identity pair and does not repeat names or pronouns on harness entries.
Every Core harness projection, overlay, evaluation pack, catalogue entry, and transcript uses the same role identity.
Selecting another harness changes the selector, channel, or tier only.
Identity cards render the role identity once.
Strict validation rejects mixed role-level and per-seat identity declarations.
Repository validation passes except the already deferred current-scorecard freshness gate tracked in #223.

## Outcome Give each role one canonical agent name and pronoun pair. Harness seats become routing selectors and may retain channel or tier metadata, but may not redefine identity. ## Migration Use the first previously declared Core seat identity as the canonical role identity: * Engineer - opal engineer, she * Director - fabled director, she * QA - opal tester, she * DevOps - fabled SRE, she * Designer - opal product designer, she * Portfolio Strategist - fabled strategist, she * Content Creator - opal content creator, she * AI Engineer - opal AI engineer, she External packages retain legacy per-seat identity compatibility when they do not declare role-level identity. ## Acceptance * Core role KDL authors one identity pair and does not repeat names or pronouns on harness entries. * Every Core harness projection, overlay, evaluation pack, catalogue entry, and transcript uses the same role identity. * Selecting another harness changes the selector, channel, or tier only. * Identity cards render the role identity once. * Strict validation rejects mixed role-level and per-seat identity declarations. * Repository validation passes except the already deferred current-scorecard freshness gate tracked in #223.

coilysiren added the

autonomy

headless

label

2026-08-06 02:01:06 +00:00