Updated 04 August 2022.
What is this?
This is a manual we use with our clients and Nodes to make sure our communication stays secure and efficient at all time under all circumstances. It is based on years of experience in managing international projects. It is updated as often as needed.
TL;DR.
- The organization as a whole is comprised of people from all walks of life, all countries, religions, ages, genders. For most of them English is the second language if not the third. Access to internet is unequal. With this, we must manage complex projects of international marketing and import/export, dealing with orders worth hundreds of thousands of €, dealing with various laws, regulations, custom clearance, explicit and implicit rules. Communication is what will make or break the organization. We need a clear process to have some kind of harmony and consistency within the organization. Something that help people avoid the common mistakes and as the organization grows, something that stays up to date so as to leverage on IT tools to make the organization more efficient and secure instead of IT being seen as cumbersome.
- We are a distributed organization (Cf. Whitepaper). On each project, “Ad-Hoc teams” are formed, with their own self-governance process. They operate in a trustless and permissionless fashion. Their obligation is therefore to follow a set of rules to keep consistency across the entire organisation.
Content of this article.
01. Dilemma.
02. Fundamentals.
03. Teamwork.
04. Applications.
05. Prioritisation.
06. Offboarding.
01. Dilemma.
90 % of the problems arising can be traced back to some sort of communication problem. So we never put too much time and effort into making sure we’re explicitly understood.
We’re a distributed organization; governance is distributed. It means that once roles and responsibilities have been clearly defined for each task, project, or within each circle, people don’t ask permission when something falls under their scope of responsibility, they make any decision that they see fit and take responsibility for it. What this implies is that roles and responsibilities must be crystal clear for any participant, at any time, this information must be equally accessible by all participants. This is the main point of having a communication mantra: ensuring the rules of the game are understood and played by at any time, any where, under any circumstances.
Typical questions in a decentralized governance :
- What are the ongoing activities we need to pay attention to and who will own each ?
- What expectations can I reasonably hold of others and vice versa ?
- Who will make which decisions and within what limits ?
- What decisions can I make and what actions can I take without having to call a meeting ?
- What policies or constraints will we honor in our work together ?
- How can we change the answers to these questions as we learn better ways of working together ?
In a world that is changing faster every day, governance needs to become an ongoing part of how an organization operates. What’s more, the people working on the front line are often better positioned to drive continual improvements within their context and monitor the results from day to day.
02. Fundamentals.
02.01 Short term memory.
- Memo-pads with pens everywhere. On your desk, in your car, beside your bed, in your backpack (or purse).
- Short term memory lasts less than a minute. When you have an idea popping up in mind, like the catchphrase of the century or the agreement clause that will win the deal and so on, by the time you get back to your computer, it will be gone, forever. So always have a memo pad nearby and write down what comes to mind as soon as possible. Park your car if need be, because before the next stop light it could be gone.
02.02 Time management.
Get this: In the human brain, there is no area dedicated to measuring time. IRMf has given neuroscience the ability to record brain’s activity down to a single neuron. And it has shown that not a single neuron is used for measuring time, when at the same time humans (mostly males) have the ability to feel magnetic fields.
Conclusion: Always work with a timer, and stick to your schedule. If you have an alarm wrist watch, set alarms for all your appointments.
02.03 Sterile environment.
Multi-tasking is a myth debunked by neuroscience. (Read the book “The memory illusion” by Dr Julia Shaw). Being efficient will require self-discipline, but your mental health will greatly improve.
- Shut off all notifications of any kind on any device. A pop-up can leave traces in your brain for up to three months. Notifications are destroying your mental health.
- Group tasks according to brainpower/device/software usage: research, writing, video meeting, answering emails, answering social media, accounting.
- Then prioritize tasks according to their need for attention to detail and focus. For example, Drafting a contract over writing an article over doing a research over preparing a meeting over calling clients over answering emails over answering social media etc.
- Then schedule these tasks precisely in your diary according to above priority. Keep tasks requiring the more focus for the morning, going to tasks requiring the less focus to casual tasks along the day.
- In your diary, give enough time to each task according to their expected requirement so as not to be working under time pressure, this would be counter-productive as you would end up having to do things twice due to countless mistakes.
- Include a 5 minutes break every 25 minutes to leave your chair and monitor and go stretch your legs and get some fresh air for your brain. Use a countdown timer for this.
- Sterile environment means -> You must not BE ABLE TO answer emails, phone calls, social media messages. So not only all notifications and software must be turned off, but if you can, remove the devices from your place (i.e leave your phone outside your room).
- It is advised not to install social media apps on your phone but instead use an emulator on your computer, so that they really become work-related applications, and are accessed accordingly.
- Open your communication software only during the set time slots. One for emails, one for phone calls, one for video meetings, one for social media etc.
- Create your own rules, but put your mental health first, work efficiency will only benefit.
- Once you’ve created your own rules, stick to them for a week or so. Then adjust in an ongoing iterative process.
- Let people know how you work. Include in the footer of your emails a Post Scriptum for that (example below).
02.04 Rules for emails.
- Create a sterile environment.
- Do not use any software that has access to your devices’ notifications (i.e outlook on Windows, Gmail on Android).
- Shut off any notifications in the settings (sound, lock screen, banners, icon etc).
- Do not check your emails at all outside of the dedicated “email time” periods. We recommend between 11am-12am and 16pm-17pm.
- For new inbound emails, do not ever answer the same day. If someone has to reach you urgently, they will use the telephone or a secure app. Anyone sending you an email shouldn’t expect an answer before 7 days. Of course if you get an answer to one of your own email, you can reply asap, don’t shoot yourself in the foot.
- As an example, here is the Post Scriptum we include in our emails: “Email is the most unsecured communication channel in use. It has been invented in the 70s and has never been designed to be secure in the first place. Unless you can give us your PGP key, please stop using emails and instead use encrypted apps. See our contact page (copy/past): ubinodes.org/contact/“
02.05 Rules for Video meetings.
- Use UTC to coordinate your meeting time.
- Scheduling: Use plain English when communicating your availability in order to avoid any misinterpretation. For example, do not say “I’m available 1100 – 1700 UTC”. You’re communicating with people from different industries and cultures, so it’s not clear what the sign “-” means. The reader can not be sure whether you are available “from 1100 to 1700” or “at 1100 and then also at 1700 UTC”.
- Prepare the meeting thoroughly beforehand using a shared document app. Explicitly describe how the briefing is going to be organized:
- Day – Date – UTC Time in 24 format.
- Participants.
- Applications to be used.
- Pre-requisits. What is expected from participants prior to the briefing. (read this, install that, complete such task etc).
- Subjects. What are we going to talk about during the briefing. Ask all your questions prior to the meeting so that people have the time to prepare their answers.
- To Do. During the briefing, define a To Do list for the week.
- Use a countdown timer, stick to the schedule.
- It´s better to have multiple 20 minutes meetings rather than long, infrequent ones.
- If any new topic comes up, it will be discussed in the next meeting.
- The next meeting can be the same day, for example if you have done a meeting in the morning, you can agree to do another one late afternoon for all the new topics, or the day after, but in any case, don’t overshoot the agreed time, otherwise it’s going to become impossible to schedule a meeting in anyone’s agenda.
- Devices: If possible use a mobile device on 4G for audio/video apps (Wire, Wickr, Olvid, Signal, Threema etc) and the desktop with screensharing and office apps (Jitsi, Jami, Cryptpad, Resilio etc) on broadband but open also your audio/video messaging app on your desktop to easily write text or share clickable links. Start the call using the mobile device. That way if one channel breaks down you still have a communication channel. Additionally you have more bandwidth capacity. Also, use ear plugs with microphone so that your audience can hear you clearly.
- Lighting: Use additional lighting located close by the lens of the camera to be clearly visible for your audience.
- Background: Have a “sterile” background so as not to divert attention of participants. Remove everything that is in the frame, such as posters, office documents and accessories etc.
02.06 Rules for files.
Name: Give short and descriptive names. « Draft » is not relevant. « Draft article Resilio » is better.
Date: Put the date in front of your file’s name so that your Team mates can quickly see which is the latest version or if a file has been updated. The format shall be year/month/day. For example « 2022 07 21 draft article Resilio ».
Duplicates: Do not create a duplicate of the same file, this is extremely confusing for your team mates.
- No renaming: For example if you’ve just done some editing on « 2022 07 21 Draft article Resilio », you don’t save it under « 2022 07 21 Draft article Resilio-updated” or « 2022 07 21 Draft article Resilio v2”. You simply let your team mates know what you’ve done through communication apps.
- No cross apps: You don’t put the same file in different apps, for example you don’t put the same file in both Resilio and Cryptpad.
02.07 Rules for communication apps.
02.07.01 Use case.
Refer to whitepaper. Nodes are always working as an Ad-Hoc team. For each task, there is a lead node (see below Teamwork). For communication, groups are created using secured applications. One group is created for each task or project for the following reasons:
- So as to avoid confusion and amalgamation.
- For confidentiality purpose, as we work on a need-to-know basis, you can’t keep a “do-it-all” group for all tasks with all Nodes.
- For ephemerality purpose. Once a task is completed the group can be deleted. Otherwise with a “do-it-all” group, it’s never deleted.
The problem with chat apps is that information is lost in translation. So they shall be used as channels only to :
- Pass on a status update on documents, like a new paragraph has been added, a new file or folder has been created.
- Brainstorm ideas in groups (although video/voice meetings are best).
They should not be used to :
- Do full briefing/debriefings. This should be put in a proper document.
- Update information on documents, this should be put in red in the relevant document.
- Do project planning. Tasks, responsibilities, deadlines, and so on should be put in specific files.
Tips:
- When a chat group is created by the lead node for a specific project, providing a general announcement about what the group was created for will help inform nodes participating in the project on why they are there. This lowers the likelihood of confusion between team members.
- To make your posts easier to read, you can prepare them into a notepad and then copy/paste. That way you can use a more elaborate formatting.
02.07.02 Witness.
In each group, you must have at least three people. Even if the task is carried out by only two Nodes, one Node must be added as a witness. The role of the witness is to silently observe the communication and if need be, intervene as a trusted and unbiased party to resolve issues.
02.07.03 Hashtags.
We use groups in secured application to communicate on various tasks and projects. We do this for years now and with people from all countries, social backgrounds and native tongues. Very early, one Node started using hashtags # before each sentence to mark which topic he was referring to in the thread. It just happened naturally because we were discussing so many topics at once, it was impossible to efficiently follow on a conversation. Despite it is technically possible to answer a post so have your answer embedded into the original post, it’s hard to reply to a reply to a reply. So, even though we have one specific group for each topic, we all naturally adopted the hashtag habit. Before starting a sentence, we put a hashtag with a keyword. For example “#Proofreading. blablabla.”
02.08 Grammar.
Don’t use SMS like writing, like « tis » or « cu » etc. Nodes are from all walks of life, cultures, languages, education etc. Average age is expected to be closer to 40 than 20. Communication is going to be difficult, everything that can be done to make is easier to understand shall be done. Use simple plain text scholar English.
02.09 Compartmentalization.
Compartmentalize everything. Communication, data, lives, etc.
- Use different apps for different means. One app for clients, one for nodes, one for new candidates, and so on.
- Create synchronized folders for each specific Ad-Hoc team, so as to share on a need-to-know basis only.
02.10 Trustless and permissionless.
We are a decentralized and distributed organization, meaning that we shall operate in a trustless and permissionless manner. This is possible if and only if all participants follow and enforce the same set of rules. Bad actors shall be identified and removed from the organization while new actors shall be correctly and constantly trained to Ubinodes’ standards and procedures.
02.11 No mind reading.
Don’t assume workmates do mind reading. Use communications apps to let them know what you do, why, where you’re at and so on. It’s not because you’ve changed a file’s name that people will know you’ve updated a document. It’s not because you gave people a deadline that they’ll know you’ve actually completed the work on it. etc.
02.12 Toxic People.
There are toxic people in every community, and they present a constant threat to the livelihood of the community. Toxic people tend to join communities to fulfill a toxic latent desire; this could be attention-seeking, obtaining money without making an effort to help, etc. Either way, it’s best to always double check credentials and work effort. Keep a close eye on your own actions by keeping a record of your work. If it seems as though you haven’t done much, look for opportunities to do more, and keep an eye on the progress of other members as well. Improved record keeping will allow a quick identification of toxic person(s), and it’s always best to remove the tumor as quickly as possible.
02.13 Disconnection.
Ubinodes being international, it is running 24/7 all week long. It is therefore the responsibility of the receiver to disconnect from communications. To that end, we advise that people use devices and applications specific to Ubinodes which can be physically turned off. Understand the difference in time, culture, and situation will affect when someone responds to communication. Therefore, you should always be patient.
02.13 First hour in the morning.
The First Hour of The Morning is extremely crucial in changing our lives for the better. In order to take care of their physical and mental health so as to have clarity of mind and good communication and decision-making skills Nodes are encouraged to manage the first hour of every morning by refraining from using their mobile phones, social media or any electronic device.
That is actively refraining from something that you impulsively want to do. This leads one to actively engage in ‘action-based denial’, meaning restricting one’s behaviour as a way of keeping our dopamine circuits tuned up. Practicing the routine of avoiding using our phones or scrolling through social media when we wake up and focusing that time on other progressive routines such as preparing for your day, doing a personal assessment, doing yoga or simply stretching the body creates powerful anchors for the recurring internal mechanisms within our bodies and promotes a general feeling of wellbeing.
That’s because when you wake up in the morning, you are in the perfect position to receive the download of all the work that your neurocircuitry has been doing the night before. But if you immediately go into a sensory experience right after waking up, such as the rich sensory experience of scrolling through social media apps and phone notifications, you are potentially ruining your ability to think straight throughout the rest of the day. Today, one can get ten thousand context switches within just 30 minutes of scrolling on Instagram or Tik Tok. Hence, it is all about self-regulation. You have to be able to maintain constant control over the consumption of something that we really enjoy but that we find that we are indulging in just a little bit too frequently.
The key is to regulate that behaviour. Those who will be successful, young or old, are those people who can create their own internal buffers, people who are able to control their relationships to pleasures.
03. Teamwork.
03.01 Time difference.
- Familiarize yourself with working using UTC time (Coordinated Universal Time) as this is what we use to schedule meetings. To schedule meetings you can use the website TimeandDate.
- If you are on Windows you can use a live background to display the time in cities where you have contacts. Download the WorldClock “classic” edition, not the new “.net” one as the latest has no live background feature.
- Be specific. Day – Date – Time in 24h format. There is no “tomorrow” when working internationally. Your “tomorrow” could already be the “today” of someone else.

