Files
govoplan-booking/docs/BOOKING_DOMAIN_BOUNDARY.md

1.3 KiB

Booking Domain Boundary

Purpose

Booking procedures for rooms, resources, counters, equipment, appointment types, public slots, internal reservations, waiting lists, cancellations, attendance, and no-shows.

Owns

  • booking procedures
  • public and internal slot allocation
  • waiting lists
  • reservation lifecycle
  • attendance and no-show facts

Does Not Own

  • resource inventory master data
  • calendar event storage
  • generic approval engine

Integration Candidates

  • resources
  • calendar
  • appointments
  • scheduling
  • mail
  • notifications
  • files
  • workflow
  • approvals
  • portal

Seed State

The current repository state is intentionally small:

  • module manifest and entry point
  • tenant-level permission definitions
  • manager and viewer role templates
  • documentation topic describing the module boundary
  • Gitea issue workflow templates
  • manifest contract test

No runtime API, database model, migration, WebUI route, or navigation item is registered yet. The first implementation slice should preserve the boundary above and only add user-visible surfaces once the workflow model is clear.

First Implementation Slice

Define booking type, slot, reservation, attendance, cancellation, and no-show concepts, then add APIs for tenant-local booking configuration.