US Strategic Command Posts Nuke Launch Code For WashingtonD.C. After Shock Reveal Of Trump Overthrow Plot
By: Sorcha Faal, and as reported to her Western Subscribers
A gobsmacking new Security Council (SC) report circulating in the Kremlin today sees its transcript showing Security Council Members discussing a classified at the highest level “Of Special Importance” document compiled by the General Directorate of the General Staff of the Armed Forces (GRU)—a Russian military intelligence document that shockingly reveals that at 0349 hrs GMT+3 (Moscow local time 3:49 AM) on 29 March, the Ministry of Defense (MoD) activated to alert status Aerospace Defence Forces (ADF) in response to a “warlike-belligerent” [Russian word: воинственный] act occurring 60-seconds earlier—an act occurring at 1948 hrs GMT-5 (Washington D.C. local time 7:48 PM) on 28 March, and was when the United States Strategic Command (STRATCOM) posted on its official Twitter feed the computer cipher message: “;l;;gmlxzssaw”—that was followed nearly 8-hours later, at 0318 hrs GMT-5 (Washington D.C. local time 3:18 AM) on 29 March, by STRATCOM posting another message below their prior one stating: “Apologies for any confusion…Please disregard this post”.
Unmistakable about the first STRATCOM posted message “;l;;gmlxzssaw”, however, this GRU document says, is that this cipher is a character encoding using ASCII whose true message is “059 108 059 059 103 109 108 120 122 115 115 097 119 013 010”—as confirmed by ASCII to Text Conversion and verified by Decimal To Text analysis—is a valid launch code authorizing the Francis E. Warren Air Force Base in Cheyenne-Wyoming to release a single SM-65 Atlas Intercontinental Ballistic Missile containing a W49 Thermonuclear Warhead—whose directed release-to-target is Washington D.C.—but for reasons left to be explained, STRATCOM posted this nuclear launch code yesterday knowing that it was only valid during the Cold War year of 1963.[Note: Some words and/or phrases appearing in quotes in this report are English language approximations of Russian words/phrases having no exact counterpart.]
According to the very limited portions of this highly classified report permitted to be commented on by various ministries, the American Standard Code for Information Interchange (ASCII) was published as ASA X3.4 in 1963—uses a 7-bit binary code to represent text and other characters within computers, communications equipment, and other devices—was based on the earlier teleprinter encoding systems—and was actually designed for use with teletypes.
One of the first users of ASCII encoding, this report details, was the IBM AN/FSQ-31 SAC Data Processing System, which was the United States Air Force command, control, and coordination system for the Cold War nuclear weapon holding Strategic Air Command (SAC)—was likewise used in the ITT 465L Strategic Air Command Control System, which was the network of computer and communication systems for command and control of Strategic Air Command combat aircraft, refueling tankers, ballistic missiles—as well as the Cold War era IBM 4020 Military Computer—all of which received ASCII encoded nuclear weapon launch orders through the United States Air Force’s first high-speed data communications network Automatic Digital Network (AUTODIN) deployed in 1962.
Strategic Air Command tests nuclear weapon launch teletype system (above) in 1962.
The Cold War years of 1962 and 1963 when the US Air Force deployed AUTODIN using ASCII encoding for authorizing the release of nuclear weapons, this report continues, were the most perilous in modern human history because of the failed 1961 invasion of Cuba by rogue elements within the Pentagon and CIA known as the “Bay of Pigs” fiasco—a failed invasion said to have caused President John Kennedy to say he “wanted to splinter the CIA. in a thousand pieces and scatter it to the winds”—did see President Kennedy forcing CIA Director Allen Dulles and his entourage, including Deputy Director for Plans Richard M. Bissell Jr. and Deputy Director Charles Cabell, to all resign—all of which was followed by the October Crisis of 1962 (aka Cuban Missile Crisis) that brought the world to the brink of a nuclear holocaust.
The DeepState publically executed President John Kennedy by blowing his head apart (above photo) while he was seated next to his wife as a reminder to anyone daring to side with the American people against them.
Because these US military commanders foolishly gave themselves secret access to their nation’s nuclear launch codes using the 8-digit number 00000000, this report concludes, Soviet intelligence officers of the former Committee for State Security (KGB) were able to gain access to them, which, in turn, enabled GRU military intelligence analysts to quickly decode the message STRATCOM posted yesterday—a simple decoding of this ASCII cipher based on limited information, as immediately after President Kennedy was executed these launch codes were changed—and though why this message was sent, who it’s intended for, and who sent it remain unknown, the initial GRU military intelligence analysis points toward the recently filed US Federal Court case JUDICIAL WATCH, INC. vs. U.S. DEPARTMENT OF DEFENSE—a mind-blowing case filed by Judicial Watch demanding that the US Federal Court order the Pentagon to immediately release all information and documents they have relating to a secret conversation held on 8 January between socialist Democrat Party leader US House Speaker Nancy Pelosi and Chairman of the Joint Chiefs of Staff General Mark Milley---a secret conversation that should have never taken place as Pelosi is not in the US military command structure—an ominous call wherein Pelosi urged General Milley to overthrow President Trump—and saw this secret call occurring at the same time General Milley was openly defying President Trump’s direct order to remove all US troops from Afghanistan by Christmas day of last year—all of which are elements further proving that a traitorous plot was deployed to overthrow President Trump, and “someone” with nuclear weapon access knows this is true and plans on doing something about it.