this guide is a sort of '''turn by turn directions''' where we go point-to-point (P2P) over METAHEAP. with the foundation as it stands; it relies heavily on first-only-instances and going really fast.

in order to pull off this: maneuver ... we need cat like performance (POKE/MEOW) --> at the scale of gaming (PING/PONG) // with the physics of speed on our side.

by ditching secrets, leaving everything as plain text, and using layers when needed \\ HT's foundation scales up while it's database commands grow stronger.


between each layer exists standard BIND & BOND protocols; this is like saying, "there exists spaces between words" which is true but we choose not to endlessly drill down into every topic because destination is key here.

to begin, we use JavaScript as a language that can be run from the browser. press developer tools (option + command + i) then open the console tab. in this box: any line of JS code can be executed at the bottom beside the '>' symbol. to follow along just copy/paste code from the examples then hit enter for results.

to start, the BEEP/HONK method is good for sending health checks between each layer. when called, BEEP checks the database using {PING/PONG} commands and then responds back HONK if there is a successful connection:

let licensePlate = '123'
let road = "Main Street"
// --with-- // vehicle
ht.lane(licensePlate, road) // transport
// --or--
// mobile: start...
// lane: transporting...
// listen: Main Street
// beep: HONK

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

there is a reoccuring pattern with the structure of HT. the naming of things are totally based off of a situation by situation bases. so, in order to see (AUTO) between each layer of the system ENCODE then DECODE methods must be used. that is like saying: the layers BIND, BEEP, PING, and POKE all function differently yet communicate with one another over standard protocols (TURN).