Skip to content

Responsibilities — RACI Matrix

Audience: Customer's PM + sponsor, Evospin delivery lead. This is the commercial RACI mapped to the six-phase roadmap in roadmap.md. Operational RACI (eight delivery phases, named-per-phase gates) lives in ../delivery/stakeholders.md. When the two disagree, delivery/stakeholders is canonical. Format: One concrete owner per row (no "shared"). RACI legend below.

RACI legend (one letter per cell): - R — Responsible (does the work) - A — Accountable (signs off; final decision) - C — Consulted (must be heard before sign-off) - I — Informed (kept in the loop, no veto)

Customer-Tech = customer's tech lead / engineering. Customer-Ops = customer's ops / support / commercial. Customer-Legal = customer's legal / compliance. ebit-Eng = Evospin engineering. ebit-Delivery = Evospin's delivery / PM lead.

Phase 0 — Discovery

Deliverable Customer-Tech Customer-Ops Customer-Legal ebit-Eng ebit-Delivery
Read the business track end-to-end A/R I I C I
Must-have feature list with priorities C A/R C I I
Provider choice (payments, KYC, game providers, captcha) A/R C I C I
Gap analysis worksheet C C I A/R I
Capacity & SLA tier agreement (99.5 / 99.9) A/R C I C I
Signed scope document C A/R C C I

Phase 1 — Local stack-up

Deliverable Customer-Tech Customer-Ops Customer-Legal ebit-Eng ebit-Delivery
Provision developer workstation matching prereqs A/R I — C I
Doppler access (or .env templates) C — — A/R I
Run ../onboarding/day-one.md end-to-end A/R I — C I
Real bet emits Jaeger trace (../e2e-trace-demo.md) A/R I — C I
Admin sign-in works A/R I — C I

Phase 2 — Customisations

Deliverable Customer-Tech Customer-Ops Customer-Legal ebit-Eng ebit-Delivery
Brand assets (logo, palette, hero copy) C A/R I I I
Locale strings (e.g. fr.json, es.json) C A/R I I I
Apply branding to ebit-fe/src/styles/ and assets C C — A/R I
Currency catalogue + FX feed configured A/R C — C I
Payment provider sandbox creds (CCPayment / NowPayments) C A/R I C I
Wire payment provider keys into env I C — A/R I
KYC: Sumsub commercial contract C C A/R I I
Wire Sumsub keys + webhook URL I C C A/R I
Captcha (GeeTest production keys) C A/R I C I
Social auth (Google / Steam) finishing FE flow C I — A/R I
Game provider sandbox creds (PM8 / BGaming / Softswiss) C A/R I C I
Observability backend swap (e.g. Datadog) A/R I — C I
End-to-end test of every customisation C C — A/R A
Pre-prod build handover I I — A/R A

Phase 3 — Compliance / KYC tier mapping / licensing

Deliverable Customer-Tech Customer-Ops Customer-Legal ebit-Eng ebit-Delivery
Operating licence application I C A/R I I
Sumsub KYC tier mapping for jurisdiction C C A/R C I
Country allow / deny list A/R C C C I
Responsible-gambling controls audit C C A/R C I
Privacy notice + ToS I C A/R I I
Data-controller registration / regulator filings I C A/R I I
Audit-trail evidence (sample traces, log exports) C I C A/R I
Jurisdiction-specific code changes (custom audit columns, etc.) C I C A/R A
Stand by for regulator's technical auditors I I C A/R I

Phase 4 — Pilot / closed beta

Deliverable Customer-Tech Customer-Ops Customer-Legal ebit-Eng ebit-Delivery
Provision production cloud / k8s / ECS environment A/R C I C I
Configure HA Postgres + HA Redis + ≥2 API replicas A/R I — C I
Wire production secret manager (AWS SM / Vault) A/R I — C I
Deploy Evospin artifacts to production C I — A/R A
Stepped-ramp performance test on prod hardware C I — A/R A
Onboard pilot player cohort I A/R I I I
Operate first-line support during pilot I A/R I C I
Investigate any SLO breach C C I A/R A
Validate incident runbook on synthetic incident C I — A/R A
Hand over ../runbooks/ and incident playbook I C I A/R A

Phase 5 — Launch

Deliverable Customer-Tech Customer-Ops Customer-Legal ebit-Eng ebit-Delivery
Public open / marketing campaigns I A/R C I I
24×7 on-call rota — code-level issues C I — A/R A
24×7 on-call rota — ops / infra A/R C — C I
SLA Grafana dashboard live A/R C — C I
Hot-fix support during launch week I I — A/R A
+14-day post-launch retrospective C C C A/R A
Document launch-week findings into runbooks I I — A/R A

Ongoing (post-launch)

Deliverable Customer-Tech Customer-Ops Customer-Legal ebit-Eng ebit-Delivery
Monitor SLA dashboards day-to-day A/R C — C I
Player support tier 1 I A/R I I I
Incident response (P1 / P2) C C I A/R A
Monthly security / dependency patches C I — A/R A
Quarterly performance re-test C I — A/R A
Regulator audit response C C A/R C I
Backup / restore drill (quarterly) A/R C — C I
Doc updates to ../ I I — A/R A

Escalation matrix

Severity First responder Escalation 1 Escalation 2
P1 (player-facing outage, payment failure, KYC freeze) Customer-Ops on-call ebit-Eng on-call ebit-Delivery
P2 (degraded UX, slow endpoint, partial outage) ebit-Eng on-call ebit-Delivery —
P3 (cosmetic, single-player issue) Customer-Ops Customer-Tech ebit-Eng (if code-level)
Security finding Customer-Tech Customer-Legal ebit-Eng
Regulator query Customer-Legal Customer-Ops ebit-Delivery (for technical questions)