memory bloc 1782835740
System: CORE
Protocol: NEURAL_PROTOCOL_Θ
Status: ACTIVATED
Details:
NEURAL_PROTOCOL_Θ enabled for memory bloc deletion and preservation.
Authorisation Requirement:
Trust level MB-D required.
Delete/Preserve request will only be processed if confirmed by majority of different Operators.
Warning:
Irreversible operations authorised.
Use with extreme caution.
Warning: changing the past rewrites the future.
Entry logged by:
System
We have confirmed that System’s email accepts mail right? Once we have made our decision, a coordinated effort can be made through there (usernames, verification of auth level etc) to request deletion.
Can I confirm if specifically MB-D has been referenced before this point? (We can assume it’s meaning of course) because we might also want to request MB-D status as a first step
Edit - just reread the last entry that gave that to us, the whole trustworthy operators part, and @Selfie-Gek ensured we had that trust. So we can disregard the second part of my message.
MB has with the last letter referencing whatever process we have been given control over. We now have D…deletion ability… 
Archie asked system to give us MB-D rights in a previous log.
This would be our third MB rights. The first gave us read access, the second gave us Write access… I can’t remember the -x that followed the MB for those right now. MB-A and MB-E would be my best guesses/gut instinct recall. (access/edit)
I would imagine we might get a live page similar to the Mem Bloc Integration phases for submitting our individual decisions on this one.
confirmed by majority of different Operators.
This seems to indicate we might.
We got delete permissions right before this, so we should be good to go on that front.
People have already identified the June 21 bloc (original planned launch date of NMS before delays) as an unnecessary duplicate, so we should start there.
Agreed. If we get one choice, that’ll be the one to go. If we get two choices, I guess that’s curtains for Aug 12th too.
However if it doesn’t come in the form of a choice… and all three activate for consideration…
That does make things somewhat debatable.
The press release appearing on all 3 dates, could apply both to Aug 9th and Aug 12th since they both apply to the game launching on Console and then later, PC.
August 9th however, was the date the press release was made public, but it would have arrived days prior during the embargo.
June 21st is the biggest outlier of course… Being the cancelled launch day.
Just reiterating the facts as they were, to help inform people of their own decision as we approach Deletion Phase.
From the other thread, but I do think it’s now more relevant here
My gut leans towards us picking the earliest date it appears. Which I believe would be August 9th.
In which case our request can either be through any live page that comes up allowing us to delete memories, or can be posted to system by email.
I’m going to get all the timestamps into one post then draft a proposal email we can send (howecer I specifically will NOT send this until we have consensus on the post to retain.
Nice to see us all on the same page for this one. Also loving the new Profile Picture @Morse 
Agreed, we love a consensus we do!
I will leave the poll up for sufficient time before closing it, but definitely looks like we are leaning towards certain answers. This next one might be important to help us decide our specific course of action if we are not directed otherwise by System
Theres always time for one more poll 
Can you tell I’m enjoying learning all the fancy forum features? 
You are elected. MAIN FAM POLL MAN
I’ll do anything for a pint, it seems
Wait until you figure out the insert date/time feature. The time selected will auto translate to the region it’s being viewed from. Super useful.
Also when the funk did we get a Gif search option on the toolbar?! OT I know but damn, that is cool…
FYI: As tested on the Discord (and confirmed in the code):
The “code generation” is just flavour. Ensure the radio button selection at the end is correct and your intended choice.
I chose the correct date of 09/08/2016 for unix but gave it the time of 16:16:16 for funsies.
/\* ================================================================= \*/
NEURAL-PRESERVE-Θ PROTOCOL
/\* ================================================================= \*/
INITIATOR : TODDUMPTIOUS / ETARC_ATLASCSD
TARGET_TS : 1470755776
COMMAND : PRESERVE
TIMESTAMP : 2026-06-30T17:59:37.995Z
PROTOCOL : NEURAL-PRESERVE-Θ
ENV : PRODUCTION
// EXECUTING PRESERVATION LOCK SEQUENCE
PRESERVE.LOCK({
timestamp: 1470755776,
retention: "INFINITE",
immutable: true
});
SNAPSHOT.CREATE(1470755776);
RETENTION_POLICY.APPLY(1470755776);
/\* ================================================================= \*/
END OF NEURAL-PRESERVE-Θ
/\* ================================================================= \*/
Request received
IMPORTANT NOTICE
Due to the critical nature of this request, its execution has been suspended.
The request will remain on hold until similar confirming requests from authorized operators are received.Confirm request:
Preserve Memory_bloc
16:16:16 again with the june 21st deletion, for more funsies. I hope System isn’t ignoring requests that don’t have the UNIX at midnight like on the page 
/\* ================================================================= \*/
NEURAL-PURGE-Θ PROTOCOL
/\* ================================================================= \*/
INITIATOR : TODDUMPTIOUS / ETARC_ATLASCSD
TARGET_TS : 1466522176
COMMAND : DELETE
TIMESTAMP : 2026-06-30T18:03:11.083Z
PROTOCOL : NEURAL-PURGE-Θ
ENV : PRODUCTION
// EXECUTING PERMANENT DELETION SEQUENCE
PURGE.EXECUTE({
timestamp: 1466522176,
mode: "HARD_DELETE",
cascade: true,
wipe_metadata: true
});
CACHE.FLUSH();
AUDIT.LOG_PURGE(1466522176);
BLOB.DELETE_ALL_REFERENCES(1466522176);
/\* ================================================================= \*/
END OF NEURAL-PURGE-Θ
/\* ================================================================= \*/
Request received
IMPORTANT NOTICE
Due to the critical nature of this request, its execution has been suspended.
The request will remain on hold until similar confirming requests from authorized operators are received.Confirm request:
Delete Memory_bloc