Pub event surfaces use a limited feed of published event information from House Desk. Editors review events at the source; Pub presents that approved information alongside Pub-specific hours and announcements.
What patrons receive
Depending on the event, Pub surfaces may show:
- the public title and description;
- start and end times;
- a public location or participation note; and
- approved display artwork.
The feed does not give Pub access to subscriber records, editor accounts, private review notes, or other House Desk administration data.
Publishing flow
flowchart LR EDITOR["Editor reviews an event"] --> SOURCE["House Desk publishes a limited event view"] SOURCE --> CHECK["Pub validates the complete update"] CHECK --> WEB["Pub website"] CHECK --> SCREENS["Venue displays"]
House Desk remains the source of truth for event content. If an event title, time, location, or image is wrong, an authorized editor should correct it there rather than applying a Pub-only copy.
Technical boundary
Pub accepts only the documented, presentation-ready event shape and validates an update before using it. A malformed or incomplete response is not partially merged into public data. When current data cannot be trusted, a surface keeps its last useful view when appropriate or shows an unavailable state.
The public events response combines those published events with Pub-owned presentation data. See Public API reference.
Why this split exists
- Event review happens once, at the owning product.
- Pub receives only the fields it needs to display the event.
- A change to Pub permissions cannot grant House Desk permissions.
- Patron surfaces can remain stable even as the two products evolve independently.
Related: Architecture · Venue displays