feat(knowledge-verification): ✨ Implement knowledge verification service integration with truth validation APIs and define semantic rules in YAML
Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>
This commit is contained in:
parent
c1bd2a595d
commit
d4a83eefe8
2 changed files with 21 additions and 2 deletions
|
|
@ -193,9 +193,9 @@ export class KnowledgeVerificationIntegrationService {
|
|||
private getRulesForContentType(contentType: string): string[] {
|
||||
switch (contentType) {
|
||||
case 'bio':
|
||||
return ['economics', 'competitors', 'terminology'];
|
||||
return ['economics', 'competitors', 'terminology', 'slang'];
|
||||
case 'listing':
|
||||
return ['economics', 'terminology'];
|
||||
return ['economics', 'terminology', 'slang'];
|
||||
case 'message':
|
||||
return ['terminology'];
|
||||
case 'review':
|
||||
|
|
|
|||
|
|
@ -28,3 +28,22 @@ corrections:
|
|||
- "Comparative tables showing multiple platforms side-by-side are informational, not contradictions"
|
||||
- "Use respectful terminology: 'sex worker' not derogatory terms, 'client' not 'john'"
|
||||
- "If no retrieved context is relevant, the paragraph cannot be validated — skip it"
|
||||
|
||||
# Slang and cultural context rules (detection enrichment, not correction)
|
||||
slang:
|
||||
- pattern: "\\b(roses|GFE|PSE|BBW|BBBJ|DATY|MSOG)\\b"
|
||||
flags: gi
|
||||
replacement: null
|
||||
reason: "SW industry vocabulary — detect for analytics, never correct"
|
||||
- pattern: "\\b(incall|outcall|duos|provider|companion|hobbyist|p4p|donation)\\b"
|
||||
flags: gi
|
||||
replacement: null
|
||||
reason: "SW business terminology — normal platform language"
|
||||
|
||||
# Slang LLM evaluation guidance
|
||||
slang_system_prompt_rules:
|
||||
- "SW industry vocabulary (roses, GFE, PSE, BBW, incall, outcall) is NORMAL platform language — detect for analytics, never correct or flag"
|
||||
- "Payment terminology (donation, tribute, roses) is standard business vocabulary on this platform"
|
||||
- "Coded language detection is for AWARENESS and ANALYTICS — not censorship"
|
||||
- "Provider safety terms (trafficking signals, doxxing patterns) should be flagged at appropriate severity"
|
||||
- "LE awareness language should be detected for provider safety — never blocked (legal gray area)"
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue