Feature Package PK-06 — Amenities & Common-Area Booking
Status: Package Specification
Domain: Amenities / Resident Experience
Maps to: Process 3 (Schedules & Resource Booking), Playbook (amenity booking lifecycle)
External integration: Synapse (amenity announcements), access control
1. What This Package Does
Gives residents and the concierge one system for booking shared amenities — gym, pool, clubhouse, function room, co-working spaces — with time-slot holds, no double-booking, and resident verification.
2. Features & Functionality
| Feature | What it does | Who uses it | What stands behind it |
|---|---|---|---|
| Amenity catalog | Each amenity (gym, pool, clubhouse, tennis court) is a resource with capacity, rules, booking window | Concierge, residents | cns://resource/common-area; resource_edge amenity→building |
| Time-slot booking | Resident books an amenity for a date/time slot; time-bounded lease prevents double-booking | Resident, concierge | cns://claim/type/real-estate/amenity-booking; truth_edge resident→amenity lease |
| Resident verification | Booking only allowed for verified residents/tenants of the unit | Concierge, system | Ownership/tenancy edge check (PK-02/PK-05) |
| Guest passes | Resident can book amenities for guests with visitor limits | Resident, concierge | Guest claim linked to resident; access rights (PK-09) |
| Cancellation & waitlist | Booking can be cancelled; slot released; waitlist notified | Resident, concierge | Lease released; NATS stream notification |
| Amenity status | Operational / under maintenance / closed status; residents see live status | Residents, concierge | resource status; NATS streaming |
3. Workflow (Amenity Booking)
- Resident selects amenity and slot → booking claim created; amenity lease bound for slot
- System verifies resident is owner/tenant of a unit in the development
- Booking confirmed →
fn::poce::finalize_session; confirmation sent - Resident checks in at amenity (access control or concierge)
- After slot ends, lease released; amenity available for next booking
- If amenity under maintenance, bookings blocked; residents notified
4. Guard Rails
- No double-booking of an amenity slot (lease conflict check)
- No booking without verified resident/tenancy
- No booking while amenity status is
UNDER_MAINTENANCEorCLOSED - Guest bookings respect visitor limits and require host sponsorship
- If access control is unavailable → fail closed; no fake access grants
5. Evidence & Audit
- Amenity booking claims, amenity leases, verification records, cancellation logs, PoCE receipts