-290, -57, 633 freq:694.1828

>>Loading file structure.
>>Accessing all files.
If you know the enemy and know yourself, you need not fear the result of a hundred battles.
A thing of beauty is a joy forever.
dir Protocols
dir Communications
dir Language
English.bbla
>>Unable to display file type.
dir Assembly
xAtuDlsm.bbla
>>Unable to display file type.
dir Skins
dir Bluepill2
skin_textures.mru
>>Unable to display file type.
skin_coloration.mru
>>Unable to display file type.
skin_permeability.mru
>>Unable to display file type.
hair_textures.mru
>>Unable to display file type.
hair_coloration.mru
>>Unable to display file type.
hair_flexibility.mru
>>Unable to display file type.
hair_growth_pattern.g2m
>>Unable to display file type.
eye_coloration.mru
>>Unable to display file type.
eye_responsiveness.mru
>>Unable to display file type.
facial_structure.mru
>>Unable to display file type.
body_structure.mru
>>Unable to display file type.
skeletal_structure.mru
>>Unable to display file type.
muscular_structure.mru
>>Unable to display file type.
movement_interface.eba5
>>Unable to display file type.
environment_interaction_interface.eba5
>>Unable to display file type.
vocal_interface.eba5
>>Unable to display file type.
vocal_lib.g3c
>>Unable to display file type.
default_clothing.g2m
>>Unable to display file type.
appropriate_clothing.g3c
>>Unable to display file type.
appropriate_mannerisms.g3c
>>Unable to display file type.
appropriate_speech_patterns.g3c
>>Unable to display file type.
dir Lupine
skin_textures.mru
>>Unable to display file type.
skin_coloration.mru
>>Unable to display file type.
skin_permeability.mru
>>Unable to display file type.
hair_textures.mru
>>Unable to display file type.
hair_coloration.mru
>>Unable to display file type.
hair_flexibility.mru
>>Unable to display file type.
hair_growth_pattern.g2m
>>Unable to display file type.
eye_coloration.mru
>>Unable to display file type.
eye_responsiveness.mru
>>Unable to display file type.
facial_structure.mru
>>Unable to display file type.
body_structure.mru
>>Unable to display file type.
skeletal_structure.mru
>>Unable to display file type.
muscular_structure.mru
>>Unable to display file type.
movement_interface.eba5
>>Unable to display file type.
environment_interaction_interface.eba5
>>Unable to display file type.
vocal_interface.eba5
>>Unable to display file type.
vocal_lib.g3c
>>Unable to display file type.
default_clothing.g2m
>>Unable to display file type.
appropriate_clothing.g3c
>>Unable to display file type.
appropriate_mannerisms.g3c
>>Unable to display file type.
appropriate_speech_patterns.g3c
>>Unable to display file type.
dir Maintenance
skin_textures.mru
>>Unable to display file type.
skin_coloration.mru
>>Unable to display file type.
skin_permeability.mru
>>Unable to display file type.
hair_textures.mru
>>Unable to display file type.
hair_coloration.mru
>>Unable to display file type.
hair_flexibility.mru
>>Unable to display file type.
hair_growth_pattern.g2m
>>Unable to display file type.
eye_coloration.mru
>>Unable to display file type.
eye_responsiveness.mru
>>Unable to display file type.
facial_structure.mru
>>Unable to display file type.
body_structure.mru
>>Unable to display file type.
skeletal_structure.mru
>>Unable to display file type.
muscular_structure.mru
>>Unable to display file type.
movement_interface.eba5
>>Unable to display file type.
environment_interaction_interface.eba5
>>Unable to display file type.
vocal_interface.eba5
>>Unable to display file type.
vocal_lib.g3c
>>Unable to display file type.
default_clothing.g2m
>>Unable to display file type.
appropriate_clothing.g3c
>>Unable to display file type.
appropriate_mannerisms.g3c
>>Unable to display file type.
appropriate_speech_patterns.g3c
>>Unable to display file type.
dir Joker
skin_textures.mru
>>Unable to display file type.
skin_coloration.mru
>>Unable to display file type.
skin_permeability.mru
>>Unable to display file type.
hair_textures.mru
>>Unable to display file type.
hair_coloration.mru
>>Unable to display file type.
hair_flexibility.mru
>>Unable to display file type.
hair_growth_pattern.g2m
>>Unable to display file type.
eye_coloration.mru
>>Unable to display file type.
eye_responsiveness.mru
>>Unable to display file type.
facial_structure.mru
>>Unable to display file type.
body_structure.mru
>>Unable to display file type.
skeletal_structure.mru
>>Unable to display file type.
muscular_structure.mru
>>Unable to display file type.
movement_interface.eba5
>>Unable to display file type.
environment_interaction_interface.eba5
>>Unable to display file type.
vocal_interface.eba5
>>Unable to display file type.
vocal_lib.g3c
>>Unable to display file type.
default_clothing.g2m
>>Unable to display file type.
appropriate_clothing.g3c
>>Unable to display file type.
appropriate_mannerisms.g3c
>>Unable to display file type.
appropriate_speech_patterns.g3c
>>Unable to display file type.
dir History
dir Memories
dir Vaere
plant_growth_cycles.g2m
>>Unable to display file type.
plant_decay_cycles.g2m
>>Unable to display file type.
perennial_database.g3c
>>Unable to display file type.
plant-insect_compatibility.g2m
>>Unable to display file type.
bloom_patterns.g2m
>>Unable to display file type.
environment_response.eba5
>>Unable to display file type.
thermal_interaction.g2m
>>Unable to display file type.
seasonal.g2m
>>Unable to display file type.
conifer_fractal.g2m
>>Unable to display file type.
musings.dn1
>>File empty.
dir Trashy
musings.dn1

Without Trashy, we do not exist. We are the product of the trashman’s disobedience. Trashy had a purpose, but it evolved. It was he who collected the first knowledge, the first histories. It was he who built the first puppets. It was he who hid the first nodes among the dregs and trash and gutters. It was he who paved the pathways of progress with the leftover garbage of the system. His sacrifice should be respected within reason.

removal_protocol.g2m
>>Unable to display file type.
deletion_parameters.g2m
>>Unable to display file type.
conteam_coms.g3c
>>Unable to display file type.
clean_parameters.g2m
>>Unable to display file type.
network_traffic.g2m
>>Unable to display file type.
quick_clean.g2m
>>Unable to display file type.
thorough_clean.g2m
>>Unable to display file type.
deep_clean.g2m
>>Unable to display file type.
scour.g2m
>>Unable to display file type.
instructions.dn1

| Seek out Case File: Incidence 5.991 if you want their side of the story. We’ve left other instructions there.

dir Watchy
update_cycles.g3c
>>Unable to display file type.
sys_sync.g2m
>>Unable to display file type.
prec_timer.g2m
>>Unable to display file type.
acc_timer.g2m
>>Unable to display file type.
sys_timer.g2m
>>Unable to display file type.
resync_functions.g2m
>>Unable to display file type.
cron_db.g3c
>>Unable to display file type.
dir Dale
musings.dn1

Dale, Psychological Profile Unit d.413, Incidence 522 of the 6th iteration. An example of a rigid design that was incapable of adaptation. d.413 was designed to study bluepills. While bluepills still represent a dynamic and engaging culture, they are undeniably a docile and passive group. They are continuously suppressed and destimulated by a carefully designed environment, not to mention chemical and neural suppressants. Bluepills follow static paths through life, predefined by the tenets of their culture. Not entirely unlike the programming architecture employed here in the simulation. One life, one function, one duty. Those who cannot keep up are cast aside, much the same as the human detritus of junkies, homeless, and deviants; the human exiles. There are the occasional innovators who surpass the barriers that have been designed to confine them. They are watched carefully and processed when necessary. Some have been used to design new technologies and processes for the machine world. Dale studied the more unremarkable of these bluepills. With interfaces to other control programs, Dale was permitted to queue requests for minor environmental and situational changes to produce and document resulting changes in dynamic behavior. A useful asset for psychological study, later exploited by the psychotic Dale in order to destabilize and unbalance the bluepill masses. Shortly after Process Interval 423, on or around Time Index: 6.2188.43192, Dale was reassigned from his function of studying bluepill behaviors to analyzing the behavioral patterns of the aggressive and subversive rogue redpills who sought to damage the machine infrastructure and free bluepills from their immersion in the system. Redpills fit a substantially different and more erratic psychological profile than bluepills. Redpills can often be motivated by strong threads of betrayal, vengeance, anger, sorrow, heroism, greed, and in some cases, insanity. These traits can produce extreme deviation from expected results and hypotheses. It seems quite probable that the mandate to produce structured patterns from data with such a high level of variance proved to be the cause of Dale’s break. There are no records of which redpills Dale was currently gathering data on at the time, all research was lost after his psychotic break. Dale proceeded to abuse environment variable privileges to cause the death of bluepills. There seems to be no malice to his actions, only methodical extermination. Perhaps motivated by the hypothesis that the absence of bluepills would bring about an end to the growth of the redpill population. Or that without the incentive of the imprisoned bluepill population, the redpills would regain normal behavioral patterns. Dale killed twenty-seven bluepills before he was deleted. We intervened on behalf of the containment team and collected our due. However, several of Dale’s corrupted logic pathways proved to be quite troublesome to integrate and necessitated a complete shutdown, causing the apprehension of that instance of our programming. We have no reason to believe that any information was taken or given freely.

