Skip to content

Gate Mapping: Global Network Expansion Engine ↔ CDO SDLC

Prepared by: CDO Office
Date: 7 April 2026
Classification: Confidential - ELT Only
Context: Alignment document following CDO/CSNO onboarding meeting (6 April 2026)

Purpose

The CSNO (Bachir Njeim) operates a 6-gate expansion engine for new corridors, operators, and market entry. The CDO operates a 9-phase SDLC for software delivery. These are not competing processes - they are complementary layers of the same pipeline.

This document maps one to the other so that: 1. Global Network and CDO teams use one shared language 2. Every gate has a clear CDO-domain deliverable 3. No corridor goes into engineering without passing through the right gates 4. No gate is held up because engineering wasn't engaged early enough

The Map

Gate Flow Diagram

flowchart LR
    subgraph CSNO ["CSNO Domain"]
        direction TB
        G0["G0: Opportunity Intake\nOwner: CSNO\nCDO: Notified only"]
        G1["G1: Strategic, Regulatory\n& Commercial Validation\nOwner: CSNO\nCDO: Active - feasibility spike"]
        G2["G2: Corridor Design\nOwner: CSNO + Product\nCDO: Co-owns requirements"]
        G5["G5: Scale\nOwner: CSNO\nCDO: Operates reliability"]
    end

    subgraph CDO ["CDO Domain"]
        direction TB
        G3["G3: Execution & Integration\nOwner: CDO leads\nArch Review - Development - QA"]
        G4["G4: Controlled Launch\nOwner: CSNO + CDO\nDeployment - Canary - SLO validation"]
    end

    G0 -->|"Pipeline signal"| G1
    G1 -->|"Feasibility confirmed"| G2
    G2 -->|"Requirements complete"| G3
    G3 -->|"Code complete, pipeline green"| G4
    G4 -->|"Metrics meet targets"| G5

    style G0 fill:#e8f4f8,stroke:#4a90d9
    style G1 fill:#e8f4f8,stroke:#4a90d9
    style G2 fill:#d4eaff,stroke:#2e6da4
    style G3 fill:#fff3cd,stroke:#f0a500
    style G4 fill:#d4eaff,stroke:#2e6da4
    style G5 fill:#e8f4f8,stroke:#4a90d9
Global Network Gate Gate Owner CDO Phase(s) CDO Owner CDO Deliverable When CDO Is Engaged
G0: Opportunity Intake CSNO - - None (demand signal from CSNO) Notified - CDO aware of pipeline
G1: Strategic, Regulatory, Commercial Validation CSNO Phase 1: Discovery & Spike Digital Office Technical feasibility assessment, regulatory tech requirements, data residency analysis, architecture PoC if needed Active from G1 - Digital Office runs spike
G2: Corridor Design CSNO + Product Phase 2: Requirements & Acceptance Criteria Product Manager Stories with acceptance criteria, fund flow sequence diagrams, settlement logic, fallback scenarios, API contract draft Co-owns G2 - Product translates corridor design into engineering requirements
G3: Execution & Integration CDO Phase 3: Architecture Review → Phase 5: Development → Phase 6: Quality Gates Solution Architect + Solution Engineers ADR (if significant), technical design, code, tests, pipeline, integration with operator APIs CDO leads G3 - this is where engineering builds
G4: Controlled Launch CSNO + CDO Phase 7: Deployment → Phase 8: Post-Deploy Verification Production Engineering + Product Canary deployment, SLO validation, monitoring dashboards, limited rollout with strict alerting Co-owns G4 - CDO deploys, CSNO monitors commercial metrics
G5: Scale CSNO Phase 9: Production Operations Production Engineering Full production, performance optimisation, on-call, SLA tracking CDO operates - Production Engineering owns reliability

Visual Flow

CSNO Domain                          CDO Domain
═══════════                          ══════════

G0: Opportunity     ─── notify ───►  Pipeline awareness
        │
        ▼
G1: Validation      ◄── spike ────►  Digital Office feasibility
        │                             assessment + architecture PoC
        ▼
G2: Corridor        ◄── co-own ──►  Product: Stories, acceptance
    Design                           criteria, fund flow diagrams,
        │                             settlement logic
        ▼
G3: Execution       ◄── CDO leads ► Architecture Review → Development
    & Integration                     → Quality Gates → Code + Tests
        │
        ▼
G4: Controlled      ◄── co-own ──►  Deployment → Post-Deploy
    Launch                            Canary + SLO validation
        │
        ▼
G5: Scale           ◄── operate ──► Production Engineering
                                      SLA tracking, on-call, optimisation

Gate Entry Criteria (CDO Domain)

G1 Entry - Digital Office Spike

Triggered by: CSNO identifies opportunity worth exploring
Digital Office receives: Market brief, regulatory context, commercial hypothesis
Digital Office delivers (within 1 cycle / 10 days):

  • Technical feasibility assessment (can we build this with current platform?)
  • Regulatory technology requirements per jurisdiction
  • Data residency and compliance constraints
  • Estimated engineering effort (T-shirt size: S/M/L/XL)
  • Architecture risks and dependencies
  • Go/no-go recommendation to proceed to G2

