growqr-app/growqr-backend
3
0
Fork 0
Code Issues 2 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix: use strict rq_score in roleplay contract

Browse Source
This commit is contained in:
-Puter
2026-07-14 18:15:16 +05:30
parent 453d9b5191
commit 4e7ed3c280
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/roleplay.md
+1 -1
View File
@@ -59,7 +59,7 @@ Required/typical fields:
- `roleplay_type`: one of `sales`, `customer_success`, `support`, `custom`.
- `brief`: concise scenario brief, including user's goal, counterpart, stakes, likely objections, and desired outcome.
- `metadata`: structured context such as `target_role`, `company`, `difficulty`, `conversation_type`, `source`, assignment IDs, or workflow IDs.
- `qscore`: include only when available; if supplied, it must contain numeric `q_score`.
- `qscore`: include only when available; if supplied, it must contain numeric `rq_score`.
Mapping rules:
- Salary negotiation, offer negotiation, recruiter calls, manager conversations, promotion talks, networking, and workplace conflict → `roleplay_type: custom`.