strong priority order

This page helps specify Living Platform itself to living ontology constraints. It is CC-by-nc-sa by the Efficient Civics Guild, some rights reserved.

A list in strong priority order must be numbered; it is recognizable due to those numbers. The most common use of such a list is to specify an algorithm or less rigorous stepwise process as part of a protocol.

The numbers imply some commitments to keep the output of one step compatible with the input of the next. Industrial ecology, for instance, commits to the co-location of industries to ensure that this is convenient.

Unlike alphabetical order and weak priority order, only those accepting the commitment to work out details of the implications of the change in commitments, that is, correcting the rest of the instructional capital around it relying on it, should change a strong priority order. It is akin to doing damage to source code that is in use, and strongly frowned on, especially by the entity that maintains and guarantees those instructions useful.