Article 9, No Big Whoop Part III. THE THEORY OF EVERYTHING IS...

☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️

⚠️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.

Topic List

Topic 7. Beep beep! What the F?

Topic 8. 🎵 To every thing there is a season, and a time to every purpose under the heavens 🎵; there is an On-Track Time-Slot for moving, and a Pit-Stop Time-Slot to refrain from moving and pay taxes for moving

Topic 9. Mr. Carp says, “When you feed a fish [or glow-up a BTP with fresh WPD], never feed him a lot, so much and no more!”

Topic 10. Giiiirrrrl, did you forget about glowing-up the LLs?

Topic 11. 🎵No parking on the dance floor! Moving violations are easy to fix, just tell the DJ to fix it in the mix….It’s so easy it’s so right to rock it with your body baby turtle particles 🎵BREAKDOWN of the ATM BACKBONE TWO-STEP DANCE TO MOVE LIKE TETRIS DIAGRAM, ft. the ATM STEERING RIGHT TRIANGLE (“RT”)

☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️

Topic 7. Beep beep! What the F?

We NOTICE that one collision takes TWO DURATIONS OF TIME to get every body MOVING (or resting) as a result; initially, every body must EXPERIENCE the collision, which requires COMPARING “wut just happened” with “what was happening before”; then next, every body must BE RECONCILED to “wut just happened,” so then the QUESTION becomes:

HOW IS POSSIBLE FOR MOTION TO BE CONSTANT (i.e., occur in every INSTANT of Absolute Time) if ONE COLLISION takes TWO DURATIONS OF ABSOLUTE TIME to complete?

“No problem!” we might think, “that’s the entire point of TIME INSTANTS!”

And that’s basically what I’ve assumed until NOW, because we really didn’t have any OBJECTS to speak-of until NOW—before NOW, we were just watching things “fall apart” in a Rube Goldberg (and Reverse Rube Goldberg) fashion when they weren’t “standing still”—but NOW we’ve got an ATM Backbone, which we need to get into motion.

That’s not exactly an EXCUSE for my not knowing how TIME INSTANTS work, *exactly*, to ENABLE MOTION, but it’s an explanation for why I *tried* to take a “generalized” approach to motion analysis.

But now that it’s necessary to get the ATM Backbone into motion, it’s clear that all my hope of avoiding the issue of HOW TIME WORKS, *exactly*, is lost.

QUESTION: How do TIME INSTANTS work, *exactly*, to ENABLE MOTION?

ANSWER: Time instants work *exactly* like STOP-MOTION ANIMATION.

Begin further explanation *between the ⁉️ icons*

⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️

Think about the issue some more.

Are we prepared to say that every body STOPS WHAT THEY WERE DOING BEFORE—you know, what they were doing with their ENERGY—to BECOME RECONCILED TO CHANGES WITHOUT DELAY?

If so, then what happens to their WORK-IN-PROGRESS?

That WORK-IN-PROGRESS—including THE EXPERIENCES OF “WORKPLACE CHANGES”—was ENABLED by their OLD MASS (the WPD they were given, which they thrust-out as Emack), so therefore the ENABLED work must be COMPLETED (or completion must be attempted) *before* there can be any REACTION to EXPERIENCES OF “WORKPLACE CHANGES” that the work itself CAUSED to happen.

Also, WHAT THE F?

Are we prepared to say that every body is *experiencing* F *partially* at the same time as they are *following* F = ma?

How can any body *follow* F = ma BEFORE KNOWING F?

In other words, HOW DOES EVERY BODY KNOW WHAT TO DO WITHOUT DELAY?

Are we prepared to say that every body plays “NAME THAT TUNE” on the first note—beep!— and then GOES AND FOLLOWS F = ma (Newton’s Second Law of Motion) WHILE PAYING TAX ON MOVING SERVICES (satisfying Newton’s Third Law of Motion) AT THE SAME TIME?

That can’t be right.

And yet if every body has to WAIT to MOVE until the TAX-MAN gets his due, then are we prepared to say that every body has to WAIT to have COLLISIONS, too?

That can’t be right, either!

We would negate AUTONOMOUS (CONSCIOUS) ACTS altogether if we limited when COLLISIONS could occur, because LOCATION/DESTINATION would have to be PRE-DETERMINED to have COLLISIONS with perfect timing.

But if COLLISIONS can occur ANY TIME that movement or attempted movement is happening, *and* if F = ma movement must wait until F is known (until Newton’s Third Law of Motion is satisfied by FULLY PAYING TAX ON MOVING SERVICES in REACTION to being more or less BRUTALLY HEAD-BUTTED), then are we prepared to say that there is NO MOVING SERVICES TAX PAYMENT WINDOW that every body must recognize?

ARE WE PREPARED TO PUT THE ATOMIC COM (the ACOM) OF AN ATM, i.e., the Moving Service Recipient at the center-of-mass of every ATM, on a DIFFERENT MOVING SCHEDULE than the Atomic Mass Moving Service Providers (MSPs) IN THE SAME ATM??

Seriously: are we prepared to DELAY THE CART (the ATM Backbone, and in particular, the ACOM) but *at the same time* WHIP THE HORSE (a BTP MSP, assuming that it’s not also a Moving Service Recipient) to MAKE THE MSP GO AHEAD AND MOVE THE CART *before* the cart is finished PAYING TAXES (reacting to the Moving Service—the COLLISION—to satisfy Newton’s Third Law of Motion), which (the tax-paying) THE CART is doing for the purpose of getting THRUST (finding the total F) to ENABLE the cart to satisfy Newton’s Second Law of Motion, F = ma, as the Moving Service Provider FORCED IT TO DO???

THE CART AND THE HORSE PROBLEM WITH NEWTON’S SECOND AND THIRD LAWS OF MOTION to which I am referring is apparent in COLLISION DIAGRAM 3A’:

Moving the ATM Backbone (THE CART) is what we’ve got to accomplish!

