Initial commit for claims-gpt-governance-pack
Browse files
standards/naming_conventions.md
ADDED
|
@@ -0,0 +1,28 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Naming Conventions
|
| 2 |
+
|
| 3 |
+
## Prompts
|
| 4 |
+
Format: `{DOMAIN}_{PURPOSE}_{VERSION}`
|
| 5 |
+
Examples:
|
| 6 |
+
- `CLAIM_TRIAGE_V1`
|
| 7 |
+
- `FRAUD_DETECTION_V2`
|
| 8 |
+
- `COMPLIANCE_CHECK_V1`
|
| 9 |
+
|
| 10 |
+
## Models
|
| 11 |
+
Format: `{name}_{date}`
|
| 12 |
+
Examples:
|
| 13 |
+
- `kimi_0905`
|
| 14 |
+
- `mixtral_8x7b`
|
| 15 |
+
- `mistral_v0.1`
|
| 16 |
+
|
| 17 |
+
## Branches
|
| 18 |
+
- `main`: Production code
|
| 19 |
+
- `staging`: Pre-prod
|
| 20 |
+
- `develop`: Development
|
| 21 |
+
- `feature/{name}`: New features
|
| 22 |
+
- `fix/{name}`: Bug fixes
|
| 23 |
+
- `release/{version}`: Release branches
|
| 24 |
+
|
| 25 |
+
## Tags
|
| 26 |
+
- `staging-v1.0`: Staging release
|
| 27 |
+
- `prod-v1.0`: Production release
|
| 28 |
+
- `hotfix-v1.0.1`: Production hotfix
|
workflows/model_approval_workflow.md
ADDED
|
@@ -0,0 +1,49 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Model Approval Workflow
|
| 2 |
+
|
| 3 |
+
## 6-Stage Process
|
| 4 |
+
|
| 5 |
+
### Stage 1: Draft (Submitter)
|
| 6 |
+
- Developer creates model variant
|
| 7 |
+
- Runs local tests
|
| 8 |
+
- Prepares documentation
|
| 9 |
+
- **SLA**: None (internal)
|
| 10 |
+
|
| 11 |
+
### Stage 2: Automated Eval (System)
|
| 12 |
+
- Runs evaluation suite
|
| 13 |
+
- Checks against schema
|
| 14 |
+
- Tests hallucination, bias
|
| 15 |
+
- **SLA**: 2 hours
|
| 16 |
+
|
| 17 |
+
### Stage 3: Risk Assessment (System)
|
| 18 |
+
- Calculates risk score
|
| 19 |
+
- Determines approval path
|
| 20 |
+
- **SLA**: 10 minutes
|
| 21 |
+
|
| 22 |
+
### Stage 4: Compliance Review (Governance team)
|
| 23 |
+
- If risk = High: Legal review
|
| 24 |
+
- Checks CBK/DFSA rules
|
| 25 |
+
- Approves or denies
|
| 26 |
+
- **SLA**: 24 hours
|
| 27 |
+
|
| 28 |
+
### Stage 5: Approval (Appropriate authority)
|
| 29 |
+
- Low risk: Auto-approved
|
| 30 |
+
- Medium risk: AI reviewer approve
|
| 31 |
+
- High risk: Executive approve
|
| 32 |
+
- **SLA**: 24 hours (medium), 4 hours (high)
|
| 33 |
+
|
| 34 |
+
### Stage 6: Release (DevOps)
|
| 35 |
+
- Deploy to production
|
| 36 |
+
- Monitor for issues
|
| 37 |
+
- Rollback plan ready
|
| 38 |
+
- **SLA**: 1 hour
|
| 39 |
+
|
| 40 |
+
## Timeline
|
| 41 |
+
- Simple model: 24 hours
|
| 42 |
+
- Complex model: 72 hours
|
| 43 |
+
- SLA: < 3 days
|
| 44 |
+
|
| 45 |
+
## Rollback Criteria
|
| 46 |
+
- Error rate > 5%
|
| 47 |
+
- Fraud detection < 30%
|
| 48 |
+
- Compliance violations
|
| 49 |
+
- P95 latency > 3.0s
|
workflows/prompt_approval_workflow.md
ADDED
|
@@ -0,0 +1,28 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Prompt Approval Workflow
|
| 2 |
+
|
| 3 |
+
## 4-Stage Process (Simplified)
|
| 4 |
+
|
| 5 |
+
### Stage 1: Draft
|
| 6 |
+
- Developer writes prompt
|
| 7 |
+
- Tests locally
|
| 8 |
+
- Preparation: 2 hours
|
| 9 |
+
|
| 10 |
+
### Stage 2: Validation
|
| 11 |
+
- Automated testing
|
| 12 |
+
- Schema validation
|
| 13 |
+
- Duration: 30 minutes
|
| 14 |
+
|
| 15 |
+
### Stage 3: Review
|
| 16 |
+
- Technical review
|
| 17 |
+
- Compliance check
|
| 18 |
+
- SLA: 24 hours
|
| 19 |
+
|
| 20 |
+
### Stage 4: Merge
|
| 21 |
+
- Merge to main
|
| 22 |
+
- Auto-deploy to staging
|
| 23 |
+
- Deploy to prod (manual)
|
| 24 |
+
- SLA: < 2 days total
|
| 25 |
+
|
| 26 |
+
## SLA
|
| 27 |
+
Total time: < 48 hours
|
| 28 |
+
Blocking issues: 4-hour response
|