Programs publication is a human review workflow. Incoming material may suggest an event, but an authorized operator decides whether the information is complete, current, and appropriate for residents.
What operators review
- title, date, time, location, and organizing group;
- whether the item already exists or conflicts with another source;
- whether a flyer or link is appropriate to publish;
- whether an RSVP, lottery, or other action is required;
- whether the source later corrected or withdrew the event.
Publication states
flowchart LR INTAKE["Incoming material"] --> REVIEW["Needs review"] REVIEW --> PUBLISH["Publish"] REVIEW --> HOLD["Hold or reject"] PUBLISH --> CORRECT["Correct or withdraw later"]
Publication is explicit. A source receipt, automated suggestion, or parsed flyer does not by itself create a resident-facing event.
What residents can rely on
- Published entries came through a review step.
- Corrections can update the subscribed calendar without a new download.
- When source material does not state an end time, the calendar may use a visible default duration.
- Registration is separate: adding an event to a calendar does not complete an RSVP or lottery entry.
Pub event sharing
Pub may display selected published events through a read-only integration. That projection contains only the event fields needed by the public Pub surface; it does not grant Pub access to House Desk administration or resident subscription records.