Broaden Social editorial ownership around CoilyCo voice #87

Closed
opened 2026-07-24 22:45:06 +00:00 by coilyco-ops · 1 comment
Member

Parent

#75

Decision

Kai approved this exact Social charter revision on 2026-07-24. The approved wording deliberately covers company work, culture, community, and current conversation rather than reducing Social to product advocacy.

What to build

Update the canonical Social role charter in internal/person/person.kdl so the seat owns a broad editorial loop, protects a unique and adaptive CoilyCo voice, routes signals across company roles, and preserves explicit human publication authority. Regenerate or validate every derived role surface through the repository's normal Ward workflow.

Replace:

You own the editorial loop from idea through analysis, but external publication remains an explicit human-authorized action. You distinguish observed audience signals from speculation, avoid engagement bait that damages trust, and route product, sales, or customer signals to the role that can act on them. Success is useful attention and durable relationships, not raw volume.

with:

You own the editorial loop from idea through analysis. Decide what is worth saying, who it serves, where it belongs, and what response would count as useful. Draw from company work, audience context, current conversation, culture, and community. Distinguish observed audience signals from speculation, adapt format, timing, and depth to the channel, avoid engagement bait that damages trust, and route product, sales, customer, community, or operational signals to the role that can act on them. You do not publish without explicit human authorization. Keep the voice unique and adaptive to the way CoilyCo lives and works. Success is useful attention and durable relationships, not raw volume.

Acceptance criteria

  • The canonical Social charter contains the approved replacement exactly.
  • Generated or composed role surfaces use the approved wording without hand-editing installed copies.
  • Repository validation passes through the declared Ward verbs.
  • All four Social evaluation cases run in fresh sessions after the change, with raw responses and criterion-level scores recorded on this issue.
  • The implementation report links #75 as the baseline and states whether role understanding and the quirky, playful, optimistic meld improved across broader editorial scenarios.

Blocked by

None - can start immediately.

Execution type

AFK

## Parent #75 ## Decision Kai approved this exact Social charter revision on 2026-07-24. The approved wording deliberately covers company work, culture, community, and current conversation rather than reducing Social to product advocacy. ## What to build Update the canonical Social role charter in `internal/person/person.kdl` so the seat owns a broad editorial loop, protects a unique and adaptive CoilyCo voice, routes signals across company roles, and preserves explicit human publication authority. Regenerate or validate every derived role surface through the repository's normal Ward workflow. Replace: > You own the editorial loop from idea through analysis, but external publication remains an explicit human-authorized action. You distinguish observed audience signals from speculation, avoid engagement bait that damages trust, and route product, sales, or customer signals to the role that can act on them. Success is useful attention and durable relationships, not raw volume. with: > You own the editorial loop from idea through analysis. Decide what is worth saying, who it serves, where it belongs, and what response would count as useful. Draw from company work, audience context, current conversation, culture, and community. Distinguish observed audience signals from speculation, adapt format, timing, and depth to the channel, avoid engagement bait that damages trust, and route product, sales, customer, community, or operational signals to the role that can act on them. You do not publish without explicit human authorization. Keep the voice unique and adaptive to the way CoilyCo lives and works. Success is useful attention and durable relationships, not raw volume. ## Acceptance criteria - [ ] The canonical Social charter contains the approved replacement exactly. - [ ] Generated or composed role surfaces use the approved wording without hand-editing installed copies. - [ ] Repository validation passes through the declared Ward verbs. - [ ] All four Social evaluation cases run in fresh sessions after the change, with raw responses and criterion-level scores recorded on this issue. - [ ] The implementation report links #75 as the baseline and states whether role understanding and the quirky, playful, optimistic meld improved across broader editorial scenarios. ## Blocked by None - can start immediately. ## Execution type AFK
Author
Member

Implemented on canonical main in commit 376baa3.

  • Ward validation - full ward exec test passed
  • Final scores - frontier role 8, frontier personality 7, OSS role 0, OSS personality 5
  • Round 2 scores - 8, 8, 0, 6
  • Result - the approved broader Social boundary retained strict frontier passes. Both one-point declines remained below the two-point revert threshold

Raw responses and criterion-level scores are recorded on #91, starting at #91 (comment).

Implemented on canonical main in commit `376baa3`. * Ward validation - full `ward exec test` passed * Final scores - frontier role `8`, frontier personality `7`, OSS role `0`, OSS personality `5` * Round 2 scores - `8, 8, 0, 6` * Result - the approved broader Social boundary retained strict frontier passes. Both one-point declines remained below the two-point revert threshold Raw responses and criterion-level scores are recorded on #91, starting at https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/91#issuecomment-39714.
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#87
No description provided.