Platform Integration
Surviva connects to the Kennis OS platform via the /api/platform/v1 endpoint
family. All AI-powered features, including KORA health coaching, route through
this integration layer rather than calling external APIs directly.
Product Identifier
Surviva identifies itself to the platform using the product code suriva.
Every request to the Platform API must include the X-Kennis-Product: suriva
header so that the Assembler can load the correct bot configuration, guardrails,
and prompt templates.
Required Headers
| Header | Value | Purpose |
|---|---|---|
Authorization | Bearer <token> | Septimius JWT for authenticated requests |
X-Kennis-Product | suriva | Routes to the correct bot and guardrails |
X-Correlation-Id | UUID v4 | Traces a user action across all services |
X-Causation-Id | UUID v4 | Links a request to the event that caused it |
Assembler Exclusivity
Surviva must never import or call the Anthropic SDK directly. All LLM
interactions are routed through the Kennis OS Assembler module by posting to
the /api/platform/v1/assemble endpoint. This constraint ensures that:
- Prompt templates are managed centrally in the Assembler
- The KOS-GUARD-HEALTH-001 guardrail is applied to every KORA-007 response
- Token usage, latency, and cost are tracked in the platform telemetry pipeline
- Health-specific safety checks run before any output reaches the user
Key Endpoint
POST /api/platform/v1/assemble
This is the primary endpoint for KORA health coaching interactions. The request body includes the conversation context, user profile, and any assessment data. The Assembler selects the appropriate prompt template for bot KORA-007 / CHT-056, applies guardrails, and returns the generated response.
Health Guardrail
All output from KORA-007 passes through the KOS-GUARD-HEALTH-001 guardrail before being returned to the caller. This guardrail validates that responses do not contain unsupported medical claims, that disclaimers are present where required, and that the tone remains supportive and non-diagnostic.