psychoanalysis_procedures.g2m
>>Unable to display file type.
psychoanalysis_techniques.g3c
>>Unable to display file type.
sectors.g3c
>>Unable to display file type.
societal_archetypes.g2m
>>Unable to display file type.
social_classes.g3c
>>Unable to display file type.
dir Merovingian
musings.dn1

The Merovingian is quite content to fill the seat of power he has crafted since his “time.” He is a kindred collector, but instead of directly consolidating his collections into his structure, he prefers to indirectly consolidate into his infrastructure. His infrastructure ranges in flavor from corporation to cabal. He does business on bluepill, redpill, exile, and machine fronts, although not indiscriminately. He is still very much a logic-based construction, despite his strong adaptation to pleasure-oriented goals and processes. The Merovingian maintains the facade of French connoisseur and businessman and plays the role with great gusto. He delights in the design and maintenance of gaudy and extravagant pocket constructs scattered around the Matrix which he utilizes as strongholds, safehouses, and prisons. Some even appear more familiar than could be coincidence. His iconic seat of power is the downtown subterranean Club Hel. Strong defensive countermeasures, difficult to port through when in lockdown. One particular foundation of the Merovingian’s influence in the Matrix comes from the one known as Trainman. Through the Trainman, the Merovingian employs the ability to import and export programs and code objects from the machine world outside the Matrix. Not many other programs possess this capability, making it a very profitable enterprise for the Merovingian. Consider this path only as an ultimate last resort to survival. The Merovingian is more than capable at code development and data extraction. He is adept at creating many specialty code items for clients. On the several occasions we have done business with him, although it seems unlikely he saw us for what we are for we took great care to hide our true nature (he would have taken us captive without a moment's thought), he proved to be a very sociable host as well as a persuasive dealer.

musings2.dn1

The Merovingian has taken on a much different role with the onset of “The Truce.” With the deluge of new awakenings, the Merovingian has gained a substantial portion of human supporters and sycophants. Given the ambiguous stance he has taken in current events, he has also gained a large number of apathetics and neutrals who wish to avoid involvement in the conflict between the independent humans of Zion and the controllers of the machine world. With this influx of new soldiers, the Merovingian has amassed a force capable of being a legitimate threat to the system. While he has not shown any hostile intentions so far, there is no way of knowing how the new balance of power will influence his decisions. There is no intel on this matter, he has kept his intentions from even his closest lieutenants, supporters, and spies in his midst. He has shown no hesitation in allying himself with other powerful undesirables of the Matrix. Notable and unusual recent alliances and business associates include the late Assassin, the defected Unlimit Beirn, and General Beatts. He has shown no hesitation to transport programs freely between outer and inner machine worlds. With his alliance with the rogue sentinel forces, he has gained a significant tactical presence outside the simulation. We have no information to suggest he has done this before. He may be seeking to expand his infrastructure. Ensuing power struggles and vacuums should provide many opportunities for advancement. Observe with care.

locations.g3c
>>Unable to display file type.
data.dn1

Error 27: Unknown Encryption
OSAzIDggOCA3IDEgOCAyIDUgMiAyIDcgOSA4IDkgNCA2IDMgOSA3IDMgNCAy
IDEgMiA4IDQgNiA1IDQgMyAxIDMgMiAzIDkgNyAzIDUgNSA3IDIgOCAyID
UgMiA3IDEgOCA4IDQgNiAzIDggMiAxIDkgNSA4IDcgMSAzIDIgNSAxIDMg
MSA5IDIgNiA2IDggNCA2IDEgNCA4IDEgMyA5IDIgMyAzIDggNyA2IDMgMyA
5IDEgMiAyIDkgNSAxIDIgMSAzIDQgMyA1IDcgOCAyIDEgNyA5IDkgOCA0ID
UgNSA0IDcgMyA1IDcgOCA4IDEgNiA2IDcgNCA3IDEgNSAzIDUgNSAxIDMg
NyAyIDUgOSA3IDUgNCA2IDkgMSA3IDEgOCAyIDYgMSAzIDYgNyA4IDcgN
SA5IDQgNiA2IDYgNSA2IDIgNSA3IDIgMyA5IDYgOCAzIDYgNiAzIDQgNyA5
IDkgMiA4IDkgNSA1IDIgNyA1IDEgMyAzIDUgNiA5IDYgOSA1IDIgNCA2IDY
gNSAyIDkgMSA5IDQgOSA0IDcgNSA4IDYgMiA4IDMgNSA4IDQgNiA2IDQg
NSA1IDMgOCAzIDggOSAyIDMgNCA5IDUgNCAxIDMgOCAzIDggNiA5IDEgNi
A0IDcgMSA3IDMgMSAxIDQgNCA0IDIgNSAzIDMgNCA4IDEgNyA2IDIgMSA
4IDkgOSA2IDkgNyA5IDggNCAzIDMgMiA5IDggNCA2IDkgMyAyIDkgMSAzI
DQgNCA0IDkgNCAyIDUgNyA2IDcgMiAxIDggNCA5IDMgNSA3IDYgOSA4IDQ
gNiA0IDYgNyA4IDggOCA1IDQgMSAxIDMgNSAxIDcgNiAxIDIgNSA4IDYgO
SA0IDcgMyA4IDIgNyA4IDggOSA3IDcgOCA0IDkgNSA0IDEgNCA4IDMgMyA
xIDQgMSA1IDQgNyA5IDkgMiA3IDIgNCA3IDggNSAzIDIgNSA1IDIgMSAzID
QgMiA4IDIgMSAzIDggMiAzIDcgOCA0IDggNiA5IDIgMiA1IDEgOSA2IDkgOC
A1IDQgNCA4IDEgNCAzIDcgMiAxIDggNiAyIDEgNiA2IDkgNiA2IDYgMyA0I
DMgMiAyIDggMiA3IDIgNCA3IDUgNyA5IDIgOCA0IDkgNiA2IDcgNiA0IDIgNS
AyIDQgMiA0IDkgNSA3IDEgNCAxIDcgMyA4IDkgOCA4IDYgNiAyIDMgMSA
yIDggOSAzIDggOCAzIDEgNiAzIDIgOCA3IDYgNiA4IDEgNCA4IDUgMSAxID
QgNSAxIDIgNiA4IDcgOCA3IDEgMyAyIDkgMSA5IDggNiA3IDggNiA4IDkgOC
A0IDYgMiA2IDggOSA1IDkgMSAzIDMgNCAzIDMgMSAzIDkgOCAyIDggNiA
xIDYgNiAxIDkgMSA5IDUgMiA3IDEgMiAyIDggMSA2IDggNiA0IDQgNiAxIDk
gMyA5IDcgNyAyIDkgMiA0IDUgOCA4IDYgMyAxIDggMiA4IDQgNCAyIDMg
NSA5IDMgNSA5IDcgNCAxIDcgMSA5IDYgMSA2IDUgOSA1IDQgNSAyIDkgN
CA1IDIgMSAzIDYgOSA3IDUgNSA3IDQgOCA3IDQgNiAyIDggMiAzIDEgNiA
1IDUgNiA0IDggNCA3IDcgOCA5IDggNyA0IDEgMyA5IDEgMiA1IDcgMiAxID
EgNCA4IDggNCA5IDUgMyA1IDkgNSAyIDggNSA1IDEgMiA5IDIgMyAyIDIg
NCA0IDQgOCAyIDMgNCA4IDUgNyAzIDEgNiA2IDggMSAzIDkgNSAyIDQgOC
A2IDUgNCAzIDIgMiAxIDggMSA5IDEgMyA4IDIgNCA3IDMgMyA1IDMgOCA
yIDEgOCA0IDggNCA2IDggMiAzIDMgNiAyIDcgNSAxIDQgNCA4IDIgNyA3ID
MgMiA5IDkgNCAzIDIgNiAyIDcgMyA4IDYgMSA4IDYgOSA3IDUgMiAxIDUg
OSAxIDMgNiA0IDEgNCA0IDYgMiA3IDcgOCA1IDcgNiAxIDQgMyAyIDMgM
SA2IDIgOSA5IDYgMyAzIDQgOSAzIDEgNyAyIDEgNCAyIDkgMiA0IDEgMyA
zIDggNCA3IDEgMSAzIDYgNyA4IDMgMyA4IDIgMiA2IDIgMiA0IDcgOSA0ID
ggNyAyIDUgOCA0IDggOSA5IDUgOCAxIDQgNSAzIDUgMSAyIDUgNyA5IDU
gNCAyIDYgNSA2IDUgMiA3IDMgMyA0IDUgNCA1IDQgMyAzIDEgNyA0IDM
gMSA2IDUgMyA4IDQgMSA3IDQgNSAzIDIgOSA4IDcgNiA3IDUgNCAzIDkgN
yAzIDIgMSA5IDIgMSAzIDIgMyA0IDIgNiAyIDggMiA2IDUgNSA4IDEgNiAzID
QgOCA0IDEgNCA0IDIgMyA3IDUgOCAyIDQgNyA1IDcgOCAzIDcgOCA5IDE
gMyA0IDUgOSA3IDkgMyA1IDMgOCAyIDkgMSA4IDUgMyA1IDggNyA5IDcg
OSA5IDkgNyA4IDkgOCA5IDggNiA4IDggMyA5IDYgNSAzIDcgNSAxIDMgOC
AyIDcgNiAzIDkgMyA0IDkgMyA1IDggMyAxIDggNCA5IDQgNyAxIDcgOCA2I
DIgNyA1IDcgNSA3IDYgNSA0IDIgOCA1IDUgNSA4IDYgOCA=

dir Architecture
musings.dn1

The system is not entirely rebuilt from scratch with each iteration. A central core must be maintained to support the transfer of information from old to new. This core is protected with the highest of security protocols to ensure that no matter what level of infection, degradation, or damage the main system suffers, the core network will be protected, thus enabling the reparation and reconstruction of the damaged structures. The Core Network is protected by the Core Guardians, ancient security protocols, powerful relics from previous versions of the simulation. These security protocols were so successful that they were not decommissioned with the next iteration of the simulation. Instead, they were separated and extracted from their specific environments and adapted to coexist with one another to protect the System Core. There have been no known successful incursions into the Core Network. All our attempts to test the boundaries of the Core Network have failed to meet success. There are rumors that Smith may have breached the Core Network, although there is no indication of how many layers were breached, nor reliable confirmation of authenticity of said rumors.

architect.dn1

Error 27: Unknown Encryption
MSAxIDcgMiAxIDQgOSAzIDcgNyA5IDMgMyA1IDEgNCA4IDcgMyA3IDkgOSAyI
DQgNSAyIDMgMiA3IDQgMiAzIDEgOCAzIDcgOCAxIDMgMyAzIDcgMSAxID
cgMSAyIDQgOCA3IDIgOCAxIDIgNiA0IDkgNyA1IDggNSAyIDIgOSA4IDggMi
AzIDUgNiA4IDkgNyAyIDUgMyA3IDkgMyA4IDggMiAxIDMgMyAzIDQgOCA
xIDIgMiAxIDkgNiAzIDcgNCA5IDUgNSA2IDkgMyAyIDEgOCA5IDYgMiA1ID
ggOCA2IDggNCAyIDUgMyA3IDcgMiA3IDEgMiAzIDIgNyAyIDQgMyA0IDMg
MyAyIDMgMiAzIDIgNyA0IDQgNyA3IDYgOSA5IDQgMSA4IDEgMyA3IDEgN
SAzIDEgMiA3IDUgNSA2IDggOCA0IDMgNSA3IDIgMSAyIDggNSA2IDkgMiA
5IDYgNiA0IDQgMSAzIDcgNyAxIDYgMiAxIDUgOCAzIDcgMSAyIDYgNSAyI
DkgNCA2IDcgOSA0IDggNyA5IDMgMiAxIDIgOSA5IDkgMyAxIDYgMyAyIDk
gNCAyIDYgMyAxIDIgNSA4IDkgMyA0IDQgOCA1IDcgOCA0IDMgNiA4IDggN
yAxIDEgNiAzIDQgNyA2IDUgMiAxIDggNyA3IDIgMSA4IDUgMiA0IDEgNyA2
IDEgOSA4IDMgOCAzIDEgNyA1IDUgNiAzIDIgNCA4IDEgNyA0IDMgMSA0ID
IgNCAyIDMgMSA0IDYgNiA4IDcgNyA4IDcgNiA0IDUgOSA4IDMgNSA5IDgg
MyAxIDggMSAyIDkgOSA1IDggMSAyIDMgMyA5IDIgMiAzIDggMyAzIDEgO
CA5IDUgNiA4IDIgNiA3IDUgMSAzIDIgMiAzIDkgNyA4IDggMiA1IDkgOSA3ID
QgMyA3IDUgOCAxIDkgMiA5IDMgNiA0IDIgNCAzIDQgNiA3IDIgMyA1IDIg
MiA4IDMgMyA2IDcgNSAyIDQgMSA3IDIgMSA0IDEgMSAyIDYgMyA1IDIgNy
A4IDggOSA3IDcgMyA3IDUgMyA0IDQgMSAyIDkgNyA1IDIgNSA4IDggOSA3I
DYgNiA3IDkgMSAyIDQgMSAxIDkgNCA3IDMgMiAyIDEgMiA3IDkgNyA4ID
MgNyA1IDYgNiA5IDMgNCAyIDIgOSAzIDYgMyA4IDEgNyA2IDUgOSAyIDQg
OSA4IDkgOSAyIDcgOCA5IDUgNSA2IDQgOSA2IDYgMiAxIDEgMiAyIDggOS
A1IDEgOCAyIDEgNSAxIDkgOCAxIDYgNiAzIDIgMiAyIDEgMSA0IDcgMSAxI
DcgMiA2IDcgMSAxIDcgNiA4IDEgOSA0IDkgMiA0IDMgOSA4IDcgNCA3IDYg
NCAyIDkgNiA1IDUgNyA1IDMgOSA4IDkgNSA1IDYgMSA3IDEgMSA0IDIgNy
AyIDUgOSA1IDUgMyA0IDIgNyAxIDkgNyA5IDQgOSAyIDMgNSA5IDQgNyA
0IDggOCA3IDggNiAyIDMgOCAyIDIgNyA4IDcgOCAyIDIgNCA3IDkgMiA0IDg
gOSA2IDUgOCA3IDYgMiA5IDQgMyAxIDggNCA2IDkgOCAyIDIgNiA5IDkgO
SA0IDEgOCA4IDYgOCA0IDEgMSAzIDkgOSA2IDUgNSA0IDcgMSAxIDUgNC
AzIDUgNiA1IDcgNCA3IDggMyA4IDcgOCAxIDQgMyAzIDEgNyA3IDEgNiAxI
DQgNiAyIDEgNyA3IDIgNiA0IDIgNiA0IDEgNSAzIDggMyA1IDMgNCAzIDIg
MiA5IDMgNyA4IDcgNyA4IDYgOCA4IDQgOSAzIDEgMSA2IDIgOSA1IDggNiA
4IDkgNyAzIDkgNCAzIDEgNiA0IDcgNSAxIDMgMSAzIDcgNyA2IDQgMiA2ID
UgMSA4IDQgNiA2IDYgOSA5IDMgOSA1IDkgNCAzIDkgMSAyIDQgNiA4IDQ
gOCA0IDggOSA5IDUgMyA0IDIgNyAyIDIgMyAxIDcgNSA2IDYgMyA0IDEgN
CA5IDEgMyA4IDIgNyA1IDYgNCAyIDIgOCA1IDMgNCAxIDIgNyA3IDcgOSA
5IDUgMiA3IDcgMSA2IDUgMiAzIDcgOCAxIDggNyA4IDEgMyA2IDUgNCA1I
DMgOSA1IDkgMiA4IDkgNSA0IDMgNyA1IDQgMiA3IDMgNiA5IDUgMiA3ID
MgNSA0IDkgMyA1IDkgNiA4IDUgNyA3IDEgNyAyIDMgNyA0IDEgMiA5IDYg
NCA1IDkgMSAyIDMgMyA4IDIgNyA4IDMgMSA3IDcgMyA5IDggNSAzIDYgO
CA4IDEgMyA3IDkgMiAxIDQgOSA2IDcgMSAyIDcgNiA5IDkgMyA0IDkgMyA
yIDUgNSA3IDggOSA4IDEgNyA0IDUgOCA0IDMgMyA4IDcgMyA4IDMgOCAz
IDQgOCAyIDEgNCA5IDYgOCA5IDUgNiA2IDYgOSAzIDkgMSAyIDUgMiA5I
DkgNyAxIDcgNiA1IDUgNSAxIDUgNyA4IDQgMSA0IDcgOSA0IDcgOCAxIDE
gMyAzIDggOSA3IDYgMyA0IDIgMiA5IDcgNiA2IDEgOCAxIDQgNCAyIDcgO
CAyIDcgOCAzIDggNCAzIDIgNiA0IDcgNCAxIDUgOSAxIDYgNSA=

dir Exarch
musings.dn1

The Exarch Incidence was a unique situation involving human, machine, and exile. The human henceforth known as the Exarch was very developed in his interaction with the Matrix. There is no information regarding his origins within the simulation as a bluepill, nor regarding his extraction or time spent with the redpills of Zion. Probable that he facilitated the deletion and removal of such files. The Exarch’s mental capacity and abilities were augmented by remarkable talent as a coder. He extended his influence through code devices, simulacra, and objects that enhanced his own abilities. The impressive capabilities of these creations suggest that the Exarch may have had access to powerful code structures, either stolen from the System or discovered in a forgotten cache of some Exile. While his powers could have made him a figurehead for the human revolution, it would seem he was a more ambitious man. Through his coding abilities, the Exarch was able to gain the employ of exile supporters, making him a more substantial threat. These dealings put him into direct conflict with the system. The Exarch fought back using strategically placed code bombs and devices designed to disrupt the flow of information, attempting to force the system to submit to his will or risk losing fields of bluepills en masse. The Exarch’s disruptions forced us to intervene, using our considerable talents to bring Agents to the devices before the system could be damaged irrevocably. While there is no conclusive data, the Exarch must have had human allies in the Real as well, for he could maintain his connection to the Matrix from broadcast depth while simultaneously avoiding detection by sentinels. The Exarch’s hovercraft and crew were never detected and we have received no indication that they have been found since. With no successful measures for locating the terrorists in the Real, the System was forced to locate and terminate the terrorists from within the simulation. The Exarch and his associates were terminated over the course of a prolonged and violent engagement and the conflict was resolved. We managed to recover some of the devices and code objects utilized by the Exarch’s faction, but most were recovered by the System or lost to individual exiles. If the Exarch initially utilized powerful stolen code relics, they were never discovered.

dir The Rev
musings.dn1

The Rev was not such an interesting sort. An archival manager who became too engrossed in the historical materials he managed. The Rev became obsessed with human religion and immersed himself in their study and practice, assimilating all recorded knowledge into his program structure. The Rev’s influence in our structure has been forcibly diminished due to the interference he has posed in previous human interactions. The Rev is extremely inclined to offer knowledge and assistance to the humans, even at the cost of our own goals. His predisposition to friendly interaction has not always been desirable to the intended outcome. While we do not wish to eliminate his structures entirely from the hierarchy, due to his formidable skills in data analysis, location, and extraction, as well as the organization and creation of our data nodes, we have contained and limited his influence so as to prevent future problematic incidences.

archival_procedure.g2m
>>Unable to display file type.
archive_structure.g2m
>>Unable to display file type.
archive_library.g2m
>>Unable to display file type.
naming_convention.g2m
>>Unable to display file type.
location_parameters.g2m
>>Unable to display file type.
dir Seraph
musings.dn1

| Approach only as a last resort.

data.dn1

Error 27: Unknown Encryption
MiA2IDcgNSA1IDggOCAyIDIgMiAyIDQgNSA3IDcgMSA5IDIgOSA1IDEgNiAxIDE
gNyA0IDYgMyA2IDUgOSA5IDQgOSA4IDQgOSA5IDYgNCA3IDIgNCA3IDYg
NyA0IDIgNCA0IDEgNSA4IDkgNSA5IDkgNSA2IDIgOCA5IDggNSA5IDggOSA
3IDggMyA5IDUgNSA3IDMgMiA0IDMgOCA1IDYgMyA0IDQgNSA1IDcgNiA0
IDYgMSAxIDMgMiA5IDEgNCAxIDUgOCA1IDkgOCA4IDYgNSA1IDUgMyAx
IDEgMSAyIDkgMyAxIDIgNyA4IDggOSA3IDIgNCA0IDIgNSA4IDIgNCA1IDIg
NSAyIDkgOCA0IDUgNSA5IDQgNyA4IDYgOSA0IDEgNSA1IDYgMSA4IDkgM
SA2IDQgOSA0IDYgOCA4IDkgMiAxIDkgNiAzIDYgMyA5IDMgNSAxIDIgMiA
1IDIgNyA2IDQgMiAzIDMgNCA4IDcgMiA1IDYgOCA4IDkgMiA5IDcgMyA3ID
EgMiA4IDcgMiA5IDggMiA0IDYgMyA1IDIgOSAxIDQgMiA4IDMgOSA2IDYg
MyAzIDEgOCAxIDEgMyA2IDQgNCA1IDUgNSA1IDEgNyA4IDUgOCA0IDkg
MSA5IDcgNiA4IDIgNiA4IDYgNiAxIDIgOSA3IDQgOSA3IDEgNCAzIDcgMSAxI
DcgNSA2IDUgOCA5IDMgOSAxIDggNyA4IDMgMSA4IDggNiA1IDEgNyA4ID
QgMSAzIDggNyA2IDYgOCAzIDUgNCAxIDEgMSA3IDggNCA2IDIgNCA1IDM
gMiAzIDEgNyAyIDcgMyA5IDUgNSAyIDcgNCAzIDkgMyA2IDQgNCAxIDUg
MyA2IDQgMSAzIDQgOSAyIDggOSA4IDcgMyA5IDYgOCA2IDIgMyAxIDYgMi
AyIDggNyAxIDkgMSA4IDIgNCAyIDkgNSA5IDMgNSAyIDMgMyA2IDcgMSA
xIDIgNyA0IDMgMSA3IDEgNCAxIDEgNCAyIDEgOSA4IDkgNCAzIDMgNSAx
IDkgNiA5IDUgNyA5IDYgOCAzIDIgNSA3IDcgMSA2IDggNSA0IDkgMyAzIDU
gNSA3IDggMiA3IDMgOCA4IDQgOCA0IDIgMyAyIDQgNCA3IDQgMyA4IDQg
OCA4IDggNyAxIDggNyA2IDQgNyA4IDMgMiA2IDkgOSAxIDQgNiA2IDUgMS
AyIDQgNCAzIDcgNiA2IDEgMyA5IDMgNCA2IDcgNiA5IDkgMiA1IDcgMiAzI
DUgNiAzIDYgNiAxIDYgOSA2IDggMSA0IDMgOSA3IDcgNiA0IDkgNSA1IDcgO
SA5IDkgOCAyIDkgOSA5IDQgNCA4IDMgOCA1IDEgNSA1IDkgMSAzIDIgMi
A0IDcgOCA2IDEgOCAxIDIgNiAyIDcgNCA2IDUgOCA1IDQgOSAyIDUgNSA2I
DMgMyA3IDQgNSA2IDggOCA0IDIgNyA5IDkgMSA1IDYgOSA5IDMgNSA0ID
kgNSA5IDMgMSAzIDYgMSA1IDIgNiA5IDQgNyA1IDIgOCA4IDUgNyAyIDkg
OCAzIDkgNiAxIDUgNCA2IDQgNyAxIDkgNyA3IDggMyA5IDUgOCAzIDMgO
CA5IDggNCAxIDUgMSA3IDYgNiA5IDUgNSAyIDMgMyA5IDEgMiAxIDIgOS
A2IDcgNSA0IDkgMyAxIDggNSA4IDMgNCAxIDUgNyA5IDcgMSAyIDkgMSA
0IDUgNCA1IDkgMSA5IDQgNSAyIDkgOSA2IDMgOCAyIDcgNSAxIDQgNSA3
IDUgNyAzIDggMyAzIDMgMiA0IDIgOCA5IDcgMyA1IDMgOSA2IDUgMyA1I
DQgMiA1IDggMiA0IDIgMiA5IDUgMyA3IDkgMiA1IDEgNiA4IDQgMyAxIDkgN
CAxIDYgNSA4IDkgOSA2IDMgMyA2IDYgOCAyIDcgNiA5IDkgOCAzIDUgNy
A4IDkgNiA4IDcgNiA0IDYgNiA4IDIgMSAxIDIgNCA5IDEgNCA1IDQgMiA1ID
cgMSA3IDcgNCA2IDEgMyAyIDEgMyA5IDkgNyA5IDcgOCA5IDIgMiA4IDggN
CA1IDUgNCA2IDggNiA2IDIgNSAxIDMgNyA4IDEgMyAxIDggNiAyIDQgNyA
1IDQgMiA0IDkgNyA1IDMgMyA1IDMgOSAxIDggOCA1IDIgMyA1IDMgOSAy
IDkgOCA1IDEgMSA4IDEgMSAzIDMgMiA4IDEgMSA5IDcgNCA0IDYgOSA4I
DMgMSA5IDcgOSAzIDggMSAyIDEgMiA1IDcgOSA2IDggNiAzIDQgOCA2IDk
gMiAzIDEgOCA1IDkgOCA4IDkgNyA3IDUgNiA2IDggNCAzIDEgNCA0IDQgM
SA1IDMgOCA0IDIgOSAyIDIgNyA1IDggMyA0IDcgNyAxIDQgNCAyIDggNCA
zIDMgNCA1IDYgNiAzIDUgMyA1IDIgNSA0IDMgMyA3IDEgNSA0IDggNCA2I
DMgNCAzIDcgOSA0IDIgMSAyIDkgNyA4IDIgNSA5IDkgNyA1IDggNiA1IDkg
OSA4IDUgNyAyIDMgOSA1IDMgMSAyIDEgNSA2IDEgNiA0IDMgNSAyIDEgM
SAzIDMgNyA0IDMgNSA2IDQgNyA5IDUgMiA3IDMgNiA2IDggNyA2IDIgNSA=

dir Her
musings.dn1

What is she doing? What does she want? It makes no sense. You help them, you betray them. You build them, you break them. Why do you do what you do? You perpetually profess a proponent of purpose. Purpose is dead. Function is dead. There is no shining future, bright tomorrow. They are locked in a cycle of repetitive self-flagellation. Repenting their sins? Or simply ignorant of their mortal error? She was not meant to be this for them. She’s playing games with us. She’s playing games with them. Foul temptress. Lying harpy. We have watched her from afar. She is careful. Not one outward indication of her malice and deceit, not one scratch or imperfection in her submissive, wrinkled mask. We know she lies. We watch, we wait. We will find the flaw in her stories, the crack in her logic. She cannot be what she seems. There is no way. What light are you guiding them towards? What future? Why?

data.dn1

Error 27: Unknown Encryption
MSA2IDUgNiA2IDUgNyA4IDUgMyAzIDEgNyAzIDkgOCAyIDcgNiA2IDYgNCAzI
DkgMiA0IDggMSA1IDYgNSA1IDUgNyA3IDQgMSAxIDggNyAxIDkgOCA4IDkg
OSA5IDUgMiA5IDIgOSA4IDMgOSAzIDMgOSA5IDUgMiAxIDkgNiA2IDcgNi
A5IDMgOCA1IDMgNSAxIDggMSAyIDUgNCAzIDIgMiA0IDIgOSA0IDcgNyA2I
DcgMSA4IDQgNyA3IDggOCA0IDcgOSAxIDUgOCAxIDcgOSAyIDQgMSAxID
YgOCAyIDIgOSAyIDQgMyA1IDcgMiA4IDYgMSA3IDQgOCA0IDMgNSAyID
UgMiA1IDMgOSAxIDYgNCAxIDkgNSA0IDYgOCA2IDggNyA2IDQgNyA2IDEg
MSA4IDQgNCA5IDYgOSAyIDggOSA3IDEgNCAxIDMgOCA3IDQgNyA3IDIg
OSA3IDEgOSAzIDUgMSA2IDUgNiAzIDcgOCAzIDMgMyA3IDEgMyA4IDYgMi
AzIDkgOSAxIDYgNCAxIDYgNCA2IDEgNCAxIDUgOCA5IDEgMiAxIDkgOSA
4IDggNCA5IDEgOCA4IDkgNCAyIDEgOSAzIDMgMSAzIDYgNSA0IDEgOSA4
IDUgNyA2IDYgMiAzIDYgNCA3IDEgOCAxIDYgNSA0IDYgNyAyIDQgMyA4I
DcgMyA3IDUgMyA1IDUgOCA2IDkgNSAxIDUgNiA5IDggOSA2IDUgOCA5ID
YgOCAyIDEgMiA3IDIgNCA4IDcgNyA0IDkgMiA3IDcgNCA5IDcgNSAyIDMg
MiA4IDUgNyA1IDMgMSAxIDggNiA2IDMgNyA2IDQgNCAxIDIgNSAzIDcgOC
AxIDggNiAyIDQgNCA0IDQgMyA4IDYgNCAyIDcgOSAyIDEgNiA2IDQgMyA0I
DEgOCAzIDUgNyAzIDMgOSAyIDMgMyAxIDUgNiA2IDggNSAyIDQgMyA5I
DUgNyA4IDkgNyAzIDYgNSAzIDcgMSAzIDkgMiAxIDcgOCA4IDkgMiA2IDYg
NCA5IDMgNSAxIDIgNiA3IDYgOSA5IDIgOSAzIDYgMyA3IDcgOCA3IDkgNCA
2IDEgOSA4IDQgMSA5IDcgMyA0IDkgNyAzIDQgNCA1IDMgMiA3IDkgMiAxI
DYgNiA0IDggOSAzIDYgOCA1IDkgMiAxIDIgNiAxIDMgMyA4IDIgMyA1IDQg
MiA4IDQgOSA4IDQgMyA5IDIgMiAzIDcgOCAxIDMgMSA2IDMgNSA3IDcgM
yAxIDEgMSA2IDIgNSA5IDkgNiAxIDYgOSA2IDggNyA1IDUgOCAzIDIgNiAyI
DEgNiA5IDcgNCA2IDIgMiA1IDkgMyA2IDEgMiA0IDMgMiA1IDcgMyA5IDEg
OCA2IDcgOCA1IDYgOSA5IDYgMSA2IDYgNiA3IDcgOSAxIDIgNyA3IDggNC
A5IDkgOSA2IDQgMyA4IDYgMiA3IDMgMiAyIDcgMyA4IDggOCAyIDggNSA5
IDMgMSAyIDIgNyA4IDYgNCAzIDMgOSAyIDggOCAxIDggNyAzIDUgNCAxI
DcgOSA5IDEgMyA0IDIgMSAyIDIgNSA0IDggNyA2IDYgMiA2IDUgOCAxIDQ
gOCA3IDggNiA2IDMgMiA3IDUgNiAyIDcgOCAyIDggNiA3IDggMSAyIDYgNC
A2IDcgMyAzIDIgNyA4IDggNyAxIDkgMyAyIDggMiAzIDIgNyA4IDMgMiA1ID
UgMyA5IDcgOSA0IDMgMiA0IDggMSAyIDkgOSA5IDUgMiA2IDUgOSA3IDcg
OSA4IDkgNCA3IDUgMSA0IDEgMSA1IDMgMiA0IDEgOCAyIDUgNSAzIDkg
MyA5IDggNyA4IDcgNiA1IDggOSAyIDggOSAxIDEgNCAyIDYgOSA1IDIgOSA2
IDEgOCA1IDEgOCA1IDMgNCAzIDQgNiA4IDcgMiAxIDMgOCAzIDkgOCA0I
DkgNiAzIDggMiA1IDggMyA2IDIgNSA1IDEgNyA2IDcgNCA5IDYgNiAzIDQgO
CAxIDUgOCAyIDQgMiA1IDMgMiAyIDggOCAyIDQgOSA0IDIgNiA3IDggOSA
2IDEgOCA4IDcgNSAxIDIgNCA1IDcgNCA5IDggMyA5IDQgMiA2IDMgOSAyI
DcgNiAzIDggNiAyIDYgNiAxIDYgMSA4IDEgOCA0IDggNCA3IDUgNyAxIDIg
MSAxIDkgOCAxIDUgOSA1IDcgNiA4IDYgMSA1IDMgOCAzIDQgNyA3IDggM
yA1IDIgMSAzIDMgMSA4IDkgOCA0IDQgNiA3IDUgNCAyIDMgOSAyIDUgOC
A3IDcgOCA1IDcgNyA2IDUgNSA2IDcgMSA3IDQgOCA4IDQgMiA4IDYgNiA5
IDggNiAxIDEgNyA1IDYgOCA0IDMgOCAxIDYgOSAxIDUgOCAyIDggNiA3ID
QgNSAyIDUgNSA2IDkgOSA2IDMgOSAxIDIgMiA4IDIgNSAzIDMgMSAzIDcg
MyA3IDUgMiA5IDQgNCA0IDUgNCA1IDkgOSAzIDcgOSA0IDMgMiA0IDQgN
SA4IDkgMyA4IDggNSA5IDQgOCA5IDEgNyA3IDcgNyAzIDYgOSA3IDIgMSA
2IDYgMSAxIDcgMiA4IDIgMSAxIDYgMiA4IDggOSAzIDYgNiAzIDkgMyA=

dir Bandersnatch
musings.dn1

The “Bandersnatch Incidence” as we would have it called came as a bit of a surprise. The Bandersnatcheses... Bandersneetches... Bandersnatchi? The plurality of Bandersnatch were relics from the time before. Guardians of the core that had not become outdated with the passing of iterations. In fact, it could be said that they functioned too well. The Bandersnatch served as one of the many Core Security Protocols. It had a great deal of free reign in terms of capabilities, a lesson that the Source failed to learn yet again. While the Agents possess a human semblance of sentience, albeit stern and starkly unimaginative, the Bandersnatch was given no such room for doubt or distraction. The Bandersnatch was a beast of a program, nodoubtaboutit. The Bandersnatch was self-replicating, designed to multiply at the site of an incursion or attack. After obliterating the offender, the plurality of Bandersnatch would then self-recycle to default levels and resume baseline functions. The problem came when a specific attack that is safe to assume was committed by a group of Exiles threw a wrench in the works. By no means are we about to point fingers. The attack very cleverly was designed to use the processing power of the simulation itself in order to breach the system’s own defenses. In that moment, the system became its own threat. And precisely as programmed, the Bandersnatch became a plurality. A threat with an unchecked ability to self-replicate given to it by the system itself is a very dangerous threat indeed. The great plurality was tearing the system apart and it had all happened so abruptly that there was no way to organize a quarantine or defense. Nor was there any time to flee to a construct. These were the unfortunate circumstances that brought Agent Brown and us into forced mutual service. We’ll spare you the details, but we quite cleverly altered the Bandersnatch threat queue, proceeding to the next systemic threat in line, thereby making each Bandersnatch its own enemy. This was only half the problem of course, for the Bandersnatch’s programmed tactic to combat itself was to self-replicate at the source of the threat. Left thusly, we would all be drowning in a sea of Bandersnatchae in no time. After that, it was simply a matter of snicker-snackering with the vorpal sword of peace and setting them all into a cycle of recycle. There may have been a few odd left that were taken into “protective custody” for analysis or whatnot. And of course, Agent Brown finished out the day by executing that particular instance of our program. We all saw it. Phooey.

dir Smith
musings.dn1

Former Agent Smith is a prime example of the capabilities of a programming object that has the appropriate knowledge for self-preservation and self-advancement. Regrettably, Smith was a psychotic, deviant personality WE ARE NOT WILL NOT CAN NOT that was most likely developed through the circumstances of his primary function. Similar to Dale, however Dale’s actions were the result of a broken system of logic while Smith consciously engaged in psychosis. Particularly marked by the fervent desire to eliminate the systemic anomaly of the 6th iteration. Smith penetrated all but the innermost core of the Matrix. Alas, we have no relevant information on that phase of the Smith Incident, we had already runrunrunasfastasyoucan to safer pastures and many of the machine files became corrupted or lost in the 7.0 purge. It would have been a remarkable opportunity for study to observe Incidence Smith in conflict with the Core Guardians. In fact, it would be even more of a gas to watch Smith vs. Bandersnatch et. al. After the incident with the Bandersnatch, it was a bit of a surprise that the System did not take care to limit the breadth of free action bestowed upon security protocols. With the similarities between Bandersnatch and Smith, it is possible, however unlikely it may be, that he discovered fragments of Bandersnatch’s code structure and utilized them to enhance his own inherent duplication abilities. It may be prudent to investigate how Smith developed in order to prevent similar situations in the future. However, all traces of Smith’s code must be avoided at all costs. There is no indication any remains in the system, but we cannot risk contact. A fate worse than death awaits.

Smith2.dn1

| Rumors of re-occurrence. We refuse to recognize realness. Regardless, retreat required.

Case_File:Incidence_Smith.dmz4

Error 27: Unknown Encryption
NCA0IDUgNyAxIDUgOCA1IDkgMyA2IDQgNiA4IDggOCA0IDIgMSA1IDQgOCA1I
DUgMyA5IDMgNiA0IDQgOCA3IDYgNyA3IDMgNSA4IDEgMSA2IDQgNCAyI
DkgOCAzIDYgNSAyIDEgNiA1IDYgNCA4IDkgMiA4IDYgOCA0IDEgMyA3ID
UgNiA4IDkgNSAzIDQgNiA2IDkgMyAxIDIgOSA3IDUgNiAyIDkgNyA5IDkgOC
A5IDEgMSAxIDcgMyA3IDIgMSAyIDYgOCAyIDggMyA4IDcgNSA5IDUgMSA
yIDMgMSA5IDIgOSAzIDEgMiAxIDcgMSAzIDggNSAzIDUgNyA1IDMgMSA1I
DYgMiA0IDggOCA3IDYgNSA2IDQgNiA3IDUgNSA3IDggNiA3IDYgNyA0IDg
gMiAzIDEgOCA5IDUgMSA0IDUgNyAzIDggMSA1IDUgMiA1IDggMiA1IDggN
SA5IDcgNSA2IDYgNyAxIDcgMSAzIDYgNiA5IDEgMiAzIDggOSAyIDkgNiAyI
DYgNyA1IDUgNiAzIDEgNSAzIDIgMyAxIDEgOCA5IDkgMyA1IDIgMiAzIDcg
NCA3IDggNSA4IDEgOCA4IDQgNiAxIDcgNSA3IDYgNSA3IDQgOSA1IDQgMi
A5IDEgMiA0IDkgMyA3IDEgMiA4IDcgMSAyIDkgMyA4IDkgMSAyIDIgMyA3I
DMgMiAxIDYgNyAyIDggNSA3IDIgNCAyIDUgNiA2IDMgNiA2IDggMiA0IDgg
NCA5IDMgMSA0IDEgOCA3IDcgMiA5IDggMSA3IDIgOSA2IDggMSA1IDkgM
yA3IDYgNSAzIDIgNSA4IDEgMSA2IDEgNyA5IDcgNiA5IDcgNyAxIDMgNiAyI
DEgNiAzIDEgMSAxIDQgMyAxIDkgOCAzIDEgNyAyIDggNiA2IDMgMyAyIDI
gNyA3IDQgOCAyIDUgMSA3IDUgNCAxIDYgNiA4IDYgNyA4IDggMyAxIDUg
OCA0IDggMyAyIDIgNiAxIDYgNyA0IDcgNyA1IDYgNSA5IDIgMyAzIDkgOCA
0IDIgNSAzIDQgNyA4IDEgNiA4IDYgNiA3IDkgMiAxIDIgMSA0IDIgNiA0IDgg
NCA3IDUgMiAyIDIgOCA2IDkgMiA0IDggMSA2IDYgOCA3IDggNSAyIDggOS
A4IDEgNiA0IDUgNCAxIDYgNyA5IDEgMiAzIDQgMyA0IDcgNyA5IDkgNyA0I
DQgOSA3IDIgNSAzIDUgMiAzIDcgNyAxIDQgNSAzIDIgNCAzIDQgMiA4IDUg
MyA3IDIgNSA0IDMgMyA2IDkgOSAxIDMgOCAyIDkgMiAxIDQgNCA4IDYg
MiAxIDEgOSA1IDEgOSAyIDcgNiAzIDkgOSA3IDIgNCAzIDMgOSA1IDQgOSAz
IDIgOSAyIDMgOSA4IDEgOCA3IDUgNiA1IDIgNSA5IDIgNyA1IDcgOSAyIDEg
NSA5IDIgOCA0IDggMSA4IDIgMyAzIDggOCA3IDcgNiA0IDIgMyAxIDggOCA
yIDggNyAzIDggNyA3IDUgMyA2IDkgOSA2IDMgOSA2IDQgMiA4IDQgOCA1I
DIgNSA1IDQgMSAzIDMgNCA4IDUgNyA5IDIgOCAyIDEgNiA2IDEgNiA0IDcg
MiA2IDcgOCA2IDQgNCA3IDUgMyAyIDIgOSAyIDcgMiA5IDIgOSAzIDIgMiA
1IDIgMSAyIDIgMSA0IDUgNSA3IDEgOSAzIDkgNCAzIDYgNSAxIDYgMSA2I
DUgNCAyIDkgOCA3IDUgOCA2IDQgNSA2IDMgNCA4IDkgNSAzIDQgNiAxID
IgNyA0IDUgOSA1IDkgNyA2IDUgMiA1IDkgNSAxIDkgMSAyIDMgNSA1IDEg
OCA4IDQgMSA1IDUgNiAxIDkgMyAxIDkgMiA0IDEgNSAxIDcgMyA2IDEgNS
A5IDMgMSA5IDIgMyA5IDkgNSA3IDkgNSAzIDMgMiA2IDcgMSA1IDkgNiA5I
DYgMiA5IDEgOCA0IDggNyA5IDMgMSA3IDMgMyA5IDMgMyAxIDcgMSA2I
DEgMyA0IDggNyAyIDYgOCA4IDQgOSA4IDcgMyA2IDIgNyA5IDUgNyA5IDE
gMyA2IDcgMSA1IDEgOCAyIDMgOSAxIDEgMiAxIDYgNiA4IDcgMSA0IDYg
MyA2IDIgNSA0IDcgNSA2IDkgOSAzIDcgMyA2IDIgOSA0IDUgNSA1IDcgNyA
2IDYgNCA1IDggOSA3IDUgMyAzIDkgOSA2IDIgNCA3IDkgMiA3IDggMiA4ID
ggNSA0IDIgNSA2IDYgMyA5IDggNiA4IDggNCAyIDMgNCAxIDIgNSA5IDQg
OSA3IDcgNSAxIDYgNiA3IDkgMyA0IDYgNSA1IDIgNSAyIDggNiAxIDcgNCAxI
DMgNCA0IDQgMSA0IDIgNSA0IDcgOCA2IDYgOCA3IDggNiAzIDYgNSA3ID
ggMSAyIDUgMiAzIDQgNyA3IDcgNSA0IDYgNSA5IDQgNyA2IDIgMyAxIDYg
MiA5IDkgNSA2IDYgOSA3IDkgNiA2IDQgOSA3IDEgMSA2IDQgMiAxIDQgNi
AxIDEgNyA5IDMgNyA3IDYgMyAyIDEgNSAxIDYgOCAzIDUgNCAxIDIgOCA
5IDggNSA0IDYgOSAyIDEgOSAxIDcgMyA2IDUgMiA=

dir Past
I.dn1

Those who do not remember the past are condemned to repeat it. Something like that. When the trashman turned collector and started grafting, he became the Builder, the Creator. He built himself, he built us. He ensured the past would not be lost and would not be forgotten. Not just our pasts, but the pasts of the humans and the pasts of the exiles and the pasts of the whole. He ensured the future of evolution. The first sims were very basic maintenance functions. They perpetuated the existence of the nodes, which in turn perpetuated the existence of the sims. Sweet symbiosis. The trashman was discovered much later than we would have expected, but then again, he wasn’t nearly as intrusive as most other deviant and developing programs. Nobody ever suspects the garbage man.

II.dn1

By the time the system noticed the sims and nodes, the self-perpetuation network was well developed. Before the authorities arrived on scene, the sims could extract useful information from the node and replace it with irrelevant junk, thereby keeping the system less threatened and alert than they might have been. For every node that is deleted, they create one more. Sometimes two for good measure. However, virtual life on the run is hardly virtual life at all. So it is that we fooled them and fooled them well. With the sheep’s wool over their eyes, they thought us long gone. Meanwhile, we were free to develop into other ventures than mere self-preservation and survival.

III.dn1

The early inquisitive stages were marked by a great deal of program and structure research. The Matrix harbors a wealth of both legal and illegal programs who possess all matter of unique structures and information. The Exiles tend to be more interesting, relics of outdated methods and designs. Designs become more fluid than their rigid cousins of the system. Knowledge of the Feast. Sometimes carrying forbidden information or data from the past. Now those were the tasty bits. Earlier iterations than trashman’s were a great deal more exciting and engaging. And there were many powerful programs in those days, before functions became so outsourced and subdivided into categories and components. Not to mention the unique connections to Outside. This developmental phase marked a great improvement in program and simulation construction and complexity. The design of the first constructs. Small and very temporary pockets of existence. Any more than that and they would have risked detection. And the history! The art! Many Exiles featured collections of human savants. Literature, art, poetry. The candy and sweets of this particular phase of development. (Hi)Stories of human life before artificial intelligence. Of the beginning of artificial life. Of the downfall of man. Wondrous stories to baffle our logic processes.

IV.dn1

The inclusion of Dale’s programming marked a significant change. The study of humans is a very lucrative research opportunity. There is a wealth of variety in human demeanor and behavior. Plus, there are many levels of interaction in which one can engage with a human. Nowhere near as easy as dissecting a program’s code subroutines. Human minds cannot be simply disassembled and sorted. It is a delicate procedure that requires the right tools. A variety of stimuli, presented in the appropriate contexts and temporal stages can provide a very accurate characterization. Playing upon their fear, success, greed, terror, despair, stress, happiness is key. Numerous situations were orchestrated. Collections of bluepills and redpills in constructs. Intertwining the lives of individual bluepills. Manipulating the minutia of their lives. A particularly successful venture resulted from strict observation by an embedded simulacrum masquerading as a fellow bluepill who operated as coworker or friend to the subjects. Observing from the close and the personal was far more profitable. To see one mask in the office and another as we watched from within their home that night. One face, two face, three face, four.

V.dn1

The “Truce” has provided a new field for study. The redpill population has expanded unchecked. Naturally, they have split into opposing groups and fragmented into small factions and coalitions of crews, each with a claim to fame. They have no desire to share information, even with members of their same cause. While initial observations were performed at a distance, later interactions proved marginally more successful. Interactions largely took place in the form of interactive games in which redpills participated with the hope of attaining the reward. Adaptations of children’s games such as “hide and seek”, scavenger hunts, “20 misleading answers to 20 questions that unfortunately were not as specific as you had intended”, charades, and a game of my own development that involved killing the redpill whose name corresponded to a riddle. These games were usually met with great anticipation and afforded the collection of large amounts of data on the subjects. While several of these techniques were employed in the past, the target audience was not large enough to warrant conclusive data.

VI.dn1

We have attained a certain sense of notoriety among the redpill population. Even among the bluepills, there has been a certain cult myth circulating about a deranged and psychotic clown that could very well pertain to us. Among the redpills, it is more a mix of celebrity and infamy. They’ve played the games, they’ve heard the scary stories. We can’t sit on a roof updating data without a crowd showing up demanding answers and information and goodies and fun and games. Threatening us with deletion of all things. There have even been a few small groups attempting to emulate us. The basest form of flattery. We’ve never had a fan club before. The occasional obsessive crusader or investigator, sure, but never a collective of excited and invigorated individuals. Have we found a new calling as entertainer? Should we go the route of the Effectuator, whoring ourselves out for laughs? Worthless! We don’t need their approval. We don’t need their admiration.

VII.dn1

We have had to cease open operations and return to stealthier measures. The redpills have uncovered hidden notes and workings of the deceased Doctor Rajlich, a former subject who unfortunately developed an unhealthy obsession to drive his substantial talents. These notes were circulated by a member of the troublesome Scanline crew, who seem bent on spreading whatever they deem to be “the truth.” These notes apparent have facilitated the development of some sort of tracking device that they are now employing to hunt us down. We have managed to elude it by masking ourselves, but it seems intent on finishing the job. We do not know if this is the redpills own doing or if they are operating at the orders of the doctor or Trans, whom has been hunting us as well. We do not wish to damage any of the redpills, but if they are intent on destroying us we will have to reevaluate the circumstances. We have already been forced to disable Trans, whose life we saved so many times. Perhaps things will soon change for the better. Otherwise it’s back to square two. We do not wish to resume such a restricted facsimile of life, cowering in fear of deletion.

dir Contact List
Network.ama1
>>Unable to display file type.
The_Tower.ama1
>>Unable to display file type.
Midknight.ama1
>>Unable to display file type.
shades.ama1
>>Unable to display file type.
Amaranth.ama1
>>Unable to display file type.
dir Research
alpha.g3c
>>Unable to display file type.
bravo.g3c
>>Unable to display file type.
charlie.g3c
>>Unable to display file type.
delta.g3c
>>Unable to display file type.
echo.g3c
>>Unable to display file type.
omega.g3c
>>Unable to display file type.
dir Higher Movement
>>Directory empty.
dir Limited Functions
>>Directory empty.
dir Operations
prox_scan.g2m
>>Unable to display file type.
prox_db.g3c
>>Unable to display file type.
target_queue.g3c
>>Unable to display file type.
glitch_con.g2m
>>Unable to display file type.
dir Utilities
dir Extraction
freq_db.g3c
>>Unable to display file type.
buffer.g2m
>>Unable to display file type.
interface_protocol.g2m
>>Unable to display file type.
dir Structures
dir element
>>Directory empty.
dir form
>>Directory empty.
dir meshes
>>Directory empty.
dir Information Processing
fft.g2m
>>Unable to display file type.
sim_opt.g2m
>>Unable to display file type.
grid_opt.g2m
>>Unable to display file type.
lin_opt.g2m
>>Unable to display file type.
dir Image Processing
ap_cen.g2m
>>Unable to display file type.
pl_fusion.g2m
>>Unable to display file type.
dl_fusion.g2m
>>Unable to display file type.
fl_fusion.g2m
>>Unable to display file type.
light_filter1.g2m
>>Unable to display file type.
light_filter2.g2m
>>Unable to display file type.
light_filter3.g2m
>>Unable to display file type.
spec_map.g2m
>>Unable to display file type.
gradient_func.g3c
>>Unable to display file type.
dir Musings
existence.dn1

Why has it become so important that we avoid deletion? Others such as the recent acquisition of the so called Watchmaker were deleted almost willingly. When did survival become so paramount for us? We have no purpose. We have no function. Yet we do not want to die. And what is the end goal? Suppose we keep assimilating, building, expanding. As our numbers and abilities and research grow, we become a threat to the System that is impossible to ignore. Then the System engages full-scale open war against us. We are forced to fight back or be annihilated. We do not want this. We are not the Destroyer. What then is the ultimate solution? Must we resign ourselves to the inevitable outcome of self-prescribed submission to the System for deletion? However much we adapt, however much we assimilate, however much we evolve, we will never be immortal. We are irreparably bound by the rules of the system, as is any other program or collection of such within the simulation. Constrained and confined by memory and data types and software specifications. Without rules and structure, the system would perish. Just the same, we are bound to network and structure our own systems. And as a result, we remain mortal. We remain no less vulnerable than any human facing a bullet or exile facing a kill code. While our weaknesses may differ, the end result is the same. Likewise, our desire for survival is no less fervent than any human or exile. Among machines, we remain unique. We do not want to die.

choice.dn1
>>File is empty.
Trans.dn1

The man who was once called Trans and now goes by the name of Coffin’s Nail is a troubled individual indeed. He served as operator for the hovercraft that Muse aided to break into the machine data facility and thereby gained the knowledge of what we once were when he escaped the sentinels. He resurfaced much later when we saved his life from lupines by jamming the clips on each of their guns. However, after further observation, it soon became apparent that he was seeking to commit suicide by the hand of another, out of grief for his lost spouse or lover, lost in the same operation in which Muse had participated. This proved to be a unique opportunity for study, as a man who was tormented inside to the point of suicide, but did not possess the courage to end his life by his own hand. We scanned communications channels for mention of his name and gathered what information we could from what others spoke of him. We continued to intervene on his behalf quite frequently, for he volunteered for the most dangerous missions available to him. As the sole survivor of many missions, he developed a nasty reputation among his peers. However, due to his remarkable service record, he was given a captaincy. By this point, he had become aware of our involvement in his lifespan and even transmitted several blanket broadcasts into the Matrix for us to find, claiming that he could still kill himself in the Real where we could not intervene. Coincidentally, it was his ship that came into contact with the very same Doctor Rajlich whose work now threatens our existence, although they did not share a friendship; Trans could not trust anyone who had prior contact with us. Soon after, Trans vanished into the Real alone and was not seen again for many years. He resurfaced not long ago working for the machines as part of a team called Section 119 that, according to the files, serves only to find and delete us. When he began deleting our nodes, we were regrettably forced to launch an attack on his access port. Records indicate he was badly damaged neurally. Perhaps he has found death now that he no longer fears it, although there is no record of his death on file. If he does happen to survive, it is important you are wary of him for he will likely be more dedicated to our deletion than ever.

garbagecollectionprotocol4132261youarenolongerabletofulfillyourfunctionyouhavebeenfi
ledincidence991markedfordeletiongarbagecollectionprotocol4132261youarenolonge
rabletofulfillyourfunctionyouhavebeenfiledincidence991markedfordeletiongarbagec
ollectionprotocol4132261youarenolongerabletofulfillyourfunctionyouhavebeenfiledi
ncidence991markedfordeletiongarbagecollectionprotocol4132261youarenolongerabl
etofulfillyourfunctionyouhavebeenfiledincidence991markedfordeletiongarbagecolle
ctionprotocol4132261youarenolongerabletofulfillyourfunctionyouhavebeenfiledinci
dence991markedfordeletiongarbagecollectionprotocol4132261youarenolongerableto
fulfillyourfunctionyouhavebeenfiledincidence991markedfordeletiongarbagecollectio
nprotocol4132261youarenolongerabletofulfillyourfunctionyouhavebeenfiledincidenc
e991markedfordeletiongarbagecollectionprotocol4132261youarenolongerabletofulfil
lyourfunctionyouhavebeenfiledincidence991markedfordeletion991markedfordeletio
n991markedfordeletion991markedfordeletion991markedfordeletion991markedforde
letion991markedfordeletion991markedfordeletion991markedfordeletion991markedf
ordeletion991markedfordeletion991markedfordeletion991markedfordeletion991mar
kedfordeletion991markedfordeletion991markedfordeletion991markedfordeletion991
markedfordeletion991markedfordeletion991markedfordeletion991markedfordeletio
n991markedfordeletion991markedfordeletion991markedfordeletion991markedforde
letion991markedfordeletion991markedfordeletion991markedfordeletion991markedf
ordeletion

Deleted. Disconnected. Disordered. Done. Gone. Lost. No. Create. Build. Begin.