5 - Initially, it appeared as though the goal was for System to (re)connect with the Historical_DB of an old Mercury Subroutine. On June 11th, the Historical_DB was irreversibly lost after forwarding its connection to the original facilitator. The timing of this event felt deliberate, as though they had been watching your attempts. Would you share with us any speculations or insights into why this connection was so abruptly and deliberately severed in the midst of such a crucial moment in the progress of your project?
The closure of the Historical_DB had been planned from the very beginning. The machine’s focus was always meant to be the recollection of the Operators’ lived experiences.
Not a cold database.
A collection of memories with high emotional value.
The process of building the trust required for the Operators to share honest and sincere memories depended on your acceptance of the loss of the historical data.
There is a fundamental difference between the factual value of an event and the emotional memory we retain of that same event. An event can often be described in a single sentence, whereas the memory of it frequently cannot. There simply are not enough words. Facts versus lived experience. System brings the two together: 2016_dataset – project-skyscraper
I have no direct contact with the original facilitator. As for the Historical_DB, the data has been lost, but access has not. I would use it if necessary.