This sounds far too simple for something as complex as dealing with unsolicited attendance notification injections occurring at randomly defined intervals again

This sounds far too simple for something as complex as dealing with unsolicited attendance notification injections occurring at randomly defined intervals against a primary public<>private security surface. Particularly when you consider that some of those attendance injections may contain potential threats or unsolicited commercial messaging, or be designed to cause interference with predefined private processes, or even be designed just to consume processor cycles in unnecessary communication processing across the security layer. While I like your implementation suggestion it feels a little lightweight for something this important. Please revisit the scope and come back with a more fully fleshed out project proposal.