Booking platform / Local / development engineering note
Product and control-plane boundaries.
A development booking platform with separate product, administration, and marketing workspaces in one monorepo.
The product problem.
The platform keeps customer-facing runtime behaviour separate from administrative release and configuration authority. Shared topology and contract packages define the host, route, and API relationships across those workspaces.
The implementation boundary.
The product workspace handles directory, storefront, guest, and owner flows. The admin workspace owns drafts, approval, configuration publication, and activation. The marketing workspace has its own bundle and handoff boundary. These are separate deployable responsibilities within the current monorepo, not separate repositories.
Current status.
Development is the current program stage. Later-stage lanes remain deferred, and internal owner/admin endpoints are not public portfolio destinations. The engineering story here is the deliberate separation between running a product and having authority to publish or activate it.