And we can NEVER tell a MSP, aka THE HORSE, to move a Moving Service Recipient (MSR), aka THE CART, *until* THE CART IS DONE PAYING TAXES—i.e., until the ACOM has finished thrusting-out 🌊RTSmd in satisfaction of Newton’s Third Law of Motion, and therefore knows the total 🛳️ md, which is the Moving Service force, F—and IS FREE TO FOLLOW Newton’s Second Law of Motion, F = ma.

This means that even if the MSP BTP (THE HORSE) has no Moving Services taxes to pay, THE HORSE MUST WAIT FOR THE MSR (THE CART) TO FINISH PAYING MOVING SERVICE TAXES before moving or attempting to move again itself.

But th-th-that’s NOT ALL, folks!

At each instant, every BTP in the universe—THE CART and THE HORSE alike—must make a TAX PAYMENT (see Topic 3) on the TAXABLE RECEIVABLE of being GLOWED-UP with a new internal force of mass, which is the 3-d WOPR Stream Spectra 🐳 md at the AIP inside of the 3-d SheLL (i.e., the UPLOADED 4-d Spectra Assembly 🪵 that was skimmed from the 4-d Space River Spectrum 🔥) in the DIRECTION in which the 423DCTCC is being STEERED (i.e., the direction of the NET FORCE that the BTP is experiencing.)

Let’s call the tax payment on the 3-d WOPR Stream Spectra 🐳 the “WPD Tax Payment” 🔫 (which becomes Emack, then Emack causes Fmack, with Emack and Fmack together comprising WPD.)

Ergo, every body in the universe must enter a “Tax Payment Window” at the SAME TIME—and NEVER MOVE OR ATTEMPT TO MOVE at the Tax Payment Window!—whether or not they are paying Moving Services taxes at that TIME, because the Tax Payment Window is for BOTH:

(i) WPD Tax Payments 🔫 (which become Emack, then Emack causes Fmack, with Emack and Fmack together comprising WPD);

and

(ii) Moving Services Tax Payments, 🌊RTSmd (which experience destructive interference ☠️ with Moving Services🛳️ mds.)

QUESTION: Are we also prepared to say the “Motion Window” is only open EVERY OTHER INSTANT, and in alternate instants, the Tax Payment Window is open?

ANSWER: No, That can’t be right. Every thing must move or attempt to move in EVERY INSTANT. Some THING cannot DO NOTHING *SOME TIMES*; every thing must DO SOMETHING *ALL OF THE TIMES*, or else we’re creating or destroying energy with NOTHING, and that violates the Law of Conservation of Energy, and puts us back at THE BEGINNING, without a valid Big Bang Theory.

And WE KNOW that INSTANTS must tik-tok on the Universal Clock at the speed of light to enable light to finish its WORK-IN-PROGRESS in one instant of TIME.

NOW WHAT, *exactly*, are we prepared to say about how TIME INSTANTS work to ENABLE MOTION?

Don’t even bother to check the rear-view mirror to look for Isaac Newton.

⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️ ⁉️

End of further explanation *between the ⁉️ icons*

End of Topic 7!

☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️

Topic 8. 🎵 To every thing there is a season, and a time to every purpose under the heavens🎵; there is an On-Track Time-Slot for moving and a Pit-Stop Time-Slot to refrain from moving and pay taxes for moving

It’s fortunate that TIME INSTANTS must tik-tok at the speed of light, because there’s no Law against ONE TIME INSTANT having TWO TIME-SLOTS.

We could also refer-to ONE TWO-SLOT INSTANT ON THE UNIVERSAL CLOCK as a “Murmuration Moment,” or “MuM,” in honor of Starling Murmurations, in which hundreds—and thousands—of CONSCIOUS beings (each having a pack-animal CAPP; see Article 8) are flying synchronously wing-to-wing without a single collision.

And in fact, in Topic 7, we showed that there’s a LEGAL NECESSITY for THE LAWS OF MOTION to AUTOMATICALLY DIVIDE EACH TIME INSTANT into TWO TIME-SLOTS:

(1) a “Pit-Stop Time-Slot,” during which TAX PAYMENTS are made:

(i) WPD Tax Payments 🔫 (which become Emack, then Emack causes Fmack, with Emack and Fmack together comprising WPD) on the Taxable Receivable 🐳 mass deposit of the internal force of mass—the 3-d WOPR Stream Spectra 🐳 md—UPLOADED to the AIP inside of a 3-d SheLL to GLOW-UP a BTP in every Pit-Stop Time-Slot (as discussed in Topic 3);

and

(ii) Moving Services Tax Payments, 🌊RTSmd (which experience destructive interference ☠️ with Moving Services🛳️ mds) on the Taxable Receivable 🛳️ mass deposits from Moving Services, whenever a Moving Service Provider (MSP) makes a 🛳️ md into a Moving Service Recipient’s (MSR’s) SHELL;

and

(2) an “On-Track Time-Slot,” during which the THRUST (🔫 Emack and 🌊 RTSmd) that was GENERATED BY MAKING THE TAX PAYMENTS IN-FULL during the Pit-Stop Time-Slot causes THE APPLICATION OF PHYSICAL FORCE and attendant MOVEMENT OR ATTEMPTED MOVEMENT IN THE DIRECTION OF THE PHYSICAL FORCE, sometimes resulting-in COLLISIONS.

IN BOTH TIME-SLOTS, LIGHT DOES ITS *CONSTANT* WORK OF MOVING AT THE SPEED OF LIGHT.

For example, during BOTH the Pit-Stop Time-Slot AND the On-Track Time-Slot, Emack TFG smacks 😘 on the Fmack (see Topic 6)—which can cause Emack constructive interference and give the TFG-receiver an Emack Goose 🪿during the On-Track Time-Slot—are COURTESY-FORWARDED by ENERGY-MAIL BOXES; and also, Emack TFG smacks 👋 on the peachy 🍑 Emack emissary—which can cause Emack destructive interference ☠️ and WPD loss during the On-Track Time-Slot—may be present.

Now we need to explain how the Tax Payment Window would operate in conjunction with the TWO TIME-SLOTS of each INSTANT, aka MuM.

