MOVE is the equivalent to MOBILE & LANE. you will see this as a reoccuring theme aswell; which is the compressing and decompressing of methods. keeping multiple copies around helps with fault talerance against natural disasters, sensorship, outages, and the like.


one thing we have to understand is this: what situation we are trying to wake up from; are we dealing with chaos or are we dealing with order? one clever method is just to brute force down every possible path. notice how there are --or-- comments in every block of JS code to show how there are many possible routes that one can take to achieve same thing.

let id = '0987654321' // license plate
let freeway = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz" // road
// --with-- // vehicle
ht.lane(id, freeway) // transport
// --or--
// --or--
ht.move(id, freeway).beep()

these semantics can be thought of as one poke at a time vs two pokes at a time ... :) "semantics" -- well, you can't write clean code on top of a codebase that is already clean. it would be like trying to program with invisible ink.

// mobile: start...
// lane: transporting...
// listen: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
// beep: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
// beep: HONK

move functions at a high level because it relies on these low level commands in order to work:

frontend loop (FL) like flow-based programming is essentially a way of programming where you have a network of black boxes each with their own inputs and outputs. these black boxes are kind of like functions except they work on a distributed scale. because of this each box is capable of replicating, being modified, and connected endlessly with one another.

now that we have the ability to MOVE --> the ability to TURN ... and the ability to BEEP // this opens the door for us to transfer between manual and AUTO.