Locations — Behavior

State

Single boolean is_active:

DELETE /locations/:id performs update set is_active=false, never DELETE FROM.

Invariants

• Org-direct ownership — locations.organization_id is the boundary. Every read/write filters on it (and(eq(locations.id, id), eq(locations.organizationId, orgId))).
• No hard delete — deactivation only. Historical sessions retain a valid FK.
• Capacity does not gate bookings — location.capacity is independent of class_session.capacity. Booking checks only the session’s capacity.
• Tier limit checked at create only — moving from a higher tier down does not auto-deactivate excess locations. (TODO: verify behavior at tier-downgrade — there’s no explicit guard found.)
• Coords are an all-or-nothing — service does not reject saving only latitude without longitude; both are nullable. GPS check-in is what enforces both must be present.

Golden paths

Owner: add a branch

1. /dashboard/settings/locations (or onboarding flow).
2. Click “Add a location”. Form: name, address (autocomplete fills city/country/lat/lng), capacity.
3. POST /organizations/:orgId/locations. Tier check runs first.
4. Row inserted; appears in selector when creating sessions.

Owner: deactivate

1. Click delete. DELETE /organizations/:orgId/locations/:id.
2. is_active=false. Removed from selector.

Edge cases & error states

Side effects

None outside the row mutation. No events, no notifications.

Permissions

Active org membership required for all (requireMembership).