📝 Contact Coordination - Emails To The Architect

This post is intended for the organisation and coordination of collective emails between the community and The Architect

Who are the Heralds?

The Heralds (also dubbed @ProjectSkyHeralds by the NMSCord legendary mods) are a group of operators co-ordinating the Wasperator group email for organised contact with @the_architect.

Included in this group are: @Gumsk @sheralmyst @ThatBomberBoi @vector_cmdr @Rusty @Vau1t

Wasperator Group Email - Standard Operating Procedure

1. Gathering and Filtering

  • Whether the community needs to or should email Archie may arise organically in operator discussion of certain events or crises.

  • In these cases where operators want to reach out, a Herald or operator may suggest that we need to email The Architect as a collective.

A distinction is made here between Urgent and Non-urgent topics.

Urgent

  • Needing communication within minutes. For example: when the virus was first observed.

  • The operators and/or Heralds involved in the moment are best placed to decide whether a subject is urgent or not.

  • If a subject is urgent, it can be sent to the Architect by any active operator available at the time - do not feel obliged to wait on formalities if you have something time sensitive.

Non-urgent

  • Topics that are less time critical and may have had some community discussion of what to send or what action to take.

  • For example when the community was deciding the strategy and targets to select to stop the virus

2. Communicating to The Architect

Urgent topics

  • Emails on urgent topics can be sent by any operator, and should be followed up with an email from the heralds (if and when they available) to direct The Architect’s attention.

  • Email subject: URGENT: FAO THE ARCHITECT: [subject]

  • Email body: Include a summary of the issue, include links to relevant discussion points in ETARC or NMScord, citing the operator(s) involved.

Non-urgent topics

  • Operators may choose to independently email Archie from time to time with non-urgent topics.

  • Heralds or operators may also suggest a collective email to the architect as discussed in 1. above.

  • Email subject: FAO The Architect: [subject]

  • Email body: Include a summary of the query or solution, include links to relevant discussion points or community alignment in ETARC or NMScord.

3. Gatekeeping

  • Urgent topics do not require a consensus.

  • Non-urgent topics most likely would require a poll of operator suggestions and views to decide what to send, if sending via the Wasperators group email.

  • Clarification: If there is “no time” to wait for a poll or for a Herald to be available, then it is an urgent topic.

4. Conflict Resolution

  • There may arise occasions where there is disagreement between consensus views between the ETARC and NMSCord communities.

  • The Heralds active at the time will try to mediate and reach a consensus on what and whether to email.

5. Reporting Back

Emails sent via the Wasperators group email to Archie and the replies should be shared at the following:

  • NMScord project-skyscraper channel

  • NMScord project-sky-beacon channel

  • The ETARC thread below :backhand_index_pointing_down:

Addendum

@the_architect please reply all to include the Wasperators’ group email when you are replying to these emails, it helps us all stay up to date and provide coverage across time zones.

21 Likes

Just to be absolutely clear, this is just how the members of this email address are going to communicate with Archie. We have no pretensions of special status and no control over other waperators, and we don’t want any control. We just want everyone to understand how we will use this so there’s no ambiguity and no conspiracy theories about how we are monopolizing communication or gatekeeping inappropriately. If you have concerns, let us know and we’ll all try to address them and make everyone happy.

And thanks to Rusty for typing this up, TBB for posting it, Vector for pushing for transparent and organized communication, etc etc etc.

14 Likes

I have added the :memo: emoji as a prefix to the topic title

4 Likes

The Wasperators ! It sounds like a etymology superhero gang, I love it :sweat_smile::heart_eyes:

4 Likes

Wasperators?? I know who the mascot could be!!

(For context for those who don’t know: this is Waspinator from Transformers Beast Wars. He’s an unlucky fella who gets brutally destroyed in pretty much every episode in increasingly silly and funny ways. :laughing: )

10 Likes

I was thinking Hornitor from power rangers

6 Likes

I think it’s gotta be this guy

9 Likes

I don’t know if I’ve built up enough time in this forum to safely send an image, so I’ll just say,

I think the obvious answer is the DireWASP armor itself! It’s directly related to NMS, it fits the wasp joke, it’s (relatively) easily accessible assuming you did the expedition, what’s not to like?

Buuut if that’s not an option, I throw my hat in the ring for Toddumptious’ pick :smiley:

6 Likes

We have had some return correspondence with @the_architect on the topic of the time shift/drift events we’ve been witnessing:

Please see above

12 Likes

So putting my understanding into a list

  1. So there is an event that is important to system it’s trying to sync with.
  2. We don’t know what it is.
  3. If system could sync that single event, the asynchronous event could stop, as the symptoms would subside.

Should we start looking at memories where the timestamp from system does not match the actual event(as there are many) and feed that to system?

Sorry if this should go somewhere else.

6 Likes

A response seeking some extra clarity and offering the current understanding has been sent to @the_architect :

7 Likes

We have received a reply from @the_architect to the above email:

7 Likes

If we could please discuss the contents on the current running puzzle / event / main threads (like this one for the drift: Drift Detected ) to help keep the thread a little cleaner for chronology, we would appreciate it :folded_hands:
Thank you in advance! :heart:

(We may move the chronology of the emails into the wiki section due to multipost limits, TBC!)

8 Likes


A follow up reply to this email has been sent, gathering up potential candidates and questions from across the community.

7 Likes

Reached out to System about the 16 grey images, of the Heralds 5 out of 6 are in the 16 greyed postcards.

8 Likes

Response from The Architect


10 Likes

6 posts were merged into an existing topic: :memo: If you look out your window [System Coordinates in Prime Responses]

I bee-lieve I concur

5 Likes

I moved some replies. Let’s keep this thread for the shared emails

9 Likes

We have a challenger

5 Likes