Article 9, No Big Whoop Part IV A. THE THEORY OF EVERYTHING IS COMING UP RAINBOWS: INTRODUCING ATMs 🏧 and TATMs 🦥, Expect Mothership Day Brunch On Jesus
☕️☕️☕️☕️☕️☕️☕️☕️☕️☕️
⚠️WARNING ⚠️HARD HAT AREA: THE INITIAL CONSTRUCTION OF THIS ARTICLE IS DONE, BUT UNTIL I SEE THE SUN—the macro realm—THERE MAY BE SUBSTANTIAL MODIFICATIONS NEEDED IN THE MICRO REALM OF ARTICLE 9 THAT I COULD NOT FORESEE DURING THE CONSTRUCTION PHASE.
Coffee Talk: Mother’s Day (or as I call it: Mothership Day)
Topic 12.
Mack-on Double Jeopardy! Question: The part of The House hunting process that haunts every SouLL who wants to make an apple pie from scratch.
Mack-off Double Jeopardy! Answer: Can we ask you some specific questions?
Seriously, REALLY ANSWERING 12 SPECIFIC QUESTIONS will enable us to get from setitandforgetit—which means securing all the light-speed engines aboard the mothership ACOM, or in other words, attaching all the Baby Turtle Particles around the designated Atomic Turtle Meetball 🏧 Backbone—to full ATMs 🏧, all ready to be SETFx LOOSE in the universe to become you and me and suns and moons and planets and cats and cows and coffee beans and so forth, no big whoop.
Q&A 1 through Q&A 6 are here, in Part A.
Q&A 7 through Q&A 12 are in Part B.
☕️☕️☕️☕️☕️☕️☕️☕️☕️☕️
Q&A 1
Q: Are there any spots on the mothership ACOM (let’s start calling it the “MACOM” as we transition to speaking about full ATMs) where a lone BTP loose in the universe cannot setitandforgetit in an ATM?
A: Yes, it’s physically-impossible for a lone BTP loose in the universe to setitandforgetit in the 3-d Down direction (180-degrees) on the MACOM SheLL Compass.
Explanation:
RECALL where we left off with our ATM construction project in Topic 6, TEST 5:
We have reached two construction conclusions so far:
(i) every ATM 🏧nmust have an ATM Backbone comprising two BTPs (the ACOM and BTP1)—no more, no less—colliding head-on along the same 3DADL;
and
(ii) the two BTPs in the ATM Backbone must have the same “nominal,” aka “NORMAL,” WPD, and presumably, all of the BTPs in an ATM have the same NORMAL WPD.
Ergo, the 3-d Down direction on the MACOM must remain unoccupied by a lone light-speed engine, aka BTP, because the MACOM itself will occupy the 3-d Down direction in the ATM.
Now we can “merge” our SPECIFIC ATM Backbone Diagram and discussions with the GENERAL—simple COMMON SENSE—ATOM diagram and discussions from Article 3 to deduce the complete ATM 🏧 structure.
RECALL the simple COMMON SENSE ATOM diagram and discussions from Article 3:
Voila!
The ATM 🏧 construction project has come “full circle”!
Now—assuming that there are only 360 3-d degrees in a cross-section of the MACOM SheLL Compass, which is a simple scaling factor that we can work with—we can simply up-cycle the ATOM diagram from Article 3, with the following FOUR EDITS:
edit #1, redact the generic SAP references and add the more specific information from the ATM Backbone Diagram;
and
edit #2, add Atomic Mass BTPs (each of which was a formerly a lone BTP on the loose in the universe that collided with the MACOM in a 3-d sideways direction and got setitandforgetit status as MASS that the MACOM must forever haul around) at all of the 3-d directions on the MACOM SheLL Compass *except-for* the 3-d Down (180-degrees) direction;
and
edit #3, DRAW A FULL CIRCLE AROUND ALL OF THAT MASS (the circle represents an ATM SHELL, which implements an ATM Compass, with the ATM SHELL/Compass having ENERGY-MAIL BOXES—INTERNAL TRANSACTIONAL LOCATIONS OF THE QOL—IN EVERY 3-d DIRECTION);
and
edit #4, refer-to the whole shebang as the “First ATM Diagram”.
It might seem like an ATM would be too crowded with all of those “overlapping” BTP 3-d SheLLs in it.
But don’t forget (see Article 7) that a BTP’s 3-d SheLL—and an ATM’s SHELL as well—is A LAW, NOT A PHYSICAL STRUCTURE!
THE ONLY ACTUAL PHYSICAL STRUCTURE OF A BTP is the 423DCTCC inside of the 3-d SheLL, and the function of the 423DCTCC is to…wait for it…define one 3-d direction line on the 3-d SheLL Compass.
Ergo, it would be PHYSICALLY-POSSIBLE for an ATM 🏧 with a MACOM to include an Atomic Mass BTP in every 3-d direction of the MACOM SheLL Compass EXCEPT FOR the 3-d Down (180-degree) direction.
The overall ATM structure would have a “FLOWER OF LIFE”-like geometry, except-for the one missing “petal” in the 3-d Down (180-degree) direction.
Wikipedia explains the “points of a compass”:
We are assuming that there are 360 points per spherical compass “rose,” aka “slice” (“rose/slice,” let’s say.)
We can envision each rose/slice horizontally *and* vertically, because we need 360 roses/slices to make one spherical compass, and we’re going to end-up with duplicate slices if we try to use only horizontal or only vertical slices.
In every rose/slice, there are 358/2 3-d sideways direction lines that connect pairs of points, meaning that there are two points per line, and there is a BTP at every point.
We can’t count a BTP at the South (180-degree) point of any rose/slice, and we must count the BTP at the North (0-degree) point of every rose/slice as THE SAME BTP.
So if we omit the South and North points, i.e., the ATM Backbone points, and only count the 3-d sideways directions as points, there would be 358 points—358 BTPs—per rose/slice.
And the total number of BTPs in the 3-d sideways directions of the MACOM = 360 roses/slices x ( (358/2) lines/slice x 2 BTPs/line ) = 128,880 BTPs
So we could say that the total “ATM Skeleton Mass” = 128,880 BPTs + 2 BTPs (the MACOM and BTP1) on the ATM Backbone.
ATM Skeleton Mass = 128,882 BTPs
Skeleton Mass is what every ATM has before the BTPs get GLOWED-UP with WPD, aka MEAT.
End of Q&A 1!
☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️
Q&A 2
Q: Now we must wonder why BTPs getting GLOWED-UP with WPD would—or would not—increase an ATM’s Skeleton Mass?
A: An ATM’s Skeleton Mass is INCREASED by the NORMAL WPD of the ATM, causing the ATM to have what we could call a “MEAT AND BONES MASS,” with the Meat being the NORMAL WPD and the Bones being the BTPs.
ATM Meat and Bones Mass = NORMAL WPD x Skeleton Mass,
where NORMAL WPD = the total wave-length force (the sum of the force-values of all of the Wave-Length Logs) in the NORMAL WPD of one BTP in the ATM (e.g., the MACOM).
But that’s a mere conclusion, not an established fact, so by way of an explanation, let’s debate about that.
On the one hand, we know that every Wave-Length Log in the EM Spectrum travels at the constant speed of light, so we must wonder WHY WOULD IT MATTER—why would the Wave-Length-Log-moving WORK-LOAD INCREASE—based-on how many Wave-Length Logs were IN ONE PLACE traveling together?
But OTOH, that’s an improper APPLES-TO-ORANGES comparison of Wave-Length Log “movers”!
We cannot compare apples (Wave-Length Logs) to oranges (BTPs with WPD)!
Wave-Length Logs are NOT RELATIVE-TO EACH OTHER, and that’s why they all move themselves at the same speed (the speed of light) regardless of their force-value and regardless of how many of them are SUPERIMPOSED in one place.
BTPs have WPD comprised-of Wave-Length Logs, and the BTPs are RELATIVE-TO THE WAVE-LENGTH LOGS (Wave-Length Logs can act-on BTPs but not vice-versa) *and* the BTPs are RELATIVE-TO EACH OTHER (BTPs can all MACK-ON each other subject only to the Hierarchy of Relativity of 3-d Directions), and each BTP must *do the work* in every Pit-Stop Time-Slot of making one or more Tax Payments:
(i) a mandatory WPD Tax Payment 🔫 (that becomes Emack) to “pay for” each Wave-Length Log UPLOADED into the 3-d SheLL (the 3-d WOPR Stream Spectra 🐳 md), providing the Taxable Receivable of the *internal* force of mass to the 3-d SheLL;
and
(ii) as necessary, Moving Services Tax Payments 🌊RTSmd to “pay for” each Wave-Length Log of a Taxable Receivable Moving Service 🛳️ md that acted *externally* on the 3-d SheLL during the prior On-Track Time-Slot.
So to repeat:
apples: it DOES NOT MATTER to the experience of a Wave-Length Log how many Wave-Length Logs are IN ONE PLACE traveling together;
and
oranges: it MATTERS to the experience of a BTP how many Wave-Length Logs are IN ONE PLACE traveling together!
But that having been said, a LONE BTP ON THE LOOSE IN THE UNIVERSE isn’t going to go any faster than the speed of light—it’s not going to have a different SPEED experience—just because it has a high number of high force-value Wave-Length Logs in its NORMAL WPD (its own 3-d WOPR Stream Spectra 🐳 md), because all BTPs are also under power of FfSet 🧨 (and the FfSet-equivalent 🛳️ md contains all of the Wave-Length Logs in the entire EM Spectrum!), so a lone BTP on the loose in the universe will always be moving at the speed of light regardless of the magnitude of its own WPD.
But here’s the thing: AS FAR AS WE ARE CONCERNED FOR MOTION ANALYSIS PURPOSES, THERE IS NO SUCH ANIMAL AS A LONE BTP ON THE LOOSE IN THE UNIVERSE ANYMORE; all BTPs are found in ATMs now, where the fact that each BTP is under power of FfSet enables each BTP that did not become a MACOM to form a STRONG NUCLEAR BOMB BOND ❤️🩹 with one MACOM.
So let’s stop thinking about lone BTPs and start thinking about the experience of the MACOM of an ATM to explain why, *exactly*, BTPs getting GLOWED-UP with WPD would increase an ATM’s Skeleton Mass.
We know that the MACOM is a permanent member of the ATM Backbone, along with BTP1, and the ATM Backbone with all of the BTPs around it in every 3-d sideways direction has become ONE OBJECT BY LAW, so now the MACOM can’t move at all without being a Moving Service Recipient (“MSR.”)
And we know that when a MSP provides a Moving Service to a MSR, the MSR’s behavior depends-on THE MAGNITUDE AND DIRECTION OF THE NET FORCE experienced by the MSR.
We also know that THE MAGNITUDE AND DIRECTION OF THE NET FORCE EXPERIENCED BY THE MSR IS PARTLY DETERMINED BY THE MSR’S OWN WPD.
We further know that when the ATM Backbone is “just sitting there” experiencing ZERO NET FORCE, there are 128,880 BTPs with WPD—one potential Moving Service Provider (“MSP”) BTP in every 3-d sideways direction—“putting their weight on” the MACOM.
We still further know that when the ATM Backbone is BEING MOVED, the MACOM is A MOVING SERVICE RECIPIENT of “N” BTP WPDs (where N = the number of BTPs that are MSPs—let’s call them “WINNING MSP BTPs”—which are causing the MACOM to experience UNBALANCED NET FORCE), and therefore THE N WINNING MSP BTPs are “carrying their own weight” in a 3-d sideways direction.
So in other words, the MACOM is constantly being “put upon” by the MACOM’s own WPD, *and* by BTP1’s WPD, *and* by the (128,880 - N) BTPs with WPD in the ATM that have formed STRONG NUCLEAR BOMB BONDS ❤️🩹 with the MACOM, but are NOT “carrying their own weight”!
Ergo, WPD MATTERS to how much work it takes to MOVE THE MACOM, and ALL OF THE “BTP BAGGAGE”—BTP Skeleton Mass plus the NORMAL WPD of the “Skeleton BTPs”—that the MACOM is carrying is going to proportionally SLOW DOWN THE RATE at which the MACOM can MOVE AND BE MOVED.
In particular, THE RATE at which the MACOM can MOVE AND BE MOVED from an at-rest position (an at-rest MACOM is experiencing ZERO NET FORCE and therefore has N = 0 WINNING MSP BTPs that are MOVING THE MACOM and “carrying their own weight”) is proportional to what we could call the ATM’s “MEAT AND BONES MASS,” with the Meat being the NORMAL WPD and the Bones being the BTPs.
And to repeat: ATM Meat and Bones Mass = NORMAL WPD x Skeleton Mass,
where NORMAL WPD = the total wave-length force (the sum of the force-values of all of the Wave-Length Logs) in the NORMAL WPD of one BTP in the ATM (e.g., the MACOM).
End of Q&A2!
☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️
Q&A 3
Q: How would it be possible to determine the specific Wave-Length Logs in the NORMAL WPDs of different types of ATMs?
A: That could be done via Spectroscopy; and in fact, it is well-known that every type of atom in the “Periodic Table of the Elements” emits a unique “Atomic Spectra,” which is the same as what we’re calling an ATM’s NORMAL WPD; specifically, an Atomic Spectra comprises the different Wave-Length Logs EMITTED as an ATM’s Emack.
But the discussion of Atomic Spectras immediately raises questions about so-called Emission Spectras, Absorption Spectras, and Thermal Spectras: how, *exactly*, does each type of recognized Spectra match-up to what we’re referring to as an ATM’s NORMAL WPD, and specifically, to the different Wave-Length Logs EMITTED as an ATM’s Emack?
We’ve already deduced enough information to answer that question in some detail, but for the sake of brevity and clarity, it will be helpful to borrow an illustration of the presently-recognized types of Spectras, and simply supplement that illustration with the TOEWC’s “nutSHELL” explanation of the same phenomena:
The fact that Atomic Spectras EXIST and the fact that the TOEWC can EXPLAIN WHY is all we need to document right now, because all we need to do right now is understand how matter was formed from moving ATMs; we don’t need to try do any ANALYSIS OF THE COSMOS or of MATERIALS or of LIVING CELLS *before* we figure-out how to do MOTION ANALYSIS at the ATM level.
So fortunately, the Periodic table of the Elements gives us another solution to the problem of “weighting” different types of ATMs for COMPARATIVE MOTION purposes, to wit:
We can stipulate that the Periodic Table is an accurate list of the different types of ATMs (i.e., ATMs with different NORMAL WPDs), then we can use an ATM’s Atomic Number on the Periodic Table to *represent* the total wave-length force of the NORMAL WPD of the ATM, i.e., the sum of the force-values of all of the Wave-Length Logs in the NORMAL WPD of one BTP in the ATM (e.g., the MACOM).
That would enable us to simply CALCULATE what we could call the “ATM Relative Mass,” which is a simple way to express the ATM Meat and Bones Mass, with the Meat being the Atomic Number and the Bones being the BTPs.
ATM Relative Mass = Atomic Number x Skeleton Mass
For example, Hydrogen has Atomic Number “1” (Meat), and every ATM has the same Skeleton Mass of 128,882 BTPs (Bones.)
Hydrogen Relative Mass (“RM”) = 1 Meat x 128,882 BTP Bones = 128,882 RM
From now on, unless otherwise noted, assume that Hydrogen ATMs are shown in the diagrams and discussed in the sample calculations.
End of Q&A 3!
☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️
Q&A4
Now we’re ready to start thinking about LONE ATMs ON THE LOOSE IN THE UNIVERSE.
“This ain’t training. In training they just give you an F. Out here, you get killed.” —Frank, “Unstoppable”
Q: The mere THOUGHT of LONE ATMs ON THE LOOSE IN THE UNIVERSE gives pause and cause to wonder: IS THE ATM BACKBONE SECURE? Is the ATM Backbone UNBREAKABLE BY OTHER ATMs ON THE LOOSE IN THE UNIVERSE?
That would be wonderful, because in that case we would be FOREVER COMPELLED to treat the entire ATM as ONE OBJECT BY LAW, always counting BTP1 as mass that the MACOM is hauling, never counting BTP1 as a Moving Service Provider to the MACOM.
And MOTION ANALYSIS would become a lot simpler, too, because we could stop accounting for FfSet; as a “Legal guardian” of a collection of BTPs, an ATM must “inherit” the NORMAL WPD of the constituent BTPs (somehow, and that’s our job to figure-out in subsequent Q&As), but it would be impossible for an ATM to “inherit” FfSet, since FfSet is the “tie” that binds a single BTP to a single LL in a single Snowman of God, and AN ATM HAS NO SINGLE “CONNECTION” TO A SINGLE SNOWMAN OF GOD.
So therefore when contemplating inter-ATM interactions, we would only need to account-for the ATM’s “inherited” WPD, i.e., the constituent BTPs’ Fmack and Emack, in opposite directions along the same line.
But before we proceed to figure-out how to simplify our lives along those WPD lines, we have to OVERCOME THE FEAR that BTP1 remains a “point of vulnerability” after the ATM structure is complete (as illustrated in the First ATM Diagram); it would be A NIGHTMARE if we found out TOO LATE that our BACKBONE was going to BREAK and we had to endure a re-run of the Reverse Rube Goldberg-esque daze!
So the more specific question we must ask now is about BTP1: can we STOP WORRYING about BTP1 being a point of vulnerability in the ATM, and if so, HOW?
A: Yes, after the ATM structure is complete, the ATM Backbone is secure and unbreakable, and we must STOP WORRYING about BTP1 being a point of vulnerability; we must treat the entire ATM as ONE OBJECT BY LAW, always counting BTP1 as mass that the MACOM is hauling, because WE CAN PROVE that BTP1 is in a *unique position* in the ATM on the loose in the universe to NEVER CAUSE the MACOM’s movement.
BTP1 cannot be FORCEFULLY STEERED (it’s hemmed-in on all sides), and it’s PHYSICALLY-IMPOSSIBLE for BTP1 to CAUSE an ATM to get into a collision; indeed, as between ATMs, BTP1 cannot even become a Moving Service Recipient (and CAUSE the MACOM’s movement), since there are only three scenarios in which BTP1 could, in theory, become a Moving Service Recipient as between ATMs, and BTP1 cannot experience any of those three scenarios:
scenario (i), an ATM could tip UD and head-butt BTP1 with Fmack, i.e., apply a Moving Service to BTP1 (but this isn’t going to happen because ATMs cannot tip UD; BTP1 and the MACOM are “stuck” in the 3-d Backbone Orientation, and the 3-dUp/3-dDown directions of the 3-d Backbone Orientation have an Absolute-Relative relationship with the 3-d sideways directions, so therefore it’s PHYSICALLY-IMPOSSIBLE to cause BTP1 or BTP2 to TIP OVER by providing a Moving Service in any 3-d sideways direction during a collision, and an ATM can’t tip over if the ATM Backbone can’t TIP OVER in a collision);
OR
scenario (ii), another ATM could collide with BTP1 when the other ATM was moving in the 3-d Down direction along a 3DADL, and thereby provide a Moving Service to BTP1 from the 180-degree direction on the other ATM’s SHELL/Compass (but collisions along the 3DADL wouldn’t REALLY be a problem for BTP1, because—as discussed below, between the 🏁 icons—it’s PHYSICALLY-IMPOSSIBLE for any ATM to be EITHER a Moving Service Provider OR a Moving Service Recipient at 180-degrees on the ATM SHELL/Compass);
OR
scenario (iii), another ATM with a WPD that included some or all of the same Wave-Lengths Logs as BTP1’s WPD could give BTP1 an Emack tax-free gift (“TFG”) smack 😘 on BTP1’s Fmack while BTP1 was tipped UU, OR another ATM could give BTP1 an Emack TFG smack 👋 on BTP1’s peachy 🍑 Emack emissary while BTP1 was tipped UD (but TFG-givers wouldn’t REALLY be a problem for BTP1, because—as discussed below, between the 💰 icons—regardless of whether BTP1 was tipped UU or tipped UD, BTP1 could not become the CAUSE of the MACOM’s movement by being a TFG-receiver.)
Begin THE CLOSED DOOR🚪DISCUSSION (between the 🏁 icons) about WHY an ATM can NEITHER be a Moving Service Provider NOR a Moving Service Recipient at 180-degrees on the ATM SHELL/Compass
🏁 🏁 🏁 🏁 🏁 🏁 🏁 🏁 🏁 🏁
Spoiler Alert:
Begin short COLLISION ETIQUETTE 👍 REVIEW
NOTE that in this discussion, any reference to a “3-d SHELL,” or a “SHELL,” is intended to apply to *both*:
(i) an individual BTP 3-d SheLL, which is applying the Moving Service 🛳️ FfSet and the Moving Service 🛳️ Fmack along the same line;
*and*
(ii) an ATM SHELL/Compass that surrounds a complete set of BTP 3-d SheLLs, as illustrated in the First ATM Diagram.
RECALL that in a collision between 3-d SHELLS, there is always an equivalent amount of energy “released”—a Moving Service 🛳️ mass deposit (“md”) is “made”—from the MSP’s SHELL (which is then-applying a certain physical force in a certain 3-d direction on the MSP’s SHELL Compass), and the 🛳️ md enters into the MSR’s ENERGY-MAIL BOX (which is a location of the QOL) through an open door in the MSR’s SHELL, causing the MSR to experience a Taxable Receivable.
RECALL from Topic 7:
ALSO RECALL that a MSR BTP’s 423DCTCC will be BOINKED by the Moving Service 🛳️ md; BOINKING the 423DCTCC is how the MSP FORCEFULLY STEERS the MSR in the same direction that the MSP is heading.
But here’s the thing: ATMs don’t have their own 423DCTCC! ATMs have a MACOM, which has a 423DCTCC, and the MACOM’s experience of NET FORCE—SETFx—and in particular, DIRECTION SETFx, tells the ATM which way to go.
But here’s the other thing: it’s PHYSICALLY-IMPOSSIBLE for the 🛳️ md from an *EXTERNAL* MSP to BOINK the MACOM’s 423DCTCC, because an *EXTERNAL* MSP is actually a BTP from another mother (another MACOM), i.e., NOT a nuclear fam BTP that has formed a STRONG NUCLEAR BOMB BOND ❤️🩹 with the MACOM in the same ATM.
The precise reason why it’s physically-impossible for the 🛳️ md from another ATM—a BTP from another mother—to BOINK the MACOM’s 423DCTCC is because the MACOM is not directly behind THE BACK DOOR (at 180-degrees) on the ATM SHELL/Compass (THERE IS A HOLE DIRECTLY BEHIND THE BACK DOOR); the MACOM is, indeed, “home” at 180-degrees on the ATM SHELL/Compass, BUT the MACOM permanently resides at the center of the ATM SHELL/Compass, and a Moving Service 🛳️ md that COMES IN THE BACK DOOR (at 180-degrees) on the ATM SHELL/Compass DOES NOT HAVE TIME TO REACH the ENERGY-MAIL BOX at 180-degrees on the MACOM SheLL Compass during the On-Track Time-Slot, so then the ATM SHELL/Compass CANNOT LET THE 🛳️ md PASS out of the ENERGY-MAIL BOX at 180-degrees on the ATM SHELL/Compass, and therefore no 423DCTCC BOINKING whatsoever happens when a Moving Service 🛳️ md enters at 180-degrees on the ATM SHELL/Compass.
THE BACK DOOR 🚪 of the ATM SHELL/Compass becomes the MSR by default.
Begin PAUSE for Mini Q&A
Mini-Q: How does the ATM SHELL/Compass know that the MACOM is not behind the back door? In other words, why doesn’t the ATM SHELL/Compass allow the 🛳️ md to pass through the back door at 180-degrees on the ATM SHELL/Compass, and “get nowhere”?
Mini-A: Surely every ATM SHELL/Compass ENERGY-MAIL BOX knows WHAT TIME IT IS, and surely every Wave-Length Log has a “last sent by BTP Snowman#” timestamp indicator within it, and we can see by mere observation that the ENERGY-MAIL BOXES of the ATM SHELL/Compass are constantly detecting the Emack of every BTP in the ATM, so therefore when the ENERGY-MAIL BOX at 180-degrees on the ATM SHELL/Compass detects the Wave-Length Logs from the MACOM’s Emack, the “last sent by BTP Snowman#” timestamp indicator will automatically INFORM the ENERGY-MAIL BOX that the MACOM is one instant (one Wave-Length Log’s distance) away from the ENERGY-MAIL BOX, ergo, the ENERGY-MAIL BOX would not allow an incoming md from a MSP to pass through the back door of the ATM SHELL/Compass KNOWING that it’s PHYSICALLY-IMPOSSIBLE for the md to “get anywhere” that way, so the ENERGY-MAIL BOX would simply CLOSE THE BACK DOOR and not allow the 🛳️ md to pass through.
God: [to Job, at Job 38:11] I said, “This far and no farther will you come. Here your proud waves must stop!”
End of PAUSE for Mini Q&A
Then in every case, during the Pit-Stop Time-Slot, the ENERGY-MAIL BOX of the MSR makes a Moving Service Tax Payment 🌊RTSmd by “RETURNING-TO-SENDER” the 🛳️ md, literally reversing it and THRUSTING IT OUT of the SHELL in the opposite 3-d direction from whence it came, satisfying Newton’s Third Law of Motion.
If the 🛳️ md came in along a 3-d line, then there will be DESTRUCTIVE INTERFERENCE ☠️ between 🛳️ md and 🌊RTSmd, because the incoming 3-d line of the 🛳️ md will be the same line as the outgoing opposite-direction 3-d line of 🌊RTSmd, and it’s impossible for the same wave-lengths to survive when they’re traveling in opposite directions along the same line.
***ASIDE regarding mds that originate in 4-d***
We NOTICE that when a 4-d Spectra Assembly 🪵 enters the universe(i.e., when the 3-d WOPR Stream Spectra 🐳 md is delivered at the AIP inside of an EMPTY 3-d SheLL during the Pit-Stop Time-Slot), it’s COMING INTO THE UNIVERSE AT ONE 3-d POINT, so then when the WPD Tax Payment 🔫 is made (i.e., when the 🐳 md is reversed and THRUST OUT by the 3-d SheLL, becoming Emack, and the thrust of Emack causes the 3-d SheLL to apply the physical force of Fmack at the AIP, with Emack and Fmack together comprising WPD), the WPD Tax Payment 🔫 is OUTGOING FROM THE SAME 3-d POINT AND TRAVELING ALONE ALONG A 3-d LINE INSIDE OF THE BTP’s 3-d SheLL, and that’s why THERE IS NO INTERFERENCE between the 🐳 md and the WPD Tax Payment 🔫.
We ALSO NOTICE that the FfSet🧨-equivalent 🛳️ md originates in the 4th dimension and comes into the universe at one 3-d point, but that is a “hybrid” case, because the FfSet🧨-equivalent 🛳️ md that goes into a MSR’s 3-d SheLL during the On-Track Time-Slot *MUST COME FROM THE 3-d MSP’s SheLL*, not from the 4-d LL.
To repeat: the FfSet🧨-equivalent 🛳️ md is NOT deposited into a BTP’s 3-d SheLL during the Pit-Stop Time-Slot (i.e., during the WPD GLOW-UP process) along with the 3-d WOPR Stream Spectra 🐳 md!
*If and only if* lone 3-d SheLLs on the loose in the universe COLLIDE during the On-Track Time-Slot, an FfSet🧨-equivalent 🛳️ md will be made by the MSP 3-d SheLL into an ENERGY-MAIL BOX of the MSR 3-d SheLL; the LEGAL issue is that the 3-d SheLLs are THE TAX-PAYING ENTITIES that are colliding, and the 3-d SheLLs ARE MUTUALLY-RELATIVE, so they can both be MSPs IN THE SAME COLLISION, WHICH IS A NECESSARY CONDITION that would be impossible to fulfill if the FfSet🧨-equivalent 🛳️ md came directly from the 4-d LL, because LLs ARE NOT RELATIVE-TO EACH OTHER, AND CANNOT APPLY FORCE TO EACH OTHER!
Now we see the reason why there is DESTRUCTIVE INTERFERENCE ☠️ between the FfSet🧨-equivalent 🛳️ md from the MSP SheLL and the Moving Service Tax Payment 🌊 RTSmd from the MSR SheLL, to wit: the 3-d point at which the FfSet🧨-equivalent 🛳️ md comes into the universe WHEN A COLLISION HAPPENS during the On-Track Time-Slot is THE MSP’s ENERGY-MAIL BOX!
This means that the FfSet🧨-equivalent 🛳️ md has to “go between” THE MSP’s ENERGY-MAIL BOX AND THE MSR’s ENERGY-MAIL BOX, and those two ENERGY-MAIL BOXES cannot be at the same 3-d point, by definition, so then during the Pit-Stop Time-Slot, 🌊RTSmd also has to “go between” the same two ENERGY-MAIL BOXES, while traveling in the opposite direction on the same 3-d line as the FfSet🧨-equivalent 🛳️ md, and that causes destructive interference ☠️ between the same Wave-Length Logs.
***End of ASIDE regarding mds that originate in 4-d***
End of short COLLISION ETIQUETTE 👍 REVIEW
Now we’re ready to VERIFY that an ATM can NEITHER be a Moving Service Provider NOR a Moving Service Recipient at 180-degrees on the ATM SHELL/Compass.
Imagine an ATM (“ATM A,” let’s say), “just sitting there” along a 3DADL, with the MACOM’s SETFxATMA = 0 at 0-degrees.
So we could say that ATM A is “poised” to provide a Moving Service 🛳️ (and make a Moving Service 🛳️ mdA) from the 0-degree direction on the ATM A SHELL/Compass.
Also imagine another ATM (“ATM B,” let’s say) moving in the 3-d Down direction along a 3DADL. The MACOM of ATM B is all SETFxATMB (the MACOM of ATM B is experiencing SETFxATMB > 0) to provide a Moving Service 🛳️ (and make a Moving Service 🛳️ mdB) from the 180-degree direction on the ATM B SHELL/Compass.
Pretend that our POV is the same as ATM B’s POV, and we’re trying to be a MSP (we’re trying to release 🛳️ mdB) to ATM A—and more specifically, to BTP1 of ATM A—when the two ATMs collide.
Upon “contact” bang-on BTP1 of ATM A, ATM B makes 🛳️ mdB from 180-degrees on the ATM B SHELL/Compass; the MACOM is the only BTP at 180-degrees on the ATM A SHELL/Compass, so we presume that the MACOM makes the 🛳️ mdB.
But the problem is that the MACOM is not directly behind THE BACK DOOR (at 180-degrees) on the ATM B SHELL/Compass (THERE IS A HOLE DIRECTLY BEHIND THE BACK DOOR); the MACOM is, indeed, “home” at 180-degrees on the ATM B SHELL/Compass, BUT the MACOM permanently resides at the center of the ATM B SHELL/Compass, and the Moving Service 🛳️ mdB from the MACOM, which MUST GO OUT THE BACK DOOR (at 180-degrees) on the ATM B SHELL/Compass, DOES NOT HAVE TIME TO REACH BTP1 IN ATM A during the On-Track Time-Slot, so therefore the ATM B SHELL/Compass CANNOT LET 🛳️ mdB PASS out of the ENERGY-MAIL BOX at 180-degrees on the ATM B SHELL/Compass, and therefore there’s NO BOINKING of BTP1’s 423DCTCC in ATM A, and indeed, ATM A is not the MSR at all!
🛳️ mdB: SHELL’s not gonna let us out.
Nope! 👎
ATM B SHELL/Compass: You SHELL not pass.
THE BACK DOOR🚪of the ATM B SHELL/Compass becomes the MSR by default, experiencing a Taxable Receivable in the ENERGY-MAIL BOX at 180-degrees on the ATM B SHELL/Compass, and making the 🌊RTSmdB Tax Payment to the MACOM during the Pit-Stop Time-Slot.
There would be DESTRUCTIVE INTERFERENCE ☠️ between 🛳️ mdB and 🌊 RTSmdB.
It was The Perfect Storm.
And A HOLE at ATM B’s BACK DOOR 🚪made it happen.
👍
But to repeat: the MACOM of ATM A is NOT the MSR; the back door of the ATM B SHELL/Compass is the MSR.
So we see that at the conclusion of the On-Track Time-Slot, SETFxATMA would remain the same—SETFxATMA = 0 at 0-degrees on the ATM A SHELL/Compass—as it was before ATM B rammed into ATM A!
BTP1 IN ATM A REMAINS SECURE.
This is not a FICTION, it’s a REALITY OF POSITION.
Now continue to pretend that our POV is the same as ATM B’s POV, but assume that we’re wondering if we’re going to become a MSR of the Moving Service 🛳️ that ATM A is trying to provide from BTP1’s position at 0-degrees on the ATM A SHELL/Compass—and the 🛳️ mdA that ATM A is trying to make—at ATM B’s BACK DOOR.
Upon “contact,” ATM A makes 🛳️ mdA from BTP1 at 0-degrees on the ATM A SHELL/Compass, BANG-ON THE BACK DOOR (at 180-degrees) of the ATM B SHELL/Compass; the MACOM is the only BTP at 180-degrees on the ATM B SHELL/Compass.
But again, the problem is that the MACOM is not directly behind THE BACK DOOR (at 180-degrees) on the ATM B SHELL/Compass (THERE IS A HOLE DIRECTLY BEHIND THE BACK DOOR); the MACOM is, indeed, “home” at 180-degrees on the ATM B SHELL/Compass, BUT the MACOM permanently resides at the center of the ATM B SHELL/Compass, and the Moving Service 🛳️ mdA from BTP1 in ATM A MUST GO IN THE BACK DOOR (at 180-degrees) on the ATM B SHELL/Compass, which means that 🛳️ mdA DOES NOT HAVE TIME TO REACH THE MACOM IN ATM B during the On-Track Time-Slot, so then the ATM B SHELL/Compass CANNOT LET 🛳️ mdA PASS out of the ENERGY-MAIL BOX at 180-degrees on the ATM B SHELL/Compass, and therefore there’s NO BOINKING of the MACOM’s 423DCTCC in ATM B.
🛳️ mdA: SHELL’s not gonna let us out.
Nope! 👎
ATM B SHELL/Compass: You SHELL not pass.
And again, THE BACK DOOR 🚪 of the ATM B SHELL/Compass becomes the MSR by default, experiencing a Taxable Receivable in the ENERGY-MAIL BOX at 180-degrees on the ATM B SHELL/Compass, and making the 🌊RTSmdA Tax Payment to ATM A (at 0-degrees, the location of BTP1) during the Pit-Stop Time-Slot.
There would be DESTRUCTIVE INTERFERENCE ☠️ between 🛳️ mdA and 🌊RTSmdA.
But to repeat: the MACOM of ATM B is NOT the MSR; the back door of the ATM B SHELL/Compass is the MSR.
So we see that at the conclusion of the On-Track Time-Slot, *both* SETFxATMA *and* SETFxATMB would remain the same as they were before the collision!
BTP1 IN ATM A REMAINS SECURE.
We have shown that an ATM can NEITHER be a Moving Service Provider NOR a Moving Service Recipient at 180-degrees on the ATM SHELL/Compass, because THE BACK DOOR 🚪 of an ATM will always be the only MSR in any collision that occurs at the back door!
In fact, we’ve shown that MOVEMENT-CAUSING COLLISIONS are physically-impossible in either direction along a 3DADL.
🏁 🏁 🏁 🏁 🏁 🏁 🏁 🏁 🏁 🏁
End of THE CLOSED DOOR🚪 DISCUSSION about WHY an ATM can NEITHER be a Moving Service Provider NOR a Moving Service Recipient at 180-degrees on the ATM SHELL/Compass
Begin DISCUSSION (between the 💰 icons) about WHY BTP1 in the ATM Backbone could not become the CAUSE of the MACOM’s movement by being a TFG-receiver
💰 💰 💰 💰 💰 💰 💰 💰 💰 💰
First, consider the situation of BTP1 tipped UU when another ATM comes along and gives BTP1 an Emack TFG smack 😘 on BTP1’s Fmack.
RECALL (see Topic 6, TEST 2), that an Emack TFG that smacks 😘 a TFG-receiver in the Fmack might give the TFG-receiver a WPD Goose 🪿, to the exact extent that the WPD of the TFG-giver and the WPD of the TFG-receiver have common Wave-Length Logs, because of the CONSTRUCTIVE INTERFERENCE that occurs between the TFG and the TFG-receiver’s Emack when the ENERGY-MAIL BOX on the TFG-receiver’s 3-d SheLL COURTESTY-FORWARDS the TFG to the other side of the SheLL along the same line, which just happens to be the TFG-receiver’s WPD line.
In the case of BTP1 being tipped UU, BTP1’s (the TFG-receiver’s) ENERGY-MAIL BOX would be located at 0-degrees on the BTP1 SheLL Compass, and the Emack TFG would be COURTESY-FORWARDED to the ENERGY-MAIL BOX at 180-degrees on the BTP1 SheLL Compass, to the exact spot where BTP1 is emitting Emack. So at that point, BTP1’s own Emack and the COURTESY-FORWARDED Emack TFG would be traveling in the same direction along the same line, causing CONSTRUCTIVE INTERFERENCE between the same Wave-Length Logs, giving BTP1 a WPD Goose 🪿as a result.
BUT DON’T FORGET that when BTP1 is tipped UU, BTP1 is *already* giving the MACOM in the same ATM an Emack TFG smack 😘 on the Fmack, and the MACOM is *already* getting a WPD Goose 🪿as a result; and this situation had *already* cemented BTP1 as A PASSENGER of the MACOM!
Ergo, if BTP1 received an Emack TFG smack 😘 on the Fmack, then that would merely GIVE THE MACOM ANOTHER WPD GOOSE 🪿from BTP1, and as a result, BTP1 would simply CONTINUE TO BE A PASSENGER of the MACOM.
That’s not a problem; BTP1 REMAINS SECURE.
Next, consider the situation of BTP1 tipped UD when another ATM comes along and gives BTP1 an Emack TFG smack 👋 on BTP1’s peachy 🍑 Emack emissary.
Have you ever heard the saying, “I’m going to reach so far up your peach that you’re going to starve because I will be eating your lunch!”?
I don’t think we need to draw a picture of that.
To the extent that BTP1 and the BTPs of the TFG-giver ATM had the same wave-lengths in their WPDs, there would be DESTRUCTIVE INTERFERENCE ☠️ between the TFG and BTP1’s Emack, and that destructive interference would reach all the way up to the source of BTP1’s Emack, which is the point (the AIP) inside of BTP1’s 3-d SheLL where the 3-d WOPR Stream Spectra 🐳 md comes into the universe during the Pit-Stop Time-Slot.
Ergo, the TFG could COMPLETELY DESTROY BTP1’s WPD, leaving it with NO MEAT ON ITS 3-d SheLL BONE.
SO WE NEED TO KNOW IF WE HAVE TO WORRY ABOUT BTP1 TIPPING UU as a result? And we also need to know if we have to worry about the MACOM in the same ATM experiencing UNBALANCED SETFx in the 0-degree direction on the MACOM SheLL Compass as a result of BTP1 possibly tipping UU? And if so, then could the MACOM to tip UU and begin to accelerate?
Answer: NO, NO, NO!!!
We already know that BTP1 cannot be a Moving Service Recipient (see the above discussion between the 🏁 icons), so therefore it’s PHYSICALLY-IMPOSSIBLE for BTP1 to be the source of its own MACOM’s experience of UNBALANCED SETFx.
Also, it is ridiculous to even *suggest* that BTP1’s LOSS OF WPD could cause the MACOM to experience UNBALANCED SETFx; think about it: BTP1 has ZERO FORCE! BTP1 has become a “ghost”!! And there is no BTP below the MACOM to be “turned on” by BTP’s loss of WPD!!!
Think about it some more: If BTP1 could tip UU as a result of LOSING ALL FORCE, then that would DESTROY THE FORCE-DESTRUCTION, and you can’t DESTROY DESTRUCTIVE INTERFERENCE ☠️ (you can’t DESTROY DEATH) by COMING BACK TO LIFE (AUTOMATICALLY GETTING FORCE BACK) unless you have a separate SOURCE OF FORCE, but BTP1 has ZERO FORCE after receiving the Emack TFG smack 👋 on the peachy 🍑 Emack emissary.
SO THE DESTRUCTIVE INTERFERENCE ☠️ SITUATION would *PERSIST*, all other things being equal.
And we have learned what we needed to know, to wit: after BTP1 loses Emack and Fmack, BTP1 become like a “ghost follower” of the MACOM, which is LESS THAN A PASSENGER.
That’s not a problem; BTP1 REMAINS SECURE.
💰 💰 💰 💰 💰 💰 💰 💰 💰 💰
End of DISCUSSION about WHY BTP1 in the ATM Backbone could not become the CAUSE of the MACOM’s movement by being a TFG-receiver
Now all of our worries about BTP1 are over.
Ergo, the ATM 🏧 Backbone is UNBREAKABLE, and the ATM is IMMORTAL, and we are FOREVER COMPELLED to treat the entire ATM as ONE OBJECT BY LAW.
End of Q&A 4!
☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️
Q&A 5
Q: Referring-to the First ATM Diagram, we NOTICE that if all of the BTPs in the ATM are assumed to have the same NORMAL WPD, then Moving Services (“MS”s) provided to the MACOM by the BTPs positioned in opposite directions along the same 3-d direction lines will NORMALLY BALANCE each other (leaving the MACOM to experience ZERO NET FORCE, SETFx = 0 at 0, as a result); how, then, can ATMs provide Moving Services *to each other* if ATMs are NORMALLY NOT MOVING?
We ALSO NOTICE that it is PHYSICALLY-IMPOSSIBLE for a BTP that is not positioned in the “Lowest Circle of MACOM SheLL” (i.e., in a position encircling the 3-d Down direction at the near-bottom of the ATM) to be FORCEFULLY STEERED (via a collision with a Moving Service Provider) AWAY FROM THE MACOM, because all other BTPs are HEMMED-IN ON ALL SIDES BY BTPs THAT HAVE ESTABLISHED STRONG NUCLEAR BOMB BONDS ❤️🩹 WITH THE MACOM; how, then, can ATMs provide a FULL RANGE OF MOVING SERVICES *to each other*, and how can we be reassured that the BTPs in the Lowest Circle of MACOM SheLL are secure?
A: The MACOM’s saying, “that’s OK hey baby [turtle particle] do what you want I’ll be your night-lovin’ thing I’ll be the freak you can taunt I don’t care what you say I wanna go too far I’ll be your everything if you make me a star!” —Dirty Diana
There is a REVVING light-speed engine—a BTP with FfSet and artificial WPD (see Topic 3)—having established A STRONG NUCLEAR BOMB BOND ❤️🩹 WITH THE MACOM at every 3-d sideways direction on the MACOM SheLL Compass, so therefore an ATM can always “get moving” without an EXTERNAL Moving Service Provider’s assistance (WITHOUT FORCEFUL STEERING) because the Universal O/S can always FORCELESSLY STEER one or more BTPs slightly away from the MACOM.
In this manner, ATMs could provide a full range of Moving Services to each other.
More specifically, FORCELESS STEERING of one or more BTPs in any given Circle of MACOM SheLL in either half of the ATM (either the UPPER HALF OF THE ATM, i.e., above the equator line, which we could call the “Middle Circle of MACOM SheLL,” or the LOWER HALF OF THE ATM, i.e., below the Middle Circle of MACOM SheLL) would cause the corresponding BTP(s) in the corresponding Circle of MACOM SheLL in the OTHER HALF OF THE ATM to PROVIDE MOVING SERVICE(S) TO THE MACOM, because THE MAGNITUDE AND DIRECTION OF THE NET FORCE (SETFx) EXPERIENCED BY THE MACOM would go from *ZERO* to *NON-ZERO* whenever BTPs were FORCELESSLY STEERED slightly away from the MACOM.
And in fact, the BTPs in the Lowest Circle of MACOM SheLL can also be FORCEFULLY STEERED all the way PERPENDICULAR to the 3-d Down direction on the MACOM SheLL Compass!
But it is PHYSICALLY-IMPOSSIBLE for any Moving Service that might be PROVIDED to those BTPs in the Lowest Circle of MACOM SheLL to cause those BTPs to TIP UD.
This is a fortuitous situation, because TIPPING UD is the only way that the BTPs in the Lowest Circle of MACOM SheLL could GET AWAY from the MACOM *or* collide with each other (to collide with each other, they would have to “go around the bottom” of the MACOM, but IT’S PHYSICALLY-IMPOSSIBLE TO GO AROUND THE BOTTOM OF THE MACOM WHILE REMAINING UU.)
So we are reassured that FORCEFUL STEERING of the BTPs in the Lowest Circle of MACOM SheLL won’t cause those BTPs to SEPARATE FROM THE MACOM.
Mini-Q: When, *exactly* (in which Time-Slot), would FORCELESS STEERING occur, and when, *exactly* (in which Time-Slot) would the MACOM experience SETFx > 0?
Mini-A: Let’s consider both possibilities—(1) Forceless Steering occurs during an On-Track Time Slot, and (2) Forceless Steering occurs during a Pit-Stop Time-Slot—and decide which one is correct.
(1) If FORCELESS STEERING occurs during an On-Track Time-Slot, then the corresponding BTP(s) in the Highest Circle of MACOM SheLL would PROVIDE MOVING SERVICE(S) 🛳️—and begin to make 🛳️ md(s)—TO THE MACOM in that same On-Track Time-Slot, so then the MACOM would experience SETFx > 0 at the beginning of the Pit-Stop Time-Slot, when the THRUST of making the Moving Service Tax Payment(s) 🌊RTSmd was first experienced, and the ATM would MOVE in accordance with SETFx during the next On-Track Time-Slot.
(2) If FORCELESS STEERING occurs at the beginning of a Pit-Stop Time-Slot, then the corresponding BTP(s) in the Highest Circle of MACOM SheLL would have to wait for the next On-Track Time-Slot to PROVIDE MOVING SERVICE(S)—and begin to make the md(s) 🛳️—TO THE MACOM, so then in that case, the MACOM would experience SETFx >0 at the beginning of the next Pit-Stop Time-Slot, as the THRUST of making the tax payment(s) RTSmd 🌊 was experienced, and the ATM would MOVE in accordance with SETFx during the next On-Track Time-Slot after that.
Ergo, we can assume that FORCELESS STEERING must occur during an On-Track Time-Slot, which is also when FORCEFUL STEERING (COLLISIONS) occur.
End of Q&A 5!
☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️
Q&A 6
Q: Referring-to the “ATM Accelerating Down a 3DADL Diagram,” what, *exactly*, would happen to the ATM if the Universal O/S FORCELESSLY STEERED two BTPs in the Lowest Circle of MACOM SheLL directly across from each other—i.e., on opposite sides of the MACOM—so that their 423DCTCCs tilted away from the MACOM?
NOTE that as shown, the two FORCELESSLY STEERED BTPs are positioned at 120-degrees and at 240-degrees in the Lowest Circle of MACOM SheLL; ALSO NOTE that all of the Circles of MACOM SheLL in between the Lowest Circle of MACOM SheLL and the Highest Circle of MACOM SheLL have been omitted from the diagram.
A: When the two BTPs in the Lowest Circle of MACOM SheLL suddenly “disappeared,” the MACOM would experience TWO UNBALANCED MOVING SERVICES provided by the two corresponding MSP BTPs in the Highest Circle of MACOM SheLL.
We have to do a MOTION ANALYSIS (between the 🐢 icons, below; for the MOTION ANALYSIS How-To, see Topic 4) to figure-out the MACOM’s NEW SETFx (MAGNITUDE SETFx and DIRECTION SETFx.)
🐢 🐢 🐢 🐢 🐢 🐢 🐢 🐢 🐢 🐢
Regarding MAGNITUDE SETFx, we notice that both MSP BTPs in the Highest Circle of MACOM SheLL are UD, so we assign a negative value to the MSs they are providing.
MAGNITUDE SETFx = - (Fmack + FfSet) - (Fmack + FfSet) = -2(Fmack + Ffset)
Regarding DIRECTION SETFx, we have two MSs being applied to the MACOM along *different lines*, so we have to find the midpoint of the two directions in which the MSP BTPs in the Highest Circle of MACOM SheLL are trying to get the MACOM to move on the MACOM SheLL Compass.
In the diagram, the MSP BTPs in the Highest Circle of MACOM SheLL are labeled from their own POV; one MSP BTP is providing a MS to the MACOM at 120-degrees on that MSP BTP’s SheLL Compass, and the MS is trying to get the MACOM to move at 120-degrees on the MACOM SheLL Compass; the other MSP BTP is providing a MS to the MACOM at 240-degrees on that MSP BTP’s SheLL Compass, and the MS is trying to get the MACOM to move at 240-degrees on the MACOM SheLL Compass.
Finding the midpoint, DIRECTION SETFx = (120 + 240)/2 = 180
SETFx = 2(Fmack+FfSet) @ 180
This means that the MACOM will TIP UD and begin hauling mass IN THE 3-d DOWN DIRECTION along the 3DADL, according to Newton’s Second Law of Motion,
MAGNITUDE SETFx = ma,
where a = v²,
and where v² = present-instant velocity = (the base rate of acceleration, OR if no acceleration, then 1) MULTIPLIED BY (prior-instant velocity in the same direction)
In the first instant, the ATM’s velocity, “v1” (which is the base rate of acceleration), is calculated according to Newton’s First Law of Motion,
MAGNITUDE SETFx = mv
Solving for v,
v1 = MAGNITUDE SETFx/m
We know: MAGNITUDE SETFx = FfSet = c (because in Reality, it’s impossible to use 2(Fmack+FfSet) Wave-Length Logs in one instant; FfSet = c is the maximum wave-length force in Reality, and in that case, all of the Wave-Length Logs in the EM Spectrum are being used in one instant),
and m = 128,880 = Hydrogen Relative Mass (128,882) MINUS the mass of the two WINNING MSP BTPs in the Highest Circle of MACOM SheLL, which are *causing* the MACOM to experience UNBALANCED NET FORCE (SETFx > 0), and therefore they are “carrying their own weight.”
Substituting, we find v1 = MAGNITUDE SETFx/m = 299,792,548/128,880 = 2,326 m/s
In other words, in the first On-Track Time-Slot (“instant 1”) after the On-Track Time-Slot in which the FORCELESS STEERING occurred, v1 = 2,326 m/s
In instant 2, v2 = (the base rate of acceleration) MULTIPLIED BY (prior-instant velocity in the same direction) = (v1) x (v1) = 2,326 m/s x 2,326 m/s = 5,410,276 m/s
In instant 3, v3 = (v1) x (v2) = GREATER THAN THE SPEED OF LIGHT, which is PHYSICALLY-IMPOSSIBLE, ergo, v2 is the TERMINAL VELOCITY in this case.
🐢🐢 🐢 🐢 🐢 🐢 🐢 🐢 🐢 🐢
In summary of the answer, according to our assumptions, in instant 1 (which means during the first On-Track Time-Slot after the On-Track Time-Slot in which the FORCELESS STEERING occurred), the Hydrogen ATM would move in the 3-d Down direction along the 3DADL (i.e., in the 180-degree direction on the ATM SHELL/Compass) at v1 = 2,326 m/s, and in instant 2, the ATM would accelerate and reach TERMINAL VELOCITY, which would be v2 = 5,410,276 m/s.
End of Q&A 6!
☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️
Q&A 7 through Q&A 12 are in Part B.
In joy,
Frank