RECALL from Article 7:

And that’s how the Tax Payment Window would operate!

A Taxable Receivable NEEDS SOMEWHERE TO GO *IN* A 3-d SHELL so that the 3-d SHELL CAN THRUST IT *OUT*!

And that’s why ENERGY-MAIL BOXES are necessary.

The NEW INFORMATION here is that the Tax Payment Window remains CLOSED for access by the 3-d SHELL until the beginning of the Pit-Stop Time-Slot.

This doesn’t mean, however, that a 3-d SHELL is “holding onto mass”; no, there’s no “holding mass,” but rather, THE 3-d SHELL IS WAITING FOR LIGHT TO FINISH ACTING-ON THE 3-d SHELL—including being THRUST OUT by the 3-d SheLL—and that’s not only OK, it’s NECESSARY to enable motion.

Unlike internal 🐳 mass deposits, which can be TRANSFERRED from location-to-location of the QOL WITHOUT DELAY (by INSTRUCTION of the DJ, either Jesus or the Universal O/S, which is ADMINed by Jesus), Moving Services 🛳️ mass deposits TAKE TIME to ENTER SHELLs.

But again, that’s OK, because a taxpayer (a 3-d SHELL) cannot USE any Taxable Receivable (🐳 md or 🛳️ md) *BEFORE* A TAX PAYMENT (🔫 Emack or 🌊RTSmd) IS MADE IN-FULL, and that always takes *exactly* the duration of the Pit-Stop Time-Slot to do, because A SHELL CAN’T “BOSS LIGHT AROUND,” but rather, A SHELL HAS TO *DO ITS OWN WORK* OF KEEPING ITSELF EMPTY, i.e., THRUSTING-OUT TAXABLE RECEIVABLES that FORCED THEIR WAY IN.

Check it out: it’s impossible to make a Tax Payment (🔫 or 🌊) FASTER than the duration of the Pit-Stop Time-Slot, but it’s always possible to make Tax Payments in-full during the Pit-Stop Time-Stop; so therefore regardless of when a particular Taxable Receivable (🐳 md or 🛳️ md) BEGINS LOADING into in ENERGY-MAIL BOX—

in other words, whether a Taxable Receivable BEGINS LOADING in the On-Track Time-Slot (which is the case with a Moving Service 🛳️ md) OR a Taxable Receivable BEGINS LOADING in the Pit-Stop Time-Slot (which is the case with a 🐳 md)—

the MSR will always FINISH making the Tax Payment *just in time* for the On-Track Time-Slot.

Then, having MADE ALL REQUIRED TAX PAYMENTS, the taxpayer (3-d SHELL) would be ENABLED TO MOVE or attempt to move at the beginning of the On-Track Time-Slot with the FULL FORCE OF THE GENERATED THRUST (🔫 Emack and 🌊RTSmd.)

How awesome is that?!?!

End of Topic 8!

☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️

Topic 9. Mr. Carp says, “When you feed a fish [or glow-up a BTP with fresh WPD], never feed him a lot, so much and no more!”

The “hack” that LIGHT uses—the “trick” that LIGHT has up its proverbial sleeve—is to NEVER GIVE A BTP MORE WAVE-LENGTH FORCE IN THE WPD (the wave-length force in a BTP’s WPD is the sum of the force-value of each individual wave-length in the 3-d WOPR Stream Spectra 🐳 md) than the BTP can use in the On-Track Time-Slot.

In this manner, every BTP in the universe “runs out of gas” at the end of the On-Track Time-Slot of every INSTANT!

Then all of the BTPs in the universe get “re-fueled”—GLOWED-UP with new WPD—in the Pit-Stop Time-Slot of the SAME INSTANT, so that the BTPs are all SET to MOVE or attempt to move again *just-in-time* for the Universal Clock to tik-tok and usher-in the NEXT INSTANT, which begins ”On-Track.”

Different BTPs could get different WPDs, but the wave-length force in every WPD would be limited by wave-length LENGTH!

In other words, wave-length LENGTH is A CONSTANT, and WE ALREADY KNEW THAT, but WHAT WE DID NOT KNOW BEFORE is that each wave-length “fits” neatly into one Time-Slot, like a log of firewood (so let’s begin to call wave-lengths “Wave-Length Logs”), with each Wave-Length Log traveling at the same constant speed, c, and (as discussed in Topic 1) with different Wave-Length Logs having different force-values, like different denominations of a cash currency.

https://www.youtube.com/watch?v=soqqXXscQlQ

That additional detail about wave-lengths being LENGTH-LIMITED Wave-Length Logs that are always consumed by matter in exactly one Time-Slot might not sound like any big whoop.

But it’s a very big whoop, because it means that we cannot envision each Wave-Length Log as being like a “long log” with length “L,” traveling at the speed of light for an entire instant, and covering a certain distance “D.”

No!

Now WE’VE DISCOVERED LIGHT’S HACK, to wit: each Wave-Length Log is like a precisely-cut “short log” with length “l,” traveling at the speed of light for HALF OF AN INSTANT, and covering a certain distance “d,” with d + d = D.

RECALL that distance = speed x time

So WE’RE NOT “CHEATING” OR RE-WRITING THE LAWS OF PHYSICS!

And we’re not even saying anything NEW about SPEED!

BTP SPEED (the rate at which a BTP moves or attempts to move) is—EXACTLY AS WE ALWAYS ASSUMED—established by how many wave-lengths (now called Wave-Length Logs) are SUPERIMPOSED to give the BTP its PHYSICAL FORCE.

We know that regardless of how many Wave-Length Logs are SUPERIMPOSED in one location, it’s physically-impossible to USE more Wave-Length Logs in one Time-Slot than *all the Wave-Length Logs* in REALITY, i.e., in the EM Spectrum, which has a total wave-length force of c.

All we’re doing now DISCOVERING TWO NEW DETAILS, one about TIME, and one about DISTANCE, to wit:

(i) there are TWO TIME-SLOTS IN EACH INSTANT;

