Feature Package PK-05 — Events & Banquets
Status: Package Specification
Domain: Events / Catering / Function Space
Maps to: Playbooks H-5 & H-6
External integration: Gotenberg (PDF export), Synapse (client chat), ERPNext (event invoicing)
1. What This Package Does
Gives the events team one system for booking function spaces, managing banquet event orders (BEOs), designing event concepts with mood boards, and settling post-event — replacing scattered contracts, email threads, and unversioned design files.
2. Features & Functionality
| Feature | What it does | Who uses it | What stands behind it |
|---|---|---|---|
| Function-space booking | Book banquet hall, boardroom, or terrace for a date range with an F&B minimum; time-bounded lease prevents double-booking | Events manager, client | cns://claim/type/hotel/event; cns://resource/function_space; lease conflict check |
| BEO (banquet event order) | Event details, menu, guest count, AV needs, deposit status captured as a claim with milestone approvals | Events manager, banquet chef | Milestone approvals as PoCE steps |
| Event design / mood board | Curate visual direction (layout, color palette, floral, AV) with pinned assets; client sign-off gate | Events team, client, designer | cns://creative/mood_board; MinIO assets + SHA-256 |
| PDF export | Export a signed, presentation-grade event deck or BEO PDF | Events manager | Gotenberg /services/playbook/moodboard/{board_id}/export-pdf; PDF hash on claim |
| Client communication | E2E-encrypted discussion room bound to the event thread | Events manager, client | Synapse Matrix room; integration_entity mirror |
| Post-event settlement | Consumption logged to folio lines; escrow release for corporate/group contracts | Finance, events manager | H-1 folio lines; federated PoCE if client is a separate org |
3. Workflow (Event Lifecycle)
- Event claim created (function space, dates, F&B minimum, guest count)
- Space reserved via time-bounded lease (no double-booking)
- Milestones: menu sign-off, BEO approval, deposit confirmation (PoCE steps)
- Mood board designed; client annotates; PDF exported via Gotenberg; client signs off
- Event executes; consumption logged to folio lines
- Post-event settlement; escrow released if group contract (federated PoCE)
4. Guard Rails
- No space double-booking (lease conflict check)
- No event start without deposit confirmation
- No asset pinned without SHA-256 integrity
- No auto-cancellation; human approval required
- No client delivery without sign-off
5. Evidence & Audit
- Event claim, lease binding, milestone PoCE steps, mood-board asset hashes, exported PDF reference, settlement receipt