A module you cannot switch on yourself
Bid-On is an allocation with a signed agreement behind it, not a feature flag. A tenancy whose agreement ends keeps the read and loses the write, because the record of what was sent to a buyer has to outlive the subscription.
Most software sells a module as a switch. Somebody ticks a box in billing, a flag flips, and the feature appears. That is fine for a reporting add-on and wrong for this one, because what Bid-On holds is other companies’ commercial material — their insurance values, their accident figures, their people’s names.
So it is an allocation. The module is restricted in the catalogue, cannot be self-activated, and is granted to a named tenancy by the platform operator. The grant carries a reason, the person who decided it, and — where the module’s own registry demands one — an agreement reference. Without that reference the allocation is refused outright. A module that holds a third party’s data under a contract should not be reachable by anybody who cannot name the contract.
A grant has a life: scheduled, active, expired, revoked. The interesting part is what happens at the end of it, and it is the part most entitlement systems get wrong by being simple.
When an agreement ends, the write path closes and the read path does not. A provider whose Bid-On agreement lapsed last year may still be asked by an adjudicator, an auditor or their own insurer what exactly they submitted on a customer’s behalf two years ago. A platform that answered “that module is switched off” would be destroying a record it was trusted to keep in order to enforce a billing state. The distinction is held in the code as two separate things — what a tenancy has been granted, and what it still holds — and every read checks the second while every command checks the first.
Revocation is different from expiry on purpose, and both are different from never having held it. A tenancy that was never allocated the module is refused on a read as well, because there is nothing there to read.
The practical effect for a buyer of this software is that turning the module on is a conversation and turning it off is not a cliff. Neither of those is a feature anybody asks for in a demonstration. Both are the reason a contractor’s commercial director will sign the form.
See the record being made rather than described.
Launch the demo environment