and

(ii) THE DISTANCE, D, that light travels in ONE INSTANT is BROKEN INTO TWO EQUAL SMALLER DISTANCES, d, and light’s “hack” is to USE TWO DIFFERENT (but identical!) Wave-Length Logs to travel the two smaller distances, d.

It’s like THE BATON is being HANDED-OFF in the middle of the RACE!

“It’s called a changeover. The movie goes on, and nobody in the audience has any idea.” —Tyler Durden

We wouldn’t have any way of KNOWING this until we reached the point in our motion analysis where we figured-out that EVERY BODY MUST STOP MOVING AT THE TAX PAYMENT WINDOW or else the horse will be beating a dead cart!

And again: the only new concept we’re talking about is that A BTP IS NOT REALLY MOVING OR ATTEMPTING TO MOVE FOR AN ENTIRE INSTANT, BECAUSE THE “BURN RATE” OF EVERY WAVE-LENGTH LOG IS EXACTLY ONE TIME-SLOT, so therefore BTPs will all “run out of fuel” at the end of the On-Track Time-Slot and AUTOMATICALLY STOP MOVING OR ATTEMPTING TO MOVE—they must literally become EMPTY HUSKS OF DEATH—until they are finished getting GLOWED-UP with NEW WPD in the Pit-Stop Time-Slot.

To repeat: all of the matter in the universe literally has to be RE-CREATED *FROM SCRATCH* during the Pit-Stop Time-Slot of every instant.

NOTE that our discovery that each instant comprises TWO TIME-SLOTS necessitates a clarification of the distinction between NEW MASS (a NEW 3-d WOPR Stream Spectra 🐳 mass deposit) and OLD MASS.

There are actually TWO WAYS in which a NEW WOPR Stream Spectra 🐳 mass deposit (md) becomes an OLD WOPR Stream Spectra 🐳 md (and it is the SECOND WAY that is relevant to the RE-CREATION of matter from scratch during the Pit-Stop Time-Slot):

(1) from one Pit-Stop Time-Slot in one instant to the next Pit-Stop Time-Slot in the next instant, there is an entirely NEW SET OF WAVE-LENGTH LOGS—a new WOPR Stream Spectra 🐳 md—UPLOADED at the AIL inside of a 3-d SheLL, and the new set of Wave-Length Logs might have a DIFFERENT MAGNITUDE (a different wave-length force) OR DIRECTION as compared to the magnitude or direction of the OLD, THRUST-OUT WOPR Stream Spectra 🐳 that was causing movement or attempted movement during the On-Track Time-Slot of the prior instant;

and

(2) during the WPD RE-CREATION PROCESS, a NEW MASS (a new 3-d WOPR Stream Spectra 🐳 md) becomes OLD MASS as it is THRUST OUT as a WPD Tax Payment 🔫 over the course of the Pit-Stop Time-Slot, with the TOTAL THRUST OF THE OLD MASS causing movement or attempted movement in the On-Track Time-Slot of the same instant.

It can’t hurt to review what we have deduced so far about the WPD RE-CREATION process, which happens during the Pit-Stop Time-Slot, so let’s also do that again now.

The 4-d Spectra Assembly 🪵 (see Topic 3) is skimmed (by the 6DCT at the bottom of the Lumeyne within a Snowman of God ☃️) from the 4-d Space River Spectrum of Eternally-Burning Radioactive Waste 🔥, then the 4-d Spectra Assembly is UP-CYCLED (UPLOADED, in fact) and deposited at a 3-d location (called the AIP) inside of a 3-d SheLL in the same direction on the SheLL Compass in which the PP6DCT part of the 423DCTCC is being STEERED, where the mass deposit (now called the 3-d WOPR Stream Spectra 🐳 md) is experienced by the 3-d SheLL as a Taxable Receivable (the internal force of mass), which the 3-d SheLL must reverse 🐳 and THRUST OUT along the same line but on the opposite side of the 3-d SheLL to make the WPD Tax Payment 🔫 (that becomes Emack) to satisfy Newton’s Third Law of Motion, then Emack causes the 3-d SheLL to apply an equivalent physical force (called Fmack) at the AIP, with Emack and Fmack together comprising artificial WPD that the 3-d SheLL can GO! and work with during the On-Track Time-Slot.

Artificial WPD TRANSFORMS the EMPTY 3-d SheLL into a CUSTOM-MADE BTP!

In this manner, MOVEMENTS OR ATTEMPTED MOVEMENTS in the On-Track Time-Slot would neither have to be PRE-DETERMINED nor “CUT OFF,” but rather, they would be PRE-ENABLED, then it would be que sera sera during the On-Track Time-Slot.

End of Topic 9!

☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️

Topic 10. Giiiirrrrl, did you forget about glowing-up the LLs?

The concern is that we haven’t fully reconciled the dual discovery of Time-Slots and short Wave-Length Logs with the prior conclusion that lone EMPTY 3-d SheLLs on the loose in the universe under power of FfSet 🧨 never stop moving at the speed of light, and—when they collide in a certain order that respects the Hierarchy of Relativity of 3-d Directions—can form STRONG NUCLEAR BOMB BONDS ❤️‍🩹 with each other that last forever, so therefore NOW the question becomes:

CAN WE RECONCILE THE DUAL DISCOVERY of Time-Slots and short Wave-Length Logs with FfSet 🧨, and show that it’s perfectly fine if FfSet WAXES AND WANES like sand in the hour-glass of Time-Slots? In other words, can we show that full-mass Eternal turtle-particles also have to refrain from moving at the Tax Payment Window during the Pit-Stop Time-Slot so that they can make WPD Tax Payments 🔫 as they get GLOWED-UP with the new internal force of mass, and—in the case of Lumeynes—also make Moving Services Tax Payments, 🌊RTSmd, on the Taxable Receivable 🛳️ mass deposits from Moving Services received during the On-Track Time-Slot (as discussed in Topic 3, Lumeynes Eternally generate OPP wave-energy tax payments Ef(OPPFt) and Ef(OPPFg) in reaction to being acted-upon by the Moving Services Ft and Fg provided by the Timeyne and the Gravityne, respectively, in the same Snowman of God)?

