These are some notes that bear on the section (clocks). They may not contradict it. This belongs somewhere else!

Since programs have no inaliable rights, they have no rights to real time. Some may imagine that their programs have an implicit right to read the 370 TOD in order to enforce a contract arangement. This requires cooperation of the machine operator, however.

Desiderata:(incompatible)

A clock object should give strictly increasing values.

It should be close to WWV.

It should look like the 370's TOD values.

It should conform to POSIX.

Consequences of multiple clocks:

There will be sets of programs designed to share one clock object where we desire to grant them separate clocks. What is necessary in this case?

At the boundary between regimes with different clock objects one may post a "clock justification" facility that guarantees that clock values will appear to increase. This may be done by conbinations of: Delaying the message, Adjusting some clock object upwards, preventing the passing of clocks.