Skip to main content

Sasha AI Engine

Sasha is ReGenesis's AI engine — an "invisible intelligence" that observes coaching sessions, generates evidence-backed insights, and provides 24/7 companion support to coachees. Sasha is not a chatbot. It is a sophisticated AI system built on Anthropic's Claude that operates within strict safety guardrails, with every output subject to human oversight.

Key Design Principles

PrincipleImplementation
Human-in-the-loopAll AI-generated insights require coach approval before client delivery
Evidence-backedEvery claim links to source material (L0/L1/L2 Evidence Packs)
Privacy-firstData is pseudonymized before LLM calls; no-training flags set on every request
Safety-firstEscalation protocols for crisis, therapy-territory content, and harmful outputs
TransparentFull provenance logging: model version, prompt template, token counts, timestamps
KillableEmergency off-switch via feature flag — can disable Sasha instantly per tenant or globally

LLM Provider Strategy

  • Primary: Anthropic Claude (Claude 3.5 Sonnet for analysis, Claude 3.5 Haiku for lower-cost tasks)
  • Fallback: OpenAI GPT-4o (for provider outage scenarios)
  • No model training: Both providers contractually prohibited from training on our data
  • Provider diversity: Reduces single-vendor dependency risk

Cost Profile

TaskModelEstimated Cost Per Call
Session insight generationClaude 3.5 Sonnet$0.05 - $0.15
Evidence reasoning (L1)Claude 3.5 Sonnet$0.03 - $0.08
Companion chat responseClaude 3.5 Haiku$0.001 - $0.005
Embedding generationtext-embedding-3-small$0.0001 per 1K tokens

Emergency Off-Switch

If Sasha produces harmful output or a security incident is detected, the kill switch can disable all AI processing in under 5 seconds. This is a non-negotiable safety requirement. The feature flag is cached in Redis with a 5-second TTL, meaning changes propagate globally within one TTL cycle.

No-Training Guarantee

Every API call to Anthropic and OpenAI includes the no-training flag. This is contractually reinforced and technically enforced. Our data is NEVER used to train foundation models. This is verified in quarterly provider compliance reviews.

Prompt Versioning

All system prompts and prompt templates are version-controlled in the codebase (not stored in the database). Changes to prompts require pull request review, A/B testing, and safety review before deployment. Prompt versions are logged with every LLM call for reproducibility.