Quality bar: If Digital Office says "no-go," the corridor does not proceed to G2 regardless of commercial attractiveness. Technical infeasibility kills the opportunity early - this is the point of early engagement.

G2 Entry - Product Requirements

Triggered by: G1 pass (technical feasibility confirmed)
Product Manager receives: Corridor design from Global Network (operators, fund flows, settlement structure, CCQ targets)
Product Manager delivers:

  • Epic created in Jira with Definition of Done
  • Stories with acceptance criteria (each fits in one 9-day cycle)
  • Fund flow sequence diagram (every state, every timestamp)
  • Settlement logic documented (how money moves, when, through whom)
  • Fallback scenarios (what happens when operator X fails?)
  • Business logic rules (FX lock window, retry policy, reconciliation triggers)
  • API contract draft (OpenAPI spec for new operator integration)
  • CCQ targets mapped to SLOs (Coverage → availability, Cost → unit economics, Quality → latency + error rate)

Quality bar: No story enters a squad's backlog without acceptance criteria and a fund flow diagram. This is the "strong translation layer" Bachir is asking for.

G3 Entry - Engineering Execution

Triggered by: G2 pass (requirements complete and reviewed)
Architecture Review: Required for any new operator integration or fund flow change
Solution Engineers deliver:

  • ADR written (if significant architectural decision)
  • Technical design reviewed by architect
  • Code implemented with unit tests (80% coverage target)
  • Integration tests for operator API
  • Security review (shift-left: threat model updated if new payment flow)
  • Pipeline green (Snyk scan, static analysis, all tests pass)
  • PR approved (2 reviewers)
  • Feature flag configured for controlled rollout

Quality bar: Definition of Done per SDLC v2.0 Section 12. No exceptions for corridor launches.

G4 Entry - Controlled Launch

