### -> [[Message]] Getting frustrated with yourself, you decide to turn introspective - maybe a break from the strangeness of your situation would be best. So, this "JE" person hired you on to take a look at these documents. Sure, fine. You don't *know* them, but as far as you're concerned, you could probably call them up if needed. But you don't need to - you know you can take a hint. You look at the various documents. It's probably best to see what's similar between them, right? After all, this is probably a matter of pattern recognition... these papers seem to *reek* of a human quality - whatever narrator they have, seems to hold pretty high regards of this murderer. You have your own opinions, but it's not relevant to the case right now. A realization. Each of these documents seems to be part of an "Act" of sorts. Well, it really should be capitalized, ACT, as it's an acronym - Actualized Continuity Timepiece. You've heard about this as part of your training. As a part of working at Aether Labs, you're in charge of researching anything related to memories. You, specifically, have a degree on Personal Reactions - which is a fancy way of saying you research the Outburst phenomenon, usually. There hasn't been much Outburst going on, strangely, so you've been largely delegated to a "need to know" role. That goes onto the ACT - it's a set of somewhat coherent and related memories. You understand, from the occasional chit-chat with coworkers, that an ACT is like a *folder* for a set of memories, were each memory to be treated like a file. You open your console and test this theory out. ``` --[C:Aether Labs/test]-- mkdir ExampleAct Directory "ExampleAct" created. merge ExampleAct & C:Aether Labs/Employee/Personal/Scratchwork 4 files moved. tree ExampleAct ExampleAct |- ToDo.txt |- NumbersToLetters.txt |- DigitalPenthousing.md |- EmployeeHandbook.pdf ``` So, reasoning about this again, the `ExampleAct` folder acts like a, well, an ACT, and the scratch work that you have on file could be considered like individual memories. You try to recall how to open up, say, your to-do list. You'd have to know the full path to the file - in this case, `C:Aether Labs/test/ExampleAct/ToDo.txt`. Easy enough, you figure. But, what if you're already there, and need to see the "memory" of your employee handbook? That's easy, you figure - just replace the name of the file at the end with the name of another file - er, memory. So, for example, you'd replace the `ToDo.txt` with `EmployeeHandbook.pdf`. You start to think a bit more about your problem at hand, now. If this is truly stored via some form of ACTs, could there not be a simple way to replace something and have it go through?