ANSWER: Yes. There is ALWAYS A GLOW-UP that every particle—Eternal full-sized turtle particle and artificial baby turtle particle alike—has to get during the Pit-Stop Time-Slot; so we do not have to worry that there isn’t REALLY an “FfSet RE-SET” that has to occur to give every LL a fresh FfSet 🧨 during the Pit-Stop Time-Slot.

I could be wrong now, but I don’t think so.

Still, it may not be *exactly* clear how the two-Time-Slot INSTANT theory matches-up with the “SybiLL SAP Theory From (A) to (U) True Story” in Article 7 that supposedly completed the UNPACKING of “The #1 Physics Issue in Reality: The Non-Existent Beginning of Mass, The Wave-Particle Duality Theory of Perpetual Motion.”

Begin mash-up EXPLANATION

We can apply the two-Time-Slot theory to the ETERNAL WPD Theory from Article 7, focusing-on LLs specifically.

Directly below, RECALL from Article 7 the relevant plot-points of the ETERNAL WPD Theory….

….but as you are reading the information in the photos, IMAGINE THAT THE PLOT-POINTS ARE HAPPENING DURING THE PIT-STOP TIME-SLOT OF ONE INSTANT,

and ALSO IMAGINE that the plot-points are happening to an LL,

and FURTHER IMAGINE that the NET FORCE OF MASS that is being *EXPERIENCED* by the LL isn’t INTERNAL, but rather, THE NET FORCE OF MASS that the LL *EXPERIENCES* is a Taxable Receivable 🛳️ mass deposit equivalent to FfSet (the “FfSet🧨-equivalent 🛳️ md”, let’s call it) from the Moving Service, Ft, provided by the Timeyene during the On-Track Time-Slot,

and RECALL that the FfSet 🧨-equivalent 🛳️ md that the LL is *experiencing* comprises ALL THE WAVE-LENGTH LOGS IN THE EM SPECTRUM,

and NOTICE that ALL THE WAVE-LENGTH LOGS are SUPERIMPOSED—

so therefore the FfSet🧨-equivalent 🛳️ md may seem wider than a Redwood, who knows,

because IT’S THE LARGEST MASS DEPOSIT OF ALL,

yet it will still be the length of one Wave-Length Log,

and the whole mass will always fit into the wood-chipper,

er, I mean one LL—

And as *EVERY LITTLE BIT* of that ginormous FfSet🧨-equivalent 🛳️ md is *EXPERIENCED* by the LL as a Taxable Receivable, it is reversed and THRUST OUT during the Pit-Stop Time-Slot as the LL makes a Moving Services Tax Payment (🌊RTSmd) in the Snowman of God.

So again picture an LL shooting-out *little bits* of *every Wave-Length Log* all throughout the Pit-Stop Time-Slot, as a wood-chipper does.

Destructive interference ☠️ between the FfSet🧨-equivalent md 🛳️ and the RTSmd 🌊 Moving Services Tax Payment will send the “destroyed” wave-lengths to the 4-d Space River of Eternally-Burning Radioactive Waste 🔥 in the Absolute Forward direction along the LL’s ADL,

and when 🌊RTSmd is complete, the LL WILL HAVE THE TOTAL THRUST OF 🌊RTSmd “behind it,”

which will cause the LL to try to *apply* the physical force of FfSet 🧨 in the opposite direction as the THRUST,

BUT WE ALREADY KNOW THAT THE LL IS PARALYZED IF IT HAS A PP/3-d SheLL,

and WE ALSO KNOW NOW THAT THE BTP WITH THE PP/3-d SheLL CANNOT MOVE when it’s in the Tax Payment Window, otherwise A HORSE COULD BEAT A DEAD CART (see Topic 7),

ergo, WE DON’T HAVE TO WORRY ANYMORE ABOUT THE *APPLIED* PHYSICAL FORCE of FfSet CAUSING BTP MOVEMENT UNTIL AFTER THE TAX PAYMENT WINDOW IS CLOSED.

“Who shut up the sea behind doors when it burst forth from the womb, when I made the clouds its garment and wrapped it in thick darkness, when I fixed limits for it and set its doors and bars in place, when I said, ‘This far you may come and no farther; here is where your proud waves halt’?”—Job 38:8-11

To repeat: a tax-paying LL can’t APPLY FfSet 🧨 via a BTP’s 3-d SheLL until the LL has converted the entire FfSet 🧨-equivalent 🛳️ md into THRUST by making the Moving Services Tax Payment 🌊RTSmd during the Pit-Stop Time-Slot, and only then is the BTP FREE TO GO! at the speed of light with BIG BANG FORCE in the On-Track Time-Slot.

End of mash-up EXPLANATION

End of Topic 10!

☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️

Topic 11. 🎵No parking on the dance floor! Moving violations are easy to fix, just tell the DJ to fix it in the mix….It’s so easy it’s so right to rock it with your body baby turtle particles 🎵BREAKDOWN of the ATM BACKBONE TWO-STEP DANCE TO MOVE LIKE TETRIS DIAGRAM, ft. the ATM STEERING RT

QUESTION: How is the DJ going to get the ATM Backbone up off the wall if the ACOM, which is in the 3-d Backbone Orienation, can only move in the non-sideways 3-d directions (North and South), but it can only receive Moving Services from BTPs in the 3-d sideways directions?

ANSWER: Take me by the PP6DC Tongue and I’ll show you the Two-Step Dance Moves Like Tetris

Begin BREAKDOWN of the ATM BACKBONE TWO-STEP DANCE TO MOVE LIKE TETRIS DIAGRAM, ft. the ATM STEERING RT

Again RECALL: distance = velocity x time

In this case, velocity = speed at DIRECTION SETFx

And we know DIRECTION SETFx = angle Θ in the ATM STEERING RT

(Θ = 45-degrees on the ACOM SheLL Compass in COLLISION DIAGRAM 3A’.)

