Proposal: Resting the Machine
Self-kill. —Axeling
Adminned at 02 May 2007 21:25:54 UTC
in rule 2.3.2 “Variables” change the following:
*Name: The name by which the Variable is refered (and any abbreviations by which it may be refered).
*Creator: The name of the Worker(s) considered responsible for adding the Variable to the Machine.
*Possible States: A description of the possible states the variable may be in. If appropriate, a description of the order in which the variable advances may be included.
*State: The current State of the Variable (which must always be one of the possible states described in the previous bullet-point).
to:
*Name: The name by which the Variable is refered (and any abbreviations by which it may be refered).
*Creator: The name of the Worker(s) considered responsible for adding the Variable to the Machine.
*Possible States: A description of the possible states the variable may be in. If appropriate, a description of the order in which the variable advances may be included.
*State: The current State of the Variable (which must always be one of the possible states described in the previous bullet-point).
*Default State: The Base State which, when the Machine is Standing By, the Current State of the Variable is returned to (Note that setting Variables to their Default State does not Cause the Machine to become Runnig).
Because Ideally the machine will be reset each time, not started up again and again.
Agree with all of Hix’s points. My thinking on _my_ proposal was that Parts are either Activated or Deactivated, and they all become Deactivated once the Machine goes into Standby, but all Variables keep their states unless expressly changed.
Hix:
Also feasable would be a Rule containing a list of Variables, and saying that any Variable on the list can be reset without causing the machine to become Running (possibly subject to restrictions such as only once per day per Worker). Better yet, instead of a list, there can be a [resettable] descriptor which can optionally be added to a variable.