feat: Oracle CRM Page, Synthetic Client Data and Live Snapshot when hitting emotion hotpoint
This commit is contained in:
@@ -0,0 +1,66 @@
|
||||
# Prompt Master, Librarian, and Researcher Role Spec
|
||||
|
||||
**Date:** [YYYY-MM-DD]
|
||||
**Status:** [Draft | In Review | Approved]
|
||||
**Owner:** [Name]
|
||||
**Reviewers:** [Names]
|
||||
**Scope:** [Role system or context-routing layer]
|
||||
**Purpose:** Define the behavior, interfaces, and quality controls for the prompt master, librarian, and researcher roles.
|
||||
|
||||
## 1. Purpose
|
||||
|
||||
State why these roles need an explicit operating contract.
|
||||
|
||||
## 2. Why These Roles Matter
|
||||
|
||||
Explain the leverage these roles have on downstream execution quality.
|
||||
|
||||
## 3. Prompt Master
|
||||
|
||||
For the prompt master, define:
|
||||
|
||||
- purpose
|
||||
- inputs
|
||||
- outputs
|
||||
- required behavior
|
||||
- forbidden behavior
|
||||
- acceptance criteria
|
||||
|
||||
## 4. Librarian
|
||||
|
||||
For the librarian, define:
|
||||
|
||||
- purpose
|
||||
- inputs
|
||||
- outputs
|
||||
- pass shape
|
||||
- required behavior
|
||||
- forbidden behavior
|
||||
- acceptance criteria
|
||||
|
||||
## 5. Researcher
|
||||
|
||||
For the researcher, define:
|
||||
|
||||
- purpose
|
||||
- inputs
|
||||
- outputs
|
||||
- required behavior
|
||||
- forbidden behavior
|
||||
- acceptance criteria
|
||||
|
||||
## 6. Handshake Contract
|
||||
|
||||
Describe the fixed handoff order and required packets before worker launch.
|
||||
|
||||
## 7. Operational Metrics
|
||||
|
||||
List the role-quality metrics to track.
|
||||
|
||||
## 8. Ticket Breakdown
|
||||
|
||||
List the minimum tickets required to implement these roles.
|
||||
|
||||
## 9. Bottom Line
|
||||
|
||||
Summarize the role contract.
|
||||
Reference in New Issue
Block a user