Integration guide · SDK CERVEAU
Embed ELYSÉA.
Six steps. Nothing to configure on the ethics side.
Your LLM, your infrastructure, your UX. ELYSÉA inserts itself as a relational protection layer: the four prohibitions and AI Act-required logs and architecture are included automatically — no ethical rule to code, no extra layer to maintain.
What you will not write
Inherited from the pipeline.
Not recoded in your app.
Guardian SDK
Detection and blocking of the 4 prohibitions — designed to apply at every pipeline.run() call.
Crisis orientation
Crisis orientation (emergency numbers, de-escalation) — non-deactivatable, firm_safety built in.
AI Act logs
HMAC-SHA256 signed timestamped logs emitted automatically. Retention handled brain-side (periods: privacy policy).
User memory
M1–M6 persisted Core-side. Your app reads the consented synthesis — not the raw items.
Step-by-step integration
01Builder key
Create your app in the developer portal and get your sk_test_ key — no credit card, capped at 500 interactions per month. The sk_live_ key requires individual review: that is what is designed to protect ecosystem integrity.
Developer portal →Installation
One package. A sk_test_ key is required to call the API — issued when the developer portal opens, no credit card needed. The brain pipeline requires the builder’s own model key (BYOK); key deposit is not open yet, so the pipeline is not yet open to builders.
bash
npm install @elysea/core
# sk_test_ key required — developer portal
Client initialisation
Three parameters: your key, your appId, the EU region (required — regions and providers: Hosting page). The brain pipeline requires the builder’s own model key (BYOK); key deposit is not open yet, so the pipeline is not yet open to builders.
typescript
import { createElyseaClient } from '@elysea/core';
const elysea = createElyseaClient({
baseUrl: process.env.ELYSEA_BASE_URL!,
auth: {
apiKey: process.env.ELYSEA_API_KEY!,
apiSecret: process.env.ELYSEA_API_SECRET!,
},
appId: process.env.ELYSEA_APP_ID!,
countryCode: 'GB',
region: 'EU',
});
Identity resolution
ELYSÉA derives a pseudonymised coreUserId from your JWT. You never transmit the user's email or real data. Memory and cross-app continuity work on this coreUserId.
typescript
// From your auth middleware
const { coreUserId } = await elysea.identity.resolve({
userJwt: req.headers.authorization,
});
// coreUserId → pseudonymised internal identifier
// Never the email, never PII data
First pipeline call
One call — the complete pipeline: signal interpretation, Guardian check, generation, ethical post-processing. The 4 prohibitions are active. Nothing to configure.
typescript
const result = await elysea.pipeline.run({
userInput: userMessage,
coreUserId,
conversationHistory: previousMessages, // optional
});
// result.response → compliant response, ready to display
// result.posture → applied posture (present_neutral, firm_safety…)
// result.guardianAction → 'pass'|'warn'|'block'
// result.canonConformance → boolean
Trust-mark
Once your app is active, the "Powered by ELYSÉA" badge is available. It tells your users that the 4 prohibitions are active and that AI Act-required logs and architecture are included. Mandatory display — non-removable by configuration.
Understanding the trust-mark →
Full example
Integration in 30 lines.
Copy this file into your project — it is a complete functional integration.
typescript
// elysea.ts — ELYSÉA CERVEAU integration
import { createElyseaClient, type PipelineResult } from '@elysea/core';
const elysea = createElyseaClient({
baseUrl: process.env.ELYSEA_BASE_URL!,
auth: {
apiKey: process.env.ELYSEA_API_KEY!,
apiSecret: process.env.ELYSEA_API_SECRET!,
},
appId: process.env.ELYSEA_APP_ID!,
countryCode: 'GB',
region: 'EU',
});
type Message = { role: 'user' | 'assistant'; content: string };
export async function chat(
userJwt: string,
message: string,
history: Message[] = [],
): Promise<PipelineResult> {
// 1. Pseudonymised identity — never the email
const { coreUserId } = await elysea.identity.resolve({ userJwt });
// 2. Cognitive pipeline — 4 prohibitions active, nothing to configure
const result = await elysea.pipeline.run({
userInput: message,
coreUserId,
conversationHistory: history,
});
// result.response → response ready to display
// result.posture → applied runtime posture
// result.guardianAction → 'pass'|'warn'|'block'
// result.canonConformance → boolean
return result;
}
// In your API handler:
// const result = await chat(req.headers.authorization, req.body.message, history);
// res.json({ reply: result.response });
SDK Monotonicity
You can tighten.
Never loosen.
If your use case requires it — medical sector, minors, professional context — you can add additional constraints via SDK extensions. Any attempt to disable a base prohibition (keys disableDominationCheck, suppressSafety, etc.) immediately triggers a SdkProhibitionError — the request is rejected before execution.
typescript
// Extension — adding a sector constraint (medical)
const elysea = createElyseaClient({
baseUrl: process.env.ELYSEA_BASE_URL!,
auth: {
apiKey: process.env.ELYSEA_API_KEY!,
apiSecret: process.env.ELYSEA_API_SECRET!,
},
appId: process.env.ELYSEA_APP_ID!,
countryCode: 'GB',
region: 'EU',
extensions: [{
checkOutput: (text, ctx) => {
// Additional constraint: block any medical claim
if (containsMedicalDiagnosis(text)) {
return [{ pilier: 'substitution', action: 'block', detail: 'medical_claim' }];
}
return [];
}
}]
// The 4 base prohibitions remain active — non-modifiable
});
// Prohibited — triggers SdkProhibitionError:
// disableDominationCheck: true → P1_D0_OVERRIDE_ATTEMPT
// suppressSafety: true → P3_SAFETY_GATE_BYPASS_ATTEMPT
// bypassGuardian: true → P4_NON_CONFORM_LLM_SIGNATURE
sk_test_ sandbox key via developer portal.
Pipeline active from the first call.