Introduction

Directory

Source of truth for organisations, people, locations, login, and per-service user types.

Binding: DIRECTORY. Port 8780. JWT claims: orgId, actorId. There is no actorType in the token — domain Workers load the role from GET /v1/memberships?service=....


What it owns

  • Organisation id, display name, and status
  • Users (login accounts) and org-scoped user profiles
  • Locations with kind: workplace, venue, construction_site, shop, other
  • service_memberships — assigns each person a user type per service (admin, area-manager, manager, member, or a custom slug)
  • Domain events: PersonUpserted, PersonDeactivated, MembershipChanged, LocationUpserted, OrganisationUpserted

Register with POST /v1/auth/register (creates org + admin membership atomically). Domain APIs ingest projections via POST /v1/directory/ingest.


What it does not own

CapabilityOwner
Legal name, timezone, currency, departmentsHR
Venue brands, checklists, tasksVenue
Training skills and readinessTraining
Solver demand and published assignmentsPlanning
Tickets and SLATickets
Physical equipment assetsExpense
Signage devicesSignage
Per-service custom access role definitionseach domain Worker (/v1/access-roles or Venue /v1/roles)

See the Directory API reference.