One schedule
Availability and confirmed bookings resolve against the same venue calendar.
Exercise venue discovery, availability, direct requests, open proposals, negotiation, confirmation, event operations, settlement, review, and repeat booking from the organizer side.
Availability and confirmed bookings resolve against the same venue calendar.
Accept, counter, decline, expiry, and cancellation are explicit states.
Conversation supports a proposal or booking; it never replaces its terms.
Price, service, payout, completion, review, and repeat intent stay connected.

18 Sep · 17:30–23:30 · 36 guests · Berlin-Mitte
Check capacity, available hours, base rate, amenities, access, house rules, and the venue owner’s operating record.
Organizer
Check capacity, available hours, base rate, amenities, access, house rules, and the venue owner’s operating record.
Venue owner
Keep the listing, schedule, pricing, and blocked dates accurate enough for a qualified request.
The organizer shortlists Atelier Mitte for a 36-person hosted mixer.
Every mutation updates the same proposal, booking, schedule, notification, and conversation context.
Every branch preserves history, gives the next actor a clear decision, and keeps schedule, terms, messages, notifications, and settlement aligned.
Venue declines
Recorded: Decline reason + alternatives
Organizer can revise or continue the shortlist
Counter expires
Recorded: Immutable expired terms
Either side starts a new counter from the last agreement
Schedule conflict
Recorded: Conflict blocks acceptance
Venue offers another window without losing the request
Booking cancelled
Recorded: Actor, reason, policy, refund
Calendar is released and both workspaces are notified
Service disputed
Recorded: Issue record before settlement
Payout pauses while evidence and resolution remain visible
Repeat booking
Recorded: Clone confirmed context
New dates and terms create a new booking, never overwrite history