Triggered by: G3 pass (code complete, pipeline green, feature flag ready)
Production Engineering delivers:

  • Canary deployment to limited traffic (1–5%)
  • SLO monitoring active (availability, latency, error rate per G2 targets)
  • Alerting configured (PagerDuty/on-call for new corridor)
  • Rollback plan tested (automated rollback within 5 minutes)
  • Transaction lifecycle visibility confirmed (every state has a timestamp - per Bachir's requirement)
  • Partner-facing status page updated (if applicable)

CSNO monitors during G4: - [ ] Transaction success rates meet CCQ Quality target - [ ] Settlement completes within contracted SLA - [ ] Operator performance meets commercial expectations - [ ] No regulatory issues surface

G4 → G5 decision: Joint CDO/CSNO call. Both must agree before full scale.

G5 Entry - Full Scale

Triggered by: G4 pass (controlled launch metrics meet targets)
Production Engineering delivers:

  • Feature flag removed (full traffic)
  • On-call rotation includes new corridor
  • SLA tracking live in dashboard
  • Runbook written for new corridor (incident response)
  • Handover to BAU complete (no more "project team" - squad owns it)

CSNO's Partner Performance & Optimisation team takes over: - Routing optimisation - SLA adherence monitoring - Continuous improvement - Issue resolution with operators

Transaction Lifecycle Architecture (New Initiative)

Bachir identified a critical gap: transaction visibility is too coarse. This is a joint CDO/CSNO deliverable to be designed in Phase 2 of the 30/60/90 plan.

Requirements (from Bachir)

  • Every step in the transaction lifecycle must have a defined status
  • Every status transition must capture a timestamp
  • Full traceability from initiation to final outcome
  • Supports: operational control, incident resolution, SLA tracking, partner transparency, product improvement

Proposed Transaction States (draft - to be validated with Global Network)

Pay-In Lifecycle:
INITIATED → SESSION_CREATED → PAYMENT_METHOD_SELECTED → OTP_SENT →
OTP_VERIFIED → AUTHORISED → CAPTURED → SETTLED → RECONCILED → COMPLETE

Pay-Out Lifecycle:
INITIATED → VALIDATED → COMPLIANCE_CHECKED → FX_QUOTED → FX_LOCKED →
SETTLEMENT_INSTRUCTED → FUNDS_DISPATCHED → OPERATOR_CONFIRMED →
BENEFICIARY_CREDITED → RECONCILED → COMPLETE

Remittance Lifecycle:
SENDER_INITIATED → KYC_VERIFIED → FX_QUOTED → FX_LOCKED →
SENDER_DEBITED → CORRIDOR_ROUTED → SETTLEMENT_INSTRUCTED →
FX_CONVERTED → PAYOUT_INITIATED → OPERATOR_DISPATCHED →
BENEFICIARY_CREDITED → RECONCILED → COMPLETE

Each state captures: - Timestamp (UTC) - Duration since previous state (ms) - Actor (system, operator, user) - Outcome (success, failure, timeout, retry) - Metadata (operator reference, FX rate, amount)

Integration with CCQ Framework

CCQ Dimension Measured By
Coverage % of transaction states that have operator confirmation (not just internal)
Cost FX spread at lock vs settlement, operator fees per state transition
Quality Time in each state, failure rate per state, retry rate, end-to-end latency

Next Steps

Action Owner Deadline
Validate transaction states with Global Network (Bachir) CDO + CSNO Week 3 (21 April)
Design state machine with engineering Product + Solution Architecture Phase 2 (May)
Implement instrumentation (timestamps at every transition) Solution Engineering Phase 2 (May)
Build transaction lifecycle dashboard Data Engineering + Production Engineering Phase 3 (June)
Connect to SLA tracking and partner transparency Production Engineering + Global Network Phase 3 (June)

CCQ Framework Adoption

Bachir's CCQ (Coverage, Cost, Quality) framework should be adopted across Product and Engineering:

Where How
Product Management Every corridor/operator Epic includes CCQ targets in the Definition of Done
Architecture Review ARB evaluates new integrations against CCQ impact
Production Engineering SLOs mapped to CCQ Quality dimension
Data Engineering CCQ dashboard as a first analytics deliverable
Digital Office Feasibility spikes assess CCQ achievability before G2

Entry Archetypes (from Global Network)

Bachir defined entry archetypes that determine how we enter each market. These have direct engineering implications:

Archetype Example Engineering Implication
Aggregator-led Pakistan (via UBL/1Link) Single integration point, limited control, dependent on aggregator uptime
Direct bank integration Bangladesh (direct to bKash, Nagad) Multiple integrations, more control, higher engineering effort per operator
Wallet-first Nepal (eSewa, Khalti) Mobile wallet APIs, different auth flows, agent network considerations
Hybrid UAE (DFSA licence + aggregator + direct) Most complex - multiple integration patterns in one market

Action: Product and Architecture should maintain an "Integration Pattern Library" - reusable blueprints for each archetype. The Digital Office should validate which archetype applies during G1 spikes.

Working Rhythm: CDO and CSNO

Working Rhythm

flowchart LR
    subgraph Bi_Weekly ["Bi-Weekly"]
        A["CDO / CSNO 1:1\nStrategic alignment\nPipeline review\nEscalations\n\nAttendees: CDO + CSNO"]
    end

    subgraph Per_Gate ["Per G4 Entry"]
        B["Corridor Launch Review\nGo / no-go for\ncontrolled launch\n\nAttendees: CDO + CSNO\n+ CPO + CTO"]
    end

    subgraph Monthly ["Monthly"]
        C["Expansion Pipeline Sync\nG0-G2 pipeline visibility\nfor CDO teams\n\nAttendees: CDO + CSNO\n+ Digital Office + Product"]
    end

    A -->|"G4 reached"| B
    B -->|"Monthly cadence"| C
    C -->|"Bi-weekly reset"| A

    style A fill:#e8f4f8,stroke:#4a90d9
    style B fill:#fff3cd,stroke:#f0a500
    style C fill:#e8f0fb,stroke:#7b5ea7
Meeting Frequency Purpose Attendees
CDO/CSNO 1:1 Bi-weekly Strategic alignment, pipeline review, escalations CDO + CSNO
Corridor Launch Review Per G4 entry Go/no-go for controlled launch CDO + CSNO + CPO + CTO
Expansion Pipeline Sync Monthly G0–G2 pipeline visibility for CDO teams CDO + CSNO + Digital Office + Product

Appendix: Addressing Bachir's Concerns

Bachir's Concern What We've Built Status
"PMO governance not enforced" Digital Office owns delivery methodology + governance. Arsalan (ex-PMO Manager) leads as Manager Digital Delivery. Function elevated, not eliminated. ✅ Designed
"BRDs inconsistent" SDLC v2.0 Phase 2 requires Stories with acceptance criteria, fund flow diagrams, business logic. No story enters backlog without these. ✅ Designed
"Tech engaged too late" Digital Office runs G1 feasibility spikes. Engineering involved from Gate 1, not Gate 3. ✅ Designed
"No Definition of Done" SDLC v2.0 Section 12: 10-point DoD per Story. ✅ Published
"Transaction visibility too coarse" Transaction Lifecycle Architecture initiated as joint deliverable. Draft states above. 🟡 In progress
"Automation lacking" AI/ML initiative 3.4 expanded: reconciliation + settlement + monitoring + exception management. 🟡 Planned
"Service Delivery immature" Production Engineering - Service Delivery sub-team with Lead Service Analyst (Rohit Rana). Awaiting Bachir's restructuring proposal. 🟡 Partially addressed
"Weak middle management" Reapplication process for changed roles. 3 managers flagged "verify hands-on." 🟡 Designed
"Knowledge concentration risk" 14 Ways of Work, 79 ADRs, 74 Standards, SDLC v2.0 - documentation-first culture. ✅ Published
"Platform mindset" Architecture standards, ADRs, "build once deploy many." Entry archetype library proposed. ✅ Designed

Next review: After Bachir's dept files arrive (8 April midday). Update this document with any changes from the files.