PulseOps

Incident management platform

Snapshot readyCurated exploration

Upstream: Synthetic reference application · no upstream commit
Default branch: fixture
Revision: fixture 1.2.0
Analysis date: 2026-07-19
Fixture version: v1.2.0
Coverage: Synthetic reference application covering five incident lifecycle paths across a curated 30-file fixture.

Architecture map

Trace responsibilities, not just imports.

Follow persisted relationships across interface, API, service, persistence, worker, and external boundaries.

30 nodes42 relationships

Execution focus is active. Only validated nodes and relationships for Create an incident are shown.

New incident form

Interface · ui

Collects incident details and submits the creation request.

Incident API route

HTTP · api

Authenticates, validates, and forwards incident mutations.

Create incident schema

Validation · utility

Defines the accepted incident payload and validation rules.

Create incident service

Orchestration · service

Coordinates the complete incident-creation use case.

Incident repository

Persistence · database

Owns incident persistence queries.

Audit event service

Audit · service

Builds immutable actor and change metadata.

Notification dispatcher

Dispatch · service

Creates delivery commands after incident persistence.

Job queue

Queue · external

Buffers background delivery work outside the request path.

Notification worker

Worker · job

Consumes notification jobs with retry-safe handling.

Notification delivery service

Delivery · service

Selects the delivery channel and records its result.

10 nodes · 9 relationships

Focused execution

8 steps

Follows a new incident from the web form through validation, orchestration, persistence, audit logging, job dispatch, and notification delivery.

01
Submit the incident
The web form sends the normalized incident payload to the API.
Locate Evidence
02
Validate the request
The shared schema rejects malformed incident input before orchestration begins.
Locate Evidence
03
Orchestrate creation
The application service coordinates the use case inside one transaction boundary.
Locate Evidence
04
Persist the incident
The incident repository writes the canonical record.
Locate Evidence
05
Record the audit event
The audit service records actor and change metadata alongside the mutation.
Locate Evidence
06
Dispatch background work
The notification dispatcher places delivery outside the request path.
Locate Evidence
07
Consume the job
The worker consumes the typed notification command with retry-safe handling.
Locate Evidence
08
Deliver the notification
The delivery service selects the external channel and records the result.
Locate Evidence

Pan by dragging the canvas. Zoom with controls or trackpad.Back to repository overview