OmniAtlas
Demo WorkspaceRepositories / PulseOps
Incident management platform
Select a flow to inspect its ordered source evidence.
Traces a responder acknowledgement through authorization, persistence, audit history, and realtime publication.
Follows a new incident from the web form through validation, orchestration, persistence, audit logging, job dispatch, and notification delivery.
Shows how the SLA job locates overdue incidents, resolves owners, persists severity, audits the change, and notifies responders.
Explains how the incident detail page reads a bounded projection across incident and audit records.
Follows an asynchronous notification from dispatch through queue consumption and the external email adapter.
Focused flow
Follows a new incident from the web form through validation, orchestration, persistence, audit logging, job dispatch, and notification delivery.
The web form sends the normalized incident payload to the API.
The shared schema rejects malformed incident input before orchestration begins.
The application service coordinates the use case inside one transaction boundary.
The incident repository writes the canonical record.
The audit service records actor and change metadata alongside the mutation.
The notification dispatcher places delivery outside the request path.
The worker consumes the typed notification command with retry-safe handling.
The delivery service selects the external channel and records the result.
