AlertStatus

Owner context: alerts | Entity: Alert | Field: status | Values: 2

Status of an operational alert raised against a shift (duplicate detection, unusual conditions, etc.). The simplest state machine in the system: a boolean dressed as an enum.

States

State	Terminal	Description	Entry condition
open	No	Alert raised, not yet resolved	Initial state (Alert.create())
solved	Yes (sink)	Alert resolved by a user or by the system	Alert.setSolved(userId)

Helpers: isOpen(), isSolved(). No isFinal(), no canTransition(), no transition matrix.

Transitions

Transition Table

From	To	Trigger (service)	Invariant / guard	Side effects
(new) → open	AlertCreator	No pre-existing alert with the same (alertType, shiftId) — deduplicated at creation time	Emits AlertCreatedDomainEvent
open → solved	AlertUpdater via AlertsUpdaterController	userId must resolve to an existing user in users	Sets solvedBy to the user id; updates updatedAt

Invariants

1. Initial state is always open — Alert.create() hardcodes AlertStatus.OPEN.
2. Only forward — the only transition is open → solved. There is no reopen, no escalate, no cancel.
3. solved is a true sink — nothing moves an alert out of solved.
4. Dedup at creation — AlertCreator refuses to insert a second alert with the same (alertType, shiftId) pair. If you see a single alert for a shift, you cannot be sure how many underlying incidents it represents — it was created once and never updated.
5. solvedBy carries two kinds of value — the entity models Id | null | 'system': a user id, unsolved, or the literal string 'system' for automated resolution. The AlertUpdater service only sets user ids; the 'system' branch is set elsewhere (admin scripts or batch fixes) and should be documented if it starts being used more actively.
6. No solved event — only AlertCreatedDomainEvent is emitted. Solving an alert mutates the entity without publishing a domain event. If a consumer needs to react to resolutions, it must poll.

Code Pointers

• Value object: packages/alerts/domain/valueObjects/AlertStatus.ts
• Entity: packages/alerts/domain/entities/Alert.ts (create, setSolved)
• Creation (with dedup): packages/alerts/application/services/AlertCreator.ts
• Resolution: packages/alerts/application/services/AlertUpdater.ts
• HTTP surfaces: packages/alerts/infrastructure/controllers/AlertsUpdaterController.ts, packages/alerts/infrastructure/controllers/UnresolvedAlertsFinderController.ts
• Created event: packages/alerts/domain/events/AlertCreatedDomainEvent.ts

Related

• Owner context: alerts
• Resolver context: users (provides the user id that signs the resolution)
• Subject context: shifts — every alert references a shiftId