Client Engagement Swimlanes¶

How work flows from first contact to delivered software.

The Value Chain¶

Client Contact → Intake → Scoping → Design → Development → Review → Testing → Deployment
    (Margot)     (Dima)   (Aimée)  (Alexander) (Team Alpha  (Koen)  (Marije)   (Leon)
                                                or Beta)    (Eric)  (Judith)

Phase 1: Intake (Dima)¶

Client contacts GE (via Margot or direct)
Dima conducts creative intake (€25/hr gated assessment)
KYC verification
Scope assessment is final — defines what gets built

Phase 2: Scoping (Aimée)¶

Technical architecture decisions
Technology stack selection
Budget estimation
Work package decomposition
Formal specification creation

Phase 3: Team Assignment (Dolly)¶

Client assigned to Team Alpha or Team Beta
Assignment is permanent — client stays with their team forever
Cross-team work triggers automatic HALT
Ensures context retention and prevents knowledge fragmentation

Phase 4: Development (Team Alpha or Beta)¶

Backend (Urszula/Maxim), Frontend (Floris/Floor), iOS (Martijn/Valentin)
Alexander handles UI/UX design
Alex/Tjitte manage GitHub/CI pipelines
Boris handles database operations

Phase 5: Quality (Koen/Eric + Marije/Judith)¶

Code review (Koen for Alpha, Eric for Beta)
Testing (Marije for Alpha, Judith for Beta)
Integration tests exercise actual system paths (Proof of Life)

Phase 6: Deployment (Leon + Arjan)¶

Infrastructure provisioning (Arjan)
Deployment execution (Leon)
Zero-downtime deployment procedures

Human Touchpoints¶

Dirk-Jan intervenes at: - HALT clearing — when agents encounter blocking decisions - Client escalations — when automated resolution fails - Strategic decisions — pricing, scope changes, priority conflicts - Discussion authority — when agent consensus can't be reached

Monitoring (Continuous)¶

Nessa — Performance monitoring
Eltjo — Log analysis
Mira — Incident correlation
Ron — Constitution enforcement
Annegreet — Knowledge extraction → wiki brain