Public · Configurable booking platform
Booking
A multi-vertical booking platform that treats appointments, capacity and stays as different domain models while building auditability, supply-chain security and engineering evidence into the foundation.
- Niche
- Reusable booking without reducing every business to a calendar
- Core stack
- TypeScript · web applications · verifiable CI
- Models
- Appointments · capacity · stays
- Focus
- Strict rules · auditability · configuration
System view
The niche
Barbers, clinics, restaurants and hotels share the idea of booking, but they do not share the same rules.
The product is aimed at a configurable platform that can reuse infrastructure without pretending that a one-person appointment, a capacity-limited table and a multi-night stay are the same entity.
What is different
Business variability is modeled explicitly rather than hidden behind generic options.
Appointment, capacity and stay models can enforce different duration, availability and occupancy rules.
Presets provide a recognizable starting point without duplicating an entire application for every sector.
Control registries, CODEOWNERS, security policy and retained evidence make engineering decisions auditable.
CodeQL, SHA-pinned actions, CycloneDX SBOMs and provenance manifests belong to the workspace rather than a later compliance campaign.
Product & design thinking
Configuration should preserve the differences that make a business valid.
The design separates the user-facing questions—what resource, when, for how many people and for how long—from the internal rules that determine whether a reservation is valid. The interface can stay simple without weakening the domain.
The longer-term direction is for configuration, operations and audit evidence to be understandable surfaces for real operators, not only for the people who wrote the code.
Development approach
The domain model is treated like a design sketch: something to challenge with real scenarios before turning it into reusable infrastructure.
Rules are checked deterministically and the repository preserves evidence about how the artifact was built. The result is a foundation that can grow toward transactional persistence and administration without losing traceability.
A barber appointment, a restaurant table and a hotel stay become competing experiments against the same platform. If an abstraction only works for one vertical, it stays local; if it survives several, it earns a place in the shared core. Governance, security checks and retained evidence then automate the proof that the generalized behavior is still safe to change.
This replaces a conventional platform-first workflow with scenario → prototype → validate → generalize. The result is both more efficient and more creative: unusual business rules can be explored freely without turning every exception into permanent platform complexity.