Monday, February 12, 2007

Modelling Perceptrons and Actirons

I use a hybrid database modelling methodology of ORM and E-R and over the weekend I started to model what a Perceptron and an Actitron is and how they relate to the Trail.

Here are some of the points that came out of it:
  • A "perceptron" is a unit of perception that is picked up by a "sensor".
  • A sensor is a software device for capturing perceptrons.
  • The sensor must send where the perceptron was captured, when and who the sensor operates for.
  • The perceptron may be observed but is not seen unless it goes via someone's short term memory buffer (7 +/- 2).
  • A sensor passes perceptrons to a user or group of users or another sensor.
  • An "actitron" is a unit of action which may be performed by a person or a sensor.
  • An action performed by a person is always "seen" - but this may not be the case for a sensor.
  • Over time a user's trail is filled with seen perceptrons and seen actitrons.
  • Actitrons can happen on Things.
  • A Thing is an object in your perceptual environment.
So what does this mean? Well by creating sensors your potential perceptual environment can be expanded (i.e., see more). Your own actions are remembered and can then be temporally associated with other Things which means you can make lighter context switches as time goes by (i.e., juggle more). It means you can also add future events into your trail by putting something in front of a sensor at the right time.

No comments: