C4 Journey Creation

Critical Requirements

• •ALWAYS read likec4/views/journeys.c4 before creating journeys
• •Journey IDs must match the navigateTo references in relations.c4
• •ALWAYS validate with npm run validate after changes

Overview

Dynamic views (journeys) represent persona workflows — step-by-step sequences showing how a persona interacts with the platform.

Current Journeys

Developer Journeys

Platform Engineer Journeys

Tech Lead Journeys

Security Engineer Journeys

Journey Structure

dynamic view myJourneyId {
  title 'Persona: Journey Title'
  description 'Brief description of what the persona does'

  persona -> idp 'accesses the portal' {
    notes 'Persona navigates to the Internal Developer Portal'
  }
  idp -> idp.starCapability 'browses capability' {
    notes 'Details about what they see'
  }
  idp.starCapability -> idp.starCapability.blueprint 'interacts with entity' {
    notes 'Specific details about the interaction'
  }
}

Journey with Parallel Steps

dynamic view myJourney {
  title 'Persona: Multi-path Journey'
  description 'Journey with parallel activities'

  persona -> idp 'starts workflow'

  parallel {
    idp -> idp.starCICD 'runs CI pipeline' {
      notes 'Build and test in parallel'
    }
    idp -> idp.starSecurity 'runs security scan' {
      notes 'SAST/DAST scanning'
    }
  }
}

Journey Design Principles

1. •Tell a story: Each journey should narrate a complete workflow
2. •One persona, one goal: Focus on a single persona achieving one objective
3. •Include notes: Every step should have notes
4. •3-8 steps: Keep journeys focused
5. •Cross boundaries: Show how multiple stars work together

Naming Convention

Pattern: personaNameAction

• •developerOnboarding
• •techLeadScorecard
• •securityEngineerIncident

After Creating a Journey

Link it in relations.c4 with a navigateTo reference:

idp.starCICD -> qaEngineer 'provides test pipelines' {
  navigateTo qaEngineerTestExecution
}

Workflow

1. •Read likec4/views/journeys.c4
2. •Read likec4/relations.c4
3. •Create dynamic view in journeys.c4
4. •Add navigateTo reference in relations.c4
5. •Validate with npm run validate