1986 Multiversal Correspondence Event

While direct correspondence between different universes before individually opening connections to the multiverse is rare, there are a few reports indicating to direct multiversal correspondence of those universes. One of the most commonly reported incidents of such kind is the 1986 Multiversal Correspondence Event. In some time-concurrent universes (i.e. universes where time began at the same instance and where it flows indistinguishably, causing both universes to share the same time at any moment) where Orbital was founded in 1982, files saved to the hard drives of specific CMD-Block devices appeared to vanish as soon as the computer was shut down, being replaced by brand new files that nobody at these companies claimed to create.
== History ==
In most universes, Orbital began to develop computers with the CMD-Block Model I in 1982. By 1986, most Orbitals had moved on to the CMD-Block Model III, first released in 1985, and a new line of computers intended for home use, the CMD-84 machines first released in 1984. Despite these developments in technology, the CMD-Block Model I was still in wide usage within the Orbital office spaces.
The first correspondence incident is reported to occur between March 17 and March 21 1986, varying in different universes. A power outage in the region causes all CMD-Block Model I hard drives to become corrupted, making it seem like every file on all systems was wiped. A few hours later, various employees began to report files spontaneously reappearing on their computers, however the files were slightly different from the files that they had written before. At first this was suspected to be a consequence of the power outage file corruption, but closer examination revealed entirely different passages of text in some of the files, even describing specific Orbital CMD modules that some Orbitals had never heard of before. Several reenactions of the power outage were attempted under the same conditions as the original outage, but none yielded the same results that the original outage had had, not even erasing the files.