03.02 Monday briefing.
After the beginning of the task, everyone is going to mind its own business, get distracted, get confused with information floating around. Once a week some formal process must put everyone back on the same page. Asking people to provide a feedback everyday doesn’t work, so instead we’re doing “Monday briefings”. These are tactical meetings.
We deal with the ongoing operations, synchronize team members, triage any difficulties that are preventing progress.This results in clear understanding of projects and next-actions to be taken.
Each participant will explicitly state its situation, both professional and personal, as long as it can have an impact on the project or the other participants’ tasks. Based on the Monday briefing, later communication can be done on chat rooms.
We do an analysis by all nodes on the just concluded week to see how much of the weekly tasks were completed, reason for uncompleted tasks, noted problems, solutions and recommendations. We prepare for the coming week and the percentage of work we were able to cover must be a minimum of 70% (we can improve the figure, if possible to 100%).
03.03 Lead Node.
Each task has a lead node who is responsible for forming and representing the Ad-Hoc Team.
“Lead Node” is a role in the organization, not a position in a hierarchy. You could see the lead Node as the representative of the Ad-Hoc team with additional accountability.
The lead Node is NOT:
- A supervisor, a coach, a manager, telling others what to do and overseeing them.
- The lead Node is not managing the members of the Ad-Hoc team, who may actually fill roles in many other Ad-Hoc teams anyway, with many different lead Nodes.
- It is not the lead Node’s job to direct the team or to take care of all the tensions felt by those in the team.
The lead Node IS:
- A participating Node like all the others in the project, as we are a distributed organization, power is distributed.
- The lead Node holds the perspective and functions to align the Ad-Hoc team with the purpose, strategy and needs of its broader context.
- The lead Node is representing the Ad-Hoc team as a whole and its purpose within the broader environment of the organization.
- The lead Node holds the space within which the purpose of the circle can be fullfilled and keeps out issues and concerns that are not within the scope of that circle.
- The lead Node acts as an interface at the Ad-Hoc team’s boundary when needed, routing incoming information or requests to appropriate roles (need-to-know basis), and bringing resources into the circle and directing them to the most important functions, roles, or tasks within the circle.
- In a new Ad-Hoc team, the lead Node is an entrepreneurial role, actively building a structure to achieve a purpose, and will need to try different approaches, see what works, and adapt. All on behalf of the Ad-Hoc team itself and its purpose.
The lead node shall:
- Be on alert for any lack of clarity in the circle around what role handles what work and makes what decisions, and work to achieve that clarity through the governance process.
- Structure the governance of the Ad-Hoc team to express its purpose and enact its accountability.
- Assign Nodes to the Ad-Hoc team, monitoring the fit, offering feedback to enhance fit, and reassigning roles to other Nodes when useful for enhancing it.
- Allocating the resources across various sub-tasks and/or roles.
- Establishing priorities and strategies for the Ad-Hoc team.
- Defining metrics for the Ad-Hoc team.
Examples:
- Create the relevant shared file folders, shared documents, chat apps groups, etc. It’s easier to have all the documents pertaining to a project into a single place, so it’s best to create a specific synchronized file folder and move all the files that are going to be worked on into this folder, once they’re ready they can be dispatched again in the other shared folders for each Ad-Hoc Team.
- Be responsible for enforcing OpSec rules.
- Create daily and weekly tasks. Each task must have a specific deadline. It is best to keep them small and brief in order to increase the productivity of participating nodes in completing tasks. Once participating nodes complete their assigned tasks, nodes working on the same project can provide feedback to one another.
- Assign roles and responsibilities.
- Ensure feedback loop and iterative process can occur smoothly.
- Ensure payments are quickly processed.
- Supervise the Monday briefings.
- Create Digital Curation work to improve the organization.
03.04 Roles and responsibilities.
Make sure there are no redundancy among nodes who would work on the same task.
Make sure roles and responsibilities are clearly assigned on a nominative basis. In front of each specific task you should have a lead node and the associated participants from the Ad-Hoc team put together to complete the task.
Ask people questions to make sure they understood correctly. If you just ask if they understood or agree, you’re always going to get a “yes” answer. Check by yourself.
In a distributed organization, the role of “manager” is distributed to each Node at arms length. So each Node is equally responsible for:
- Removing constraints within the broader organization that limit the Ad-Hoc team. Said otherwise, find hacks to get the job done.
- Seeking to understand tensions conveyed by Ad-Hoc team members, and discerning those appropriate to process in the Ad-Hoc team.
- Providing visibility to the organization into the health of the Ad-Hoc team, including reporting on any metrics or checklist items assigned to the whole Ad-Hoc team.
03.05 Timeframe.
State clearly time-frames for each task with clear deadlines. “Asap” is not a time-frame and will only lead to pending and partly completed tasks.
03.06 Updates.
When we’re busy completing a project at work, rather than assuming the final product speaks for itself, it’s good to remember to regularly engage and update members of the team during the process.
03.07 Real time editing.
03.07.01 Conflicts.
We may use applications at the same time. This may create conflicts with the data processing for the app.
For applications such as WordPress and Resilio, a secured communication channel must be established so that other Nodes don’t create conflicts with the application by working on the same document/page at the same time.
Note that for Resilio, only the Nodes sharing the same Resilio shall be on this communication channel, not all Nodes. Whereas with WordPress, anyone having editor access to the website must be in the channel.
03.07.02 Cryptpad vs Resilio.
We use both Resilio and Cryptpad to collaborate. Both of them offer end-to-end encryption. It’s not one versus the other, it’s both of them at the same time on the same projects, so you need to clearly understand their pros and cons in order to figure out how you’re going to maximize efficiency for your team.
- Resilio: Provides decentralization. Good for working with static files (images, PDFs, videos). Can also be used for Text and Spreadsheet once they require minimal inputs because in no case a file shall be opened by two people at the same time.
- Cryptpad: Provides real time collaboration features. Excellent for draft articles, sharing task lists and so on. Not to be used to share static files as everytime you want access you need to download them o your computer, so Resilio is much better suited.
03.08 Ephemerality.
- On communication apps, set expiry time to 1 week for groups and individuals.
- Once you’re done working with a file or folder, destroy it using bleach it or Privazr.
- Do not duplicate information, this is extremely confusing for your workmates. For example if you’re working with an online document sharing app such as Cryptpad and decide that a file synchronisation app such as Resilio is more appropriate, then cut/paste the content then destroy the old file(s).
- Pursuant to E.U privacy and data retention law, forensically delete any trace once a project is completed: chat rooms, sync keys, emails, files, folders, etc.
- Do a clean install of your OS on a regular basis, depending on your threat model. At least once every 6 months.
- Use a micro-cut paper shredder for all the documents of the household. Make it the new norm at home.
03.09 Sandboxing.
Practice has always been the best way to improve a skill. Nobody is exempt from this rule. Like any other skill, the tasks in Ubinodes can be optimized by repetition. This is why you are expected to try every type of task in a risk-free area first before bringing it to a professional situation. Use pre-made guides when first trying a new process, and gradually add your own experiences over time to improve efficiency. We want to get every task to the level of muscle-memory, in which it should be like second nature.
03.10 Iterative process.
The process of creating projects does not end with creation and making a post. They are constantly reviewed and refined for the purpose of keeping information relevant and up-to-date. As knowledge and information is always changing, people coming to the website should be rest assured that our posts are improving with it. This also ensures that people will come to our website’s posts multiple times in order to view updates, which we will promote on our Twitter feed.
03.11 Feedback loop.
We are a distributed organization, you’re expected to provide feedback on all aspects so that we adjust our processes. You’re expected to take notes of what we teach you so as to write articles, manuals or update existing articles. Ensure that you have memo pads handy everywhere, because the onboarding process is comprehensive and goes fast.
03.12 48h cut loose.
Due to the nature of the decentralized organization made of freelancers, we regularly have nodes going MIA (missing in action) in the middle of a task. We can’t delay the completion of a project due to these behaviours. It can happen that a node wouldn’t even bother telling people they’re going to take some time off, it’s like they don’t feel any sense of responsibility or reciprocity toward the rest of the team. But most often people may also be in a situation where they have higher priorities, if not a case of force majeur. We can’t control that. So there is a 48h cut-loose procedure: if after 48h of business day a node isn’t replying, (s)he shall be cut loose and someone else be given its task. If the node re-appears later, then the lead node will manage what to do.
03.13 Payments.
Nodes shall send their invoices on Friday. Payments are to be made using the Ubinodes Token.
03.14 Monthly review.
We do a monthly review to discuss:
- The success or failure rate,
- Redundant nodes and what to do,
- Cleaning of files and documents in our folders and webmail’s or wherever necessary,
- What can be improved upon,
- Management of Digital Curation Work.
04. Applications.
With participants from all over the world and all backgrounds, applications used must ensure compatibility across devices. So we aim at using applications that are cross-platform and open-source or freemium. We also use secure communication apps.
04.01 Linux, Windows, Mac.
01. Libre Office. Save in .odt to be compatible with most other office suits.
02. Bleachit. To irretrievably delete data.
03. Wickr Me. Secure messaging. Free.
Me vs Pro:
- Wickr Me: Doesn’t ask you for an email. So you need a password manager to store a strong password as you can’t recover it. Only one-to-one audio-video calls.
- Wickr Pro: Is using your email to register. Less privacy, less security, but you can restore a lost password. Allows for group audio-video calls.
We use Wickr Me to begin with because it’s free. Note that people on the Me network can’t communicate with people on the Pro network unless the Pro is a paid plan.
04.02 Windows only.
01. Privazr. To irretrievably delete data.
02. Photofiltre. To resize and reduce weight of images we publish online.
05. Prioritization.
With all these tasks in front of you for the day, how do you prioritize them? Answer is simple:
- Money.
In this order:
- Money in terms of income, then money stream.
Money is the blood of your organization. You can have a perfectly functioning brain, solid skeleton, a good heart, and strong muscles ready to be put into action. If the blood stream stops, everything dies. Note that money isn’t energy, that would be glucose.
Money income is anything that gets money to come into the organization. The closest to getting money in, the higher in the priority list it is.
Money stream is anything within the organization that gets money flowing freely and rapidly. Again, the freest and fastest to getting money flow, the higher in the priority list. Note that money velocity is what gives value to a currency, as a currency doesn’t have any intrinsic value, contrary to money.
So when you prioritize, you do all the “money income” tasks first, then all the “money stream” actions second, then the rest.
Conclusion: Answering emails or using social media apps is the last item in your priority list! Which is why it is fundamental to use dedicated apps and devices for your communications so as to be able to shield yourself from any kinds of notifications.
Example in order of priority:
1- You have sent an invoice? -> Make sure the client has the bank account details to make a transfer, or the wallet address for crypto, or the payment online page for a credit card, etc.
2- You have sent the completed assignment to the client? -> Send an invoice, then go to number 1.
3- You have several assignments for the day? -> If and only if all things are equal, complete the one(s) that are most likely to be sent by the end of the day. Then by the end of next day. And so on. However, this is only if all things are equal, meaning that you always complete assignments as they came in, never ever allow a client to front run another one because his assignment is quicker and can be completed faster. If you do that you’ll lose the big clients and end up with small and easy assignments, you would go down the value chain.
Example in order of priority. You have received money?
1- Pay other nodes if an Ad-Hoc team is set up.
2- Pay overhead bills.
3- Pay suppliers.
4- Pay Digital Curation works.
5- Donate towards Sponsored Projects.
06. Offboarding.
In accordance with our agreements and European laws, we have designed an offboarding process which aims at protecting the organization’s and clients’ data against the most evil form of corruption, that is: a corrupt judicial system. So this process is to make sure our past stakeholders, and their devices, can no longer be used to cause harm to the organization or our clients.
If a stakeholder has to be away for an unknown period, (s)he must complete in full the onboarding process. This applies to anyone; a node, client, contractor, etc.
If at a later date the person comes back, we’ll quickly go through the stage 01 of the onboarding process and assign new IDs.
This applies to applications and accounts related to the organization in any shape or form. If you wish or have to keep contact with anyone, use new private accounts.
01. Accounts. Delete accounts for messaging apps (i.e Wickr), social media apps (i.e Twitter, LinkedIn) , email accounts (i.e Protonmail), online services accounts (i.e Cryptpad,) etc. This will ensure no-one can impersonate you.
02. Applications. Once you have deleted accounts, then uninstall the application. Some applications such as Resilio are not linked to an account.
03. Destruction. Irretrievably destroy any data from your computer, files and folders, rubbish bin, using dedicated software such as Bleachit or Privazr. If possible, do a clean install of your OS. Do a low level format of your USB sticks. This is the only way to make sure forensic software can’t retrieve deleted data. Do not keep any backups of data!