A stage is a shop station you reuse across jobs, such as Welding or Paint. It
belongs to one department (shopId).
Deliverable stage nodes point at one through data.stageId. See
domain concepts for how that linkage works.
Search columns: name
Standard CRUD applies. See standard endpoints.
Fields
Every property the API returns for a stage.
Stages carry no identifier. They are keyed by name within
a department. Both isArchived and archivedAt describe archive state.
Capacity
maxOrderCapacity is how many orders the station holds at once. Planning uses it
to tell you when a station is oversubscribed, so a value of 0 means the station
takes no work rather than unlimited work.
What you can write
Everything else in the table above is set by BuildingSwell.
Deleting
DELETE /stage/{id} is destructive.Permanently removes the station. This is not the archive operation and it cannot be undone.In practice this fails with 409 whenever a team or a route step is still assigned to the station, because those links are ON DELETE NO ACTION. Reassign them first, or archive the station instead.When the delete does go through, deliverable stage nodes are not protected: they point at a station through data.stageId, which is a JSON value rather than a foreign key, so those nodes keep an id that no longer resolves. Any QC entry referencing the station has its stageId set to null.