So we NOTICE that if time = 1 Time-Slot, then

distance between Point A and Point C = velocity = speed at DIRECTION SETFx

And we know that the ACOM’s BASE RATE OF ACCELERATION (i.e., the ACOM’s FIRST-INSTANT VELOCITY, which is the ACOM’s SPEED in DIRECTION SETFx before acceleration has occurred) is calculated according to Newton’s First Law of Motion:

SETFX = mv, where m = 2

Solving, velocity = SETFx/2

So we verify that THE MAGNITUDE AND DIRECTION OF THE NET FORCE—that’s SETFx—experienced by the ACOM functions like an ATM COMPASS NEEDLE, with the ACOM’s RADIUS defining the UNITS OF DISTANCE between Point A and Point C that can be moved IN THEORY.

We NOTICE that the ATM STEERING RT is defined by points A, B, and C, with a “Hypotenuse” line between Point A and Point C, and with two leg lines: “LegAB” between Point A and Point B; and ”LegBC” between Point A and Point C.

And again, we know that the distance between Point A and Point C—the length of the Hypotenuse line of the ATM STEERING RT—is established by the velocity of the ACOM, and we also know that the ACOM velocity = SETFx/2.

Now we can find LegAB by the known formula:

LegAB = Hypotenuse x cos (Θ)

And we can find LegBC by the known formula:

LegBC = Hypotenuse x sin(Θ)

The SLOPE, aka the STEEPNESS, of a line is calculated by the known formula:

THE RISE/THE RUN

THE RISE is the change in the 3-d Down or 3-d Up direction, i.e., the change along a 3DADL between 180-degrees and 0-degrees on the ACOM SheLL Compass, and THE RUN is the change along an “equator” line between 270-degrees and 90-degrees on the ACOM SheLL Compass, and the change can be expressed in any desired units, e.g., 3-d SheLL RADIUSes.

THE RISE = Leg BC of the ATM STEERING RT

THE RUN = LegAB of the ATM STEERING RT

So the SLOPE of the Hypotenuse can be calculated by:

SLOPE = LegBC/LegAB

And now we have all the information we need to determine ACOM SPEED AND POSITION, i.e., to MOVE THE ACOM; the problem we have to solve is that the ATM Backbone cannot TILT to Θ!

But we NOTICE that to travel from Point A to Point C, it’s technically unnecessary for the ATM Backbone to TILT, because KNOWING THE SLOPE of the Hypotenuse line between Point A and Point C, the ATM Backbone could simply traverse THE RISE (LegBC) and THE RUN (LegAB) of the SLOPE, and thereby INDIRECTLY end-up making a MOVEMENT IN DIRECTION SETFx!

And we ALSO NOTICE that when a 3-d SheLL—and more specifically, when the 423DCTCC inside of a 3-d SheLL—is in the 3-d Backbone Orientation, then it is perfectly capable of moving in THE RISE direction along a 3DADL (i.e., in the 3-d Down direction at 180-degrees on the ACOM SheLL Compass or in the 3-d Up direction at 0-degrees on the ACOM SheLL Compass.)

Then we FURTHER NOTICE that IN THEORY, it would not destroy the integrity of the ATM Backbone to CHANGE 3DADLs, which means moving in THE RUN direction (i.e., in the 270-degree or the 90-degree directions on the ACOM SheLL Compass) while remaining in the 3-d Backbone Orientation.

BUT THE PROBLEM IS THAT IT’S PHYSICALLY-IMPOSSIBLE FOR FORCEFUL STEERING to cause the ACOM’s 423DCTCC to move in THE RUN direction (i.e., to CHANGE 3DADLs) while remaining in the 3-d Backbone Orientation, because a Moving Service 🛳️ md provided at 270-degrees or at 90-degrees on the ACOM’s SheLL Compass would be BOINKING the ACOM’s PP6DCT (part of the 423DCTCC inside of the 3-d SheLL) in a SIDEWAYS direction, and all 3-d SIDEWAYS directions are RELATIVE-TO the 3-d Up and 3-d Down directions of the 3-d Backbone Orientation but not vice-versa (see Article 3), so therefore The Squeeze that was put on the PP6DCT (The Squeeze is the BUNCHING of the PP6DCT that would necessarily happen when 423DCTCC was BOINKED by an incoming 🛳️ md in a 3-d SIDEWAYS direction) could not automatically be passed-down to the 6DCT (which is in the ADL BACKBONE ORIENTATION) in the 6th dimension at the TM particle/COM attachment position.

When BOINKED in a 3-d SIDEWAYS direction, the VERTICAL PP6DCT in the ACOM’s 423DCTCC WOULD REMAIN VERTICAL—making it PHYSICALLY-IMPOSSIBLE FOR THE ACOM TO MOVE LINEARLY AT ALL—unless the Universal O/S in the 6-d COM Segment controlling the 6DCT *AGREED* to allow the PP6DCT to “HOLD” The Squeeze that was put on the PP6DCT (and the “HOLD” would have to persist during the entire Pit-Stop Time-Slot), and *ALSO AGREED* to PROGRAMMATICALLY RELEASE The Squeeze during the next On-Track Time-Slot to ENABLE the 3-d SheLL to CHANGE 3DADLs (i.e., to move linearly in THE RUN direction), which would “free” the ACOM to move linearly in THE RISE direction along the NEW 3DADL.

RECALL from Topic 3:

So now we have all the “puzzle pieces” we need to fit together to explain how the BTPs in the ATM Backbone (the ACOM and BTP1) can be programmatically controlled by the Universal O/S during the On-Track Time-Slot to do the Two-Step Dance to Move Like Tetris—or in other words, to MOVE TWICE, once to implement THE RUN of the SLOPE of the Hypotenuse of the ATM STEERING RT, and once to implement THE RISE of the SLOPE of the Hypotenuse of the ATM STEERING RT—and thereby travel a certain distance along a DIAGONAL 3-d SIDEWAYS direction line corresponding to DIRECTION SETFx, and the gist of the explanation is this:

