BOOM79: A deadline can remain open after places are filled

BOOM79 activity reading: distinguish a closing time from a place limit through a 20-place example, cancellations and a clearly defined waiting list.

“Registration closes at 18:00, so there must still be a place at 17:00.” The conclusion does not follow if the notice also limits capacity. For BOOM79 readers, a closing time and a place count answer two different questions: when requests stop being considered, and how many participants can be accommodated. You can be within the time window while the available places have already been assigned to other people.

## Twenty places, two limits

Consider a fictional guide workshop with twenty places. Requests may arrive until 18:00 IST on 25 October 2026, but allocation stops earlier if all twenty places are confirmed. The notice says both conditions apply. At 14:00 there are twelve confirmed participants. At 15:30 there are nineteen. At 16:10 there are twenty. The clock still has one hour and fifty minutes to run, yet no unassigned place remains under these facts.

A reader arriving at 17:00 meets the time condition but not the availability condition. That reader has not proved that the workshop should accept a twenty-first person. Capacity did not grow because the deadline was later than the last allocation. Conversely, if only sixteen people are confirmed at 18:00 and the notice does not extend requests, four unused places do not automatically keep registration open. Time and capacity can each stop the process independently.

We read “until the deadline or until places are filled, whichever comes first” as a pair of stopping events. The earlier event governs closure in that particular rule. In our example, full allocation happened first at 16:10. If the announcement instead says requests continue into a waiting list, that is a different instruction for later requests. A reader needs the actual waiting-list rule before treating a submitted request as either confirmed participation or an immediate rejection.

## A cancellation is not an allocation

Now suppose one confirmed participant cancels at 16:40. The number of confirmed participants falls to nineteen. It does not follow that every reader viewing the page at 16:41 can claim the place. The notice might assign a released place to the first eligible person on a waiting list, or it might provide another process. The arithmetic identifies one released place; the allocation rule identifies who, if anyone, receives it next.

For the BOOM79 exercise, define a waiting list explicitly: after capacity is reached, later valid requests are ordered by receipt time, and released places go to that order. Two requests arrive at 16:15 and 16:25. Under this invented instruction, the 16:15 request is considered first for the cancellation. The later request does not become confirmed merely because it arrived before 18:00. A valid request, a waiting position and a confirmed place remain different states.

Suppose the first waiting reader accepts the released place at 16:50. Confirmed participation returns to twenty. There was a brief period with nineteen confirmations, but that gap did not create a general reopening. A useful record contains the cancellation and its subsequent allocation, not just a screenshot of the count during the gap. This explains why two readers looking at different times may report different counts without either observation being false.

A notice may also count requests rather than people. If a page displays twenty-three requests, the number could include confirmed participants and waiting readers, depending on its labels. Do not subtract that total from capacity without understanding what is being counted. In our defined workshop, twenty confirmed plus one still waiting equals twenty-one recorded people after the cancellation has been filled. The waiting count does not increase the workshop's capacity and should not be presented as extra confirmed places.

## Resolve the late-arrival question

At 17:00 in the finished example, there are twenty confirmed participants, one waiting reader and one hour before request closure. The statement “there is still time” is true. The statement “there is an unassigned place” is false under the specified record. The reader can understand both facts at once. If asking about current details elsewhere, the exact missing information would be the current allocation state and the rule for later requests, rather than the deadline alone.

The BOOM79 case ends with a simple distinction: time left is not the same as space left. A deadline marks the end of an opportunity to make a request under the stated process; it does not manufacture capacity. A place count describes allocation; it does not erase a deadline. Read the two conditions together and even a cancellation can be explained clearly, without promising admission to someone whose request has not been confirmed.