Time limits on a contract, enforced for every provider
A URDAD contract states what a service requires and what it promises. It can now state how long the service may take as well, as a time-limit pre-condition with its own exception, e.g. “a claim is assessed within three days, or it is reported as not assessed in time”.
Part of the contract, not of a process
The limit belongs to the contract, so every realization of it is held to it. The requester keeps the time, since only the requester knows how long it has waited, and no provider needs to know of the limit. A process which requests the service handles the exception like any other, or passes it on in its own terms.
What happens when it expires
The requester is answered with the exception at once. A person’s task is withdrawn from the task portal, even when someone has claimed it, a process asked for the service undoes what it did, and an answer which still arrives late is undone through the contract’s undone by. A deployment may set another duration where the model allows it.
The motor insurer and the online auctioneer example models both use time limits. How the execution environment enforces them is in the user manual.