During the Pit-Stop Time-Slot, the Universal O/S would calculate the RUN Time and the RISE Time, then during the On-Track Time-Slot, the Universal O/S would manipulate the 6DCT in the 6th dimension via 3-d Mindful Stretching to execute TWO TIMED RELEASES of The Squeeze put on the PP6DCT (i.e., the BUNCHING of the PP6DCT in DIRECTION SETFx), which was being “HELD” during the Pit-Stop Time-Slot, with ONE TIMED RELEASE occurring over the course of the RUN Time, causing the ACOM to traverse THE RUN of the SLOPE of the Hypotenuse of the ATM STEERING RT, and a SECOND TIMED RELEASE occurring over the course of the RISE Time, causing the ACOM to traverse THE RISE.

QUESTION: Is it RELEVANT that in the case of DIRECTION SETFx being a DIAGONAL 3-d sideways direction line, the ACOM would have to travel MORE DISTANCE than a lone BTP on the loose in the universe would have to travel in one straight line to get between Point A and Point C during the On-Track Time-Slot, because the Total Dance Distance of the Two-Step Dance that the ATM Backbone would have to do—the ATM Backbone would have traverse LegAB and LegBC to get from Point A to Point C—is GREATER than the straight linear distance between Point A to Point C?

ANSWER: Yes, and the RELEVANCE is that it’s impossible for the ACOM to get all the way to Point C by doing the Two-Step Dance along LegAB and LegBC in the On-Track Time-Slot; the farthest the ACOM could get would be Point C’ on the ATM STEERING RT by doing the Two-Step Dance along LegAB’ and LegB’C’.

C’ can be calculated by:

C’ = C - ( (LegAB + LegBC) - Hypotenuse)

But that’s not a problem, because we know DIRECTION SETFx = Θ, so we could simply RE-CALCULATE LegAB’ and Leg B’C’ to SCALE THE ATM STEERING RT (make it smaller without changing the SLOPE of the Hypotenuse line), so that the ACOM could do the Two-Step Dance along the legs (LegAB’ and LegB’C’) of the SCALED ATM STEERING RT and end-up at Point C’ on the Hypotenuse line at the end of the On-Track Time-Slot.

“Look at those legs. They’re like butter.”

LegAB’ = THE RUN = C’ x cos (Θ)

Leg B’C’ = THE RISE = C’ x sin(Θ)

QUESTION: How is it possible for the Two-Step Dance from Point A to Point C’ to happen at the exact VELOCITY?

ANSWER: The ACOM will automatically have PERFECT VELOCITY in the On-Track Time-Slot because MAGNITUDE SETFx is implemented by the NET THRUST generated by the Tax Payments (🔫 Emack and 🌊RTSmd) that were made by the ACOM *and* by the MSP BTP(s) during the Pit-Stop Time-Slot; the THRUST will NATURALLY be *trying* to get the ACOM to move in DIRECTION SETFx, which is a line having a SLOPE *defined* by the Two-Step Dance, so therefore there will always be an exact amount of THRUST corresponding to THE RISE and THE RUN of the SLOPE of the DIRECTION SETFx line!

QUESTION: How is it physically-possible for the ACOM to MOVE TWICE in the On-Track Time-Slot without moving FASTER THAN THE SPEED OF LIGHT?

ANSWER: The ATM Backbone can never reach the speed of light—a Hydrogen ATM’s ACOM has a maximum velocity of c/2—because the ATM Backbone has SKELETON MASS OF TWO BTPs (the ACOM and BTP1); ergo, it’s always going to be physically-possible for every ATM Backbone to CHANGE POSITIONS TWICE during the On-Track Time Slot without causing any individual BTP to *change positions* faster than the speed of light. Don’t forget that ATMs can’t move unless the ACOM is a Moving Service Recipient—in fact, individual BTPs are always going to be Moving Service Recipients, even within massive objects—and it must always remain possible for an individual BTP to *change positions* at the speed of light; so again, as long as the ATM Backbone has a maximum velocity of c/2, it will always remain possible for every BTP in every ATM to CHANGE POSITIONS AT THE SPEED OF LIGHT (i.e., CHANGE POSITIONS TWICE) during the On-Track Time-Slot.

QUESTION: Since the ACOM is the Moving Service Recipient, do we have to worry about BTP1 “keeping up” with the ACOM during the Two-Step Dance to Move Like Tetris from Point A to Point C’ on the ATM STEERING RT?

ANSWER: No, we never have to worry about BTP1 “falling off the ACOM,” because the ACOM and BTP1 have have an Absolute-Relative relationship according to the Hierarchy of Relativity of 3-d Directions (see Article 3), with BTP1’s position in the 3-d Backbone Orientation on top of the ACOM being RELATIVE-TO the ACOM’s position in the 3-d Backbone Orientation but not vice-versa, since the 3-d Up direction is RELATIVE-TO to the 3-d Down direction but not vice-versa. Ergo, wherever the ACOM may go, BTP1’s position must AUTOMATICALLY change to remain POSITIONALLY RELATIVE-TO to the ACOM, because THE EXISTENCE OF BTP1’s POSITION DEPENDS-ON THE ACOM’S POSITION. In other words, the ACOM’s position is THE CAUSE of BTP1’s position, and that CAUSE-AND-EFFECT RELATIONSHIP must remain TRUE even if the ACOM moves.

Also NOTE that the PROGRAMMATICALLY-CONTROLLED Two-Step Dance to Move Like Tetris could never be CAUSED by a BTP—again, it must be PROGRAMMATICALLY CAUSED—ergo, as far as all other BTPs are concerned, the ACOM and BTP1 *always remain* in the 3-d Backbone Orientation.

QUESTION: Do we have to worry about how BTP3 is going to follow the ATM Backbone during the Two-Step Dance to Move Like Tetris from Point A to Point C’ on the ATM STEERING RT?

