OmniAtlas
Demo WorkspaceRepositories / PulseOps
Incident management platform
PulseOps is an incident-response platform organized as a web application, an HTTP API, background workers, and shared packages. Incident mutations enter through API routes, move through use-case services, and persist through repositories before asynchronous delivery begins.
UI routes depend on API entry points and shared request contracts. API routes own authentication and validation, services own orchestration, repositories own persistence, and workers own retryable side effects. Audit events are committed with incident mutations, while notifications and realtime updates begin only after the core state transition succeeds.
Execution paths
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.
Change surface
HTTP incident routes and request validation boundary.
Worker entry point for notification jobs.
Reads a bounded incident timeline for the detail screen.
Fans incident events out to subscribed clients.
Working conventions
17 named architectural layers represented in this snapshot.
Incident detail and timeline route.
Runtime boundaries
Reads a bounded incident timeline for the detail screen.
HTTP incident routes and request validation boundary.
Fans incident events out to subscribed clients.
Incident detail and timeline route.
Incident creation form and client-side submission boundary.
Workspace incident list route.
