Tracing trajectories of component in machine phase

Gemstone metamaterial on-chip factories operate in machine phase.
Operating in machine phase is:

• essentially necessary for gemstone metamaterial technology to work and is
• a key factor for the high performance of gem-gum technology way beyond what soft nanosystems could ever deliver.

For a discussion of details see:
See: Machine phase, The defining traits of gem-gum-tec, Stiffness, ...

Machine phase means (among other things) that such a production system is fully deterministic system.

• That is: For any given time there is exactly one uniquely defined system configuration.
  
• That is: There are no branches in configuration space.

One maybe can think of the drive system like a slider on a (very complexly shaped) one dimensional rail.

So for any given atom in a gemstone metamaterial product the complete trajectory can be traced
right from where it was captured into machine phase.
The same holds for crystolecules and microcomponents. <br The trajectory of bigger components id fully traceable from the moment "inception"
from the moment of completed assembly.

Side-note:
Of at a high enough level determinism necessarily needs to end given our macroscale reality is not totally deterministic.
E.g. It can't be predicted what kind of product a user is eventually going to produce in the next production run.

How to represent the date of component trajectories

Representing the data for the whole trajectories for the diverse component trajectories in the global frame of reference would be rather impractical.

Instead for some given time combined with some given sub-component of a product one
fist looks up the mechanism that is at that moment of time responsible for keeping this component safely in machine phase.
This gives:

• The pose coordinates of the responsible mechanism and
• the rigid body pose coordinates (position and rotation) of the component in the local coordinate frame of reference.
• (and a local frames of reference for time)

To decide:
What to call the machanism responsible for keeping the component safely in machine phase?

• "owner" "onlatcher" "caretaker" "responsible mechanism" "guider" "controller"

Avoid imperative modelling

In any case a naive imperative approach of modelling is absolutely to avoid.
"Naive imperative way" means storing positions in variables making the
responsible mechanisms into "objects as actors" that look up the old positions and orientations
of components and im place update those values to represent a new time-step.
DO NOT DO THAT!!

Related

• ...