ANSWER: No, we never have to worry about BTP3 “keeping up” with the ACOM and BTP1, because the ATM Backbone and BTP3 have an Absolute-Relative relationship according to the Hierarchy of Relativity of 3-d Directions, with BTP3’s position being RELATIVE-TO the ATM Backbone’s position but not vice-versa, since the 3-d sideways directions are all RELATIVE-TO both the 3-d Up direction and the 3-d Down direction on the ADL Backbone, but the 3-d Up/3-d Down directions are not relative-to any of the 3-d sideways directions. Ergo, wherever the ATM Backbone may go, BTP3’s position must AUTOMATICALLY change to remain POSITIONALLY RELATIVE-TO the ATM Backbone, because THE EXISTENCE OF BTP3’s POSITION DEPENDS-ON THE ATM BACKBONE’S POSITION. In other words, the ATM Backbone’s position is THE CAUSE of BTP3’s position, and that CAUSE-AND-EFFECT RELATIONSHIP must remain TRUE even if the ATM Backbone moves.

QUESTION: Then WHY DO WE NEED MOVING SERVICES AT ALL, if the ACOM’s movements can be PROGRAMMATICALLY CONTROLLED, and BTP1 and BTP3 will follow the ACOM wherever it goes?

ANSWER: One reason is that the LAWS OF MOTION *cannot require* MATTER to have PRE-DETERMINED DESTINATIONS, because that makes AUTONOMOUS CONSCIOUS MOVEMENTS impossible; here NOTE that the fact that Point C’ can be calculated is not the same as PRE-DETERMINING DESTINATION, because the ACOM is not REQUIRED to get to Point C’ without having a collision.

Another, equally important, reason is that the Law of Conservation of Energy *requires* MATTER to have VELOCITY that is CAUSED BY THE EXPERIENCE OF NET FORCE (NET THRUST); there’s no way to PROGRAMMATICALLY GENERATE ENERGY lol.

To repeat the VELOCITY Q&A from above (and here I quote between the 📝 icons):

📝 📝 📝 📝 📝 📝 📝 📝 📝 📝

QUESTION: How is it possible for the Two-Step Dance from Point A to Point C’ to happen at the exact VELOCITY?

ANSWER: The ACOM will automatically have PERFECT VELOCITY in the On-Track Time-Slot because MAGNITUDE SETFx is implemented by the NET THRUST generated by the Tax Payments (WPD Tax Payments 🔫, which become Emack, and 🌊RTSmd) that were made by the ACOM *and* by the MSP BTP(s) during the Pit-Stop Time-Slot; the THRUST will NATURALLY be *trying* to get the ACOM to move in DIRECTION SETFx, which is a line having a SLOPE *defined* by the Two-Step Dance, so therefore there will always be an exact amount of THRUST corresponding to THE RISE and THE RUN of the SLOPE of the DIRECTION SETFx line!

📝 📝 📝 📝 📝 📝 📝 📝 📝 📝

QUESTION: How, *exactly*, does the Universal O/S match-up the THRUST with the TIMING of the Two-Step Dance along LegAB’ and LegB’C’ of the ATM STEERING RT during the On-Track Time-Slot?

ANSWER: During the On-Track Time-Slot, the DIRECTIONAL THRUST—the VELOCITY—is automatic; then concurrently with movement at the predetermined VELOCITY, the Universal O/S manipulates the 6DCT via 3-d Mindful Stretching to execute a TIMED RELEASE of The Squeeze put on the PP6DCT (i.e., the BUNCHING of the PP6DCT in DIRECTION SETFx), which was being “HELD” during the Pit-Stop Time-Slot; and more specifically, the TIMED RELEASE of The Squeeze is enabled by a CALCULATION of the RUN Time and the RISE Time that went like this during the Pit-Stop Time-Slot:

We know the Dance Velocity

We also know the Total Dance Distance = LegAB’ + LegB’C’

We further know the Total Dance Distance = (Dance Velocity) x (Total Dance Time)

And therefore we can SOLVE for the Total Dance Time

And of course the Total Dance Time = RUN Time + RISE Time

We don’t know—and WE NEED TO KNOW—the RUN Time and the RISE Time, but we do know what PERCENTAGE of the Total Dance Distance that THE RUN, LegAB’, and THE RISE, LegB’C’, comprise:

Percentage RUN Total Dance Distance = (LegAB’/Total Dance Distance) x 100

Percentage RISE Total Dance Distance = (LegB’C’/Total Dance Distance) x 100

And we also know Percentage RUN Total Dance Distance = Percentage RUN Time, and Percentage RISE Total Dance Distance = Percentage RISE Time

So now we can can calculate the RUN Time = (Total Dance Time) x (Percentage RUN Time), and the RISE Time = (Total Dance Time) x (Percentage RISE Time)

And that’s all we need to know!

We should ASSUME that THE RUN will always be traversed before THE RISE during the On-Track Time-Slot, because in that manner, the Universal O/S could BEGIN the On-Track Time-Slot by using 3-d Mindful Stretching to RELEASE THE ACOM’s PP6DCT in the direction of THE RUN (270-degrees or 90-degrees on the ACOM SheLL Compass) for an amount of TIME equal to the RUN Time, which would cause the ACOM to CHANGE 3DADLs by traveling the distance of LegAB’.

Then the Universal O/S’s job would be done!

After the RUN Time was done, the Universal O/S could COMPLETELY RELEASE THE ACOM’s PP6DCT, which would automatically cause the PP6DCT to *snap* back into the 3-d Backbone Orientation on the new 3DADL, then the remaining THRUST would automatically cause the ACOM to traverse THE RISE (move in the 180-degree or 0-degree direction on the ACOM SheLL Compass) for an amount of TIME equal to the RISE Time, with the ACOM running out of THRUST bang-on Point C’, *just in time* for the Pit-Stop Time-Slot.

End of BREAKDOWN of the ATM BACKBONE TWO-STEP DANCE TO MOVE LIKE TETRIS DIAGRAM, ft. the ATM STEERING RIGHT TRIANGLE (“RT”)

End of Topic 11!

☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️ ☕️

In joy,

Frank

Comments