Operations

The Operations Aether covers the day-to-day running of your estate — who’s on call, what to do when something breaks, how planned change is managed, and the record of what’s happened.

The Incidents list with severity, status, and assigneepublic/screenshots/operations-incidents.png

How it fits together

• Foundations come first — On-Call Schedules say who responds, Runbooks say how, and Known Issues capture recurring operational knowledge.
• Planned activity — Maintenance Windows and Change Requests — is scheduled ahead of time.
• Unplanned activity — Incidents — draws on the foundations: an incident reaches for the relevant runbook and known issue.

Note

Every record carries an id (UUID), createdAt, and updatedAt — omitted from the field tables below. List endpoints accept page, pageSize, search, sort, and order, and return { data, total, page, pageSize, hasMore }. search matches name and description; sort accepts name (default) or createdAt.

Modules

The foundations — On-Call Schedules, Runbooks, and Known Issues — are most useful in place before they’re needed. Planned activity (Maintenance Windows, Change Requests) is scheduled ahead; unplanned activity (Incidents) is the record of what actually broke.

On-Call Schedules

Rotations and coverage — who is responsible, and when. Each schedule ties a person to a window of time and an optional rotation label.

Fields

Field	Type	Notes
name	string · required	Schedule name.
personId	uuid → People	The responder. FK cleared (set null) if the person is deleted.
startTime	timestamptz	Start of coverage. Nullable.
endTime	timestamptz	End of coverage. Nullable.
rotation	string	Free-text rotation label (e.g. weekly, follow-the-sun).
description	string	Free-text notes.

API — GET/POST /api/on-call-schedules, GET/PATCH/DELETE /api/on-call-schedules/{id}.

The on-call schedule with responder rotationspublic/screenshots/operations-oncall.png

Runbooks

Operational procedures — the documented steps for handling a known situation. The procedure body lives in content; category groups related runbooks.

Fields

Field	Type	Notes
name	string · required	Runbook title.
category	string	Grouping label.
content	string	The procedure body.
ownerId	uuid → People	Maintaining owner. Cleared (set null) if the person is deleted.
description	string	Short summary.

API — GET/POST /api/runbooks, GET/PATCH/DELETE /api/runbooks/{id}.

A runbook with its procedure bodypublic/screenshots/operations-runbooks.png

Known Issues

Recorded operational knowledge — recurring problems and their workarounds, so the same issue isn’t re-diagnosed twice.

Fields

Field	Type	Notes
name	string · required	Issue title.
severity	string	Defaults to medium.
status	string	Defaults to open.
affectedSystem	string	The system or service impacted.
workaround	string	The interim mitigation.
description	string	Free-text detail.

API — GET/POST /api/known-issues, GET/PATCH/DELETE /api/known-issues/{id}.

Maintenance Windows

Planned activity windows — the agreed periods for disruptive work, with an impact note and a lifecycle status.

Fields

Field	Type	Notes
name	string · required	Window name.
startTime	timestamptz	Window opens. Nullable.
endTime	timestamptz	Window closes. Nullable.
status	string	Defaults to scheduled.
impact	string	Expected disruption.
description	string	Free-text detail.

API — GET/POST /api/maintenance-windows, GET/PATCH/DELETE /api/maintenance-windows/{id}.

Change Requests

Planned change records — what’s changing, when, the assessed risk, and who asked for it.

Fields

Field	Type	Notes
name	string · required	Change title.
status	string	Defaults to draft.
risk	string	Defaults to low.
requestedById	uuid → People	Requester. Cleared (set null) if the person is deleted.
scheduledFor	timestamptz	Planned execution time. Nullable.
description	string	Free-text detail.

API — GET/POST /api/change-requests, GET/PATCH/DELETE /api/change-requests/{id}.

The Change Requests list with risk and statuspublic/screenshots/operations-change.png

Incidents

Unplanned activity records — severity, status, and a timeline for things that break.

Fields

Field	Type	Notes
name	string · required	Incident title.
severity	string	Defaults to sev3.
status	string	Defaults to open.
detectedAt	timestamptz	When the incident was noticed. Nullable.
resolvedAt	timestamptz	When it was resolved. Nullable.
assignedToId	uuid → People	The owner working it. Cleared (set null) if the person is deleted.
description	string	Free-text detail.

API — GET/POST /api/incidents, GET/PATCH/DELETE /api/incidents/{id}.

Note

The severity, status, and risk columns are stored as free text with a server-side default (e.g. incident severity → sev3, status → open); the API does not yet constrain them to a fixed enum, so any string is accepted. Every create, update, and delete across these modules is recorded by the platform-wide activity log at admin /api/activity.

API

Resources are exposed under /api/on-call-schedules, /api/runbooks, /api/known-issues, /api/maintenance-windows, /api/change-requests, and /api/incidents — all behind auth and operations Aether access. See the API reference.