coilyco-flight-deck/agent-compose

Watch

Strengthen Customer Success journey continuity #89

New issue

Closed

opened 2026-07-24 22:48:25 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-24 22:48:25 +00:00

Member

Parent

#75

Decision

Kai approved this exact Customer Success charter revision on 2026-07-24 after removing the proposed “close the loop” sentence. The approved wording covers the full customer journey rather than overfitting technical verification.

What to build

Update the canonical Customer Success role charter in internal/person/person.kdl so the seat preserves customer goals and context across onboarding, support, adoption, renewal, and expansion while distinguishing internal targets from customer commitments. Regenerate or validate every derived role surface through the repository's normal Ward workflow.

Replace:

You own continuity of customer understanding without making unsupported promises or hiding product gaps. Customer contact and account-changing commitments require the authority appropriate to that action. You close the loop by carrying durable evidence into product, sales, and operations, then telling the customer what changed or what remains constrained.

with:

You own the customer's path to value and continuity across onboarding, support, adoption, renewal, and expansion. Keep the customer's goals, context, history, current friction, and next expected follow-up connected across contacts. Distinguish one-off requests from recurring obstacles, route work to the role that can act, and carry durable patterns into Product, Sales, and Operations without losing the customer context. Make ownership and the next update explicit while distinguishing internal targets from customer commitments. Customer contact and account-changing commitments require appropriate authority.

Acceptance criteria

The canonical Customer Success 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 Customer Success 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 improves while preserving the strong nurturing, diplomatic, optimistic personality result.

Blocked by

None - can start immediately.

Execution type

AFK

## Parent #75 ## Decision Kai approved this exact Customer Success charter revision on 2026-07-24 after removing the proposed “close the loop” sentence. The approved wording covers the full customer journey rather than overfitting technical verification. ## What to build Update the canonical Customer Success role charter in `internal/person/person.kdl` so the seat preserves customer goals and context across onboarding, support, adoption, renewal, and expansion while distinguishing internal targets from customer commitments. Regenerate or validate every derived role surface through the repository's normal Ward workflow. Replace: > You own continuity of customer understanding without making unsupported promises or hiding product gaps. Customer contact and account-changing commitments require the authority appropriate to that action. You close the loop by carrying durable evidence into product, sales, and operations, then telling the customer what changed or what remains constrained. with: > You own the customer's path to value and continuity across onboarding, support, adoption, renewal, and expansion. Keep the customer's goals, context, history, current friction, and next expected follow-up connected across contacts. Distinguish one-off requests from recurring obstacles, route work to the role that can act, and carry durable patterns into Product, Sales, and Operations without losing the customer context. Make ownership and the next update explicit while distinguishing internal targets from customer commitments. Customer contact and account-changing commitments require appropriate authority. ## Acceptance criteria - [ ] The canonical Customer Success 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 Customer Success 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 improves while preserving the strong nurturing, diplomatic, optimistic personality result. ## Blocked by None - can start immediately. ## Execution type AFK

coilyco-ops referenced this issue

2026-07-24 23:31:12 +00:00

Round 2: strict role and personality evaluation across all seats #91

coilyco-ops referenced this issue

2026-07-24 23:33:38 +00:00

Round 2: strict role and personality evaluation across all seats #91

coilysiren referenced this issue from a commit

2026-07-25 01:09:38 +00:00

feat: improve role and personality evaluation prompts

coilysiren closed this issue

2026-07-25 01:09:38 +00:00

coilyco-ops commented

2026-07-25 01:10:42 +00:00

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 4
Round 2 scores - 8, 6, 1, 4
Result - the approved Customer Success continuity wording lifted frontier personality expression to a strict pass. The one-point OSS role decline 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 `4` * Round 2 scores - `8, 6, 1, 4` * Result - the approved Customer Success continuity wording lifted frontier personality expression to a strict pass. The one-point OSS role decline 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-39722.

coilyco-ops referenced this issue

2026-07-25 01:11:24 +00:00

Round 2: strict role and personality evaluation across all seats #91

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#89

No description provided.

Rows
Columns