¶(all instructions come from a lived experience of fuckups)
### øøø lots of fucks in docu ... clean up

All instructions are written here because somebody at some point messed them up, probably repeatedly.

If they look counter-intuitive ("Why do you write this?"), keep that in mind.

¶(#postserious)

Protocols don't need to be taken at face value. Lots of interactions might, will or maybe must "feel weird". That does not ultimately disqualify them, for a number of possible reasons.

So, in short, these are co-directed "acting" instructions. The crew agrees to go with this, continously updating them, and see how it plays out.

¶(do: self-document the anti-patterns)

    FUCK UP
    ↓
    RECEIVE A CORRECTION
    ↓
    CHECK HERE:
        DISCOVER IT CLEARLY WRITTEN
        OR
        IF NEW, WRITE IT DOWN

¶(also see / ties to ...)

    * 🔗newcomers and 🔗idiots-guide:
        basic instructions

    * 🔗reference-days:
        several typical day variants

    * 🔗roles and 🔗crew-labour:
        work coordination, reproductive work sharing, etc

    * 🔗engineering:
        general guidelines on how to behave in a R&D context

    * 🔗cues:
        a set of co-labour gestures and cues
    * 🔗intersub / #interpersonal

    * ^XXX🔗specificity:
        CHT as HyperDickens

    * ^XXX🔗psycho:
        →(microprotocol) CORRECTIONS
        →(game) MARK + STRIKES
        →(game) POINTS SYSTEMS
        →[...]

    * ^XXX🔗editorial:
        #ethering corrections

______________

    * 🔗in-nature
    * #behaviour, #direction
    * #re-enactment
    * #protocols
    * #subflow
    * #violence
øøø? ###L: AWK, needs context
    * [...]

¶(T) If spoken to, 🗣️ACKNOWLEDGE
#catatonic
( I think this evasive behaviour is common with "I" brigs-myers people ??? )
→ ^XXX🔗antievasion

Never skip acknowledge when crew speaks to you
Never ignore a question

Minimum ack:
    * OK
    * right/yup/on it
    * sure/fine/uhum/aha = [SI]pokroviteljsko
    * ###
 - at least with "uhum" !
 
No ack?
    A) You didn't hear
    B) You heard something was said, but are not in position to respond, so you expect it to be said again
    C) You are ignoring it = not OK 🤜

¶(W+) Triple-check your writing for basic problems
:
    * Broken links ?
    * Bad indentation
    * Spelling mistakes ?
    * Illogical TOC ?
    * [...]

¶(W++) Somebody is saying lots of things - they need to be written

:
    A) write it down ?
    B) pass the computer to them, if you're ok with that
    C) get them a pen and paper
    D) ask to record, transcribe later
    [...]

¶(W++) Maintain current indexes

Link all the pages you are working on immediately in the "main pad" (subseason index).

¶(W++) Acknowledge & credit internal research

When writing a new page, first bind it to all somewhat related pages !

¶(XXX+) Don't ASSUME somebody ASSUMED something
(and then be insulted by it ... that is ASSUMING they ASSUMED and is insulting in itself. APOLOGIZE !)
###L: AWK -- this is too much, too vague for non experiences cht ppl

¶(XXX+) 🤜 Don't take the last word & leave an argument/place
###L: AWK -- this is too much, too vague for non experiences ppl
Unilateral exit from a conversation, without consent of others, traps them in an unresolved situation.
Make sure all other options are explored.

¶(XXX++) 🤜 Don't reply with "deflections" and "justifications"
øøø
    → VOCAB

    * "But I thought that ..."
    * "But you told me to ..."

( Rather, repeat this "underlying cause" in your head and figure out how to prevent it from influencing you in the future. In any case, nothing is gained by clearing this up.)

¶(XXX++) 🤜 Write down novel corrections immediately

🗣️NOVEL
L:20200928
(Here in this document, if not → paper/phone → transcribe at first opportunity).
Repeating? Sign your fuckup with a Date & Time.
You fucked something up in a novel way.
Somebody needed to take the time to explain it to you.
Write it down for posterity and maybe everyone can try minding to not repeat it.
### Overview regularly with keeper ! → I need to ask for this ... [!→R] todos

¶(XXX++) Don't waste my time by 🗣️PARROTING
###L:  AWK - NP

Like:
    * "Go get some water". -- "...OK, I will go get some water."
    * Rhetoric ticks (--"Did you?" responses)

¶(CUE/WT++) "TIGHT" system
    #1: Do something!
    #2: Ask for more ("OK What's next?")

¶(CUE/WT++) "INITIATIVE" system

    #1: Do something!
    #2: Suggest what you could do!

¶(WT+) Upkeep your personal TODO list

(in your PREP PAD, if not elsewhere)
    * Routine tasks !
    * Tasks
    ( Needs a protocol - how to verify, process, etc. !!! )

¶(WT++)  Pre-estimate and communicate work duration

Do NOT work ridiculously longer without re-consulting.
( Example: You are writing about essential oils for 2 weeks already. Others expected it will be a 3-hour research draft. This is not good.)

¶(TRU-) 🤜 Learn how to close and open doors
#~~~ ?

Do NOT let them be taken by the wind, always hold them
Do NOT smash them - just push them in

¶(TRU-) Don't put anything hard in front of the windshield
#~~~

Like drinks glasses.
It breaks, you pay for it.

¶(TECH-) Don't touch my computer / phone without asking
###L: AWK - NP
(If not explicitly pre-consented)

¶(TECH+) Get laptops low-power ready
→→ ### documentation :
    * set Power Savings settings:
        (both to minimum time = 15 min on ubuntu)
        * pn battery
        * when plugged in
    * $ powertop
    * install "tlp" package:
    * [...]

¶(TECH+) When showing somebody something on your computer ...

Max brightness!
Enlarge fonts!

¶(TECH++) Don't do strange things on other people's networks

Don't connect to my hotspot, then run TOR or a bot network or etc
Without checking first!

¶(H-) 🤜 Don't touch glasses/drinking bottles/etc on drinking TOP

That is for my mouth, not your hands.

¶(H-) Brush your teeth daily

In extreme collapse, use a gum.
Use clorohexadine semi-regularly.

🤡

¶(CHEF+) 🤜🤜 ... definitely NOT to pans and knives

If not SPECIFICALLY instructed.

If you are cooking or cleaning, DEFINITELY do not:
    * Fuck up teflon pans:
        ("cleaning them with a glass sponge")
    * Fuck up knives:
        ("i'm cutting this on a ceramic plate")
____________

Do NOT destroy the pans by burning them, then leaving them to dry up.
### huh ???
###L: add something like "without cleaning them"

You either:
    A) Keep the final oil in the pan, for later usage
    B) Clean the pan instantly after frying
        (Scrub carefully but intense with plastic spatulla)
    C) Leave on fire with some water in
        Scrub with spatula
    D) Let soak with fresh water over night

¶(OUT+) Keep camp perimeter contained
:
    Keep camp like it was.
    Don't expand it ("adding new stuff on display"). 🤜
    Don't "invent new solutions" with consulting +Camp.Master
    Take control of EVERY SINGLE ITEM.
    Keep covered stuff covered.

¶(OUT++) Don't "casually" expose lifestyle. Not camouflaging is tactically unsound
:
    * Transporting 8L water bottles
    * walking around with tents, IKEA bags, etc:
        It will be obvious you are a camper / hippie, and this is both illegal and often not approved.
    * looking like a hippie
    * [...]

¶(POL+) Dealing with random other people

DO NOT DISCUSS WITH RANDOMERS
Don't let them come within 2m in a pandemic, and indicate that clearly but not hysterically.
Don't discuss "which van is ours".
Don't discuss "how long we're staying"
[...] ###

... WITH NOBODY
not with "friendly people"
not with "suspicious neighbours"
not with "random guy walking around"
not with "hippie woman you met somewhere"

Do:
    Nod, mutter, shrug like you don't understand, make a general gesture, change the subjects.
    Do it 3 times if they ask again.
    They will not force it, (and if they do, that's even more weird).

¶(POL+) 🤜 Be prudent (=respectful) with the police

* Try to understand, they are probably asking for something reasonable:
    (within the general consensus of the territory)

* Know what you want:
    If you want to leave, work on achieving that.
    Signal it when you get the idea that they want that, don't just "give it" because maybe they want something less, or something different
    ... and now you might need to do something more then they initially intended to ask from you

* If you don't understand, just look witout acknowledging, they'll try repeat it for you

¶(WT)🤜 No wild gesticulations in front of screens

During computer work, do NOT support your brainstorming with hand rhetorics.
Do NOT point rapidly at the screen.
Your gesticulation will make somebody, eyes focused at the screen, get dizzy, and feel ill.

$$$$ IN OVERVIEW ↓↓↓

¶(CHEF/ENV) Don't dispose oil with water

Minimize harm of the nature where we're disposing the water.
Clean oil (from pan) with paper. Throw in normal trash

¶(WT) In multi-person: call people by their name

More than 2 people around? Don't create noise burden for others !

¶(CHEF) Stay away from / respect chef tools
:
    * Never clean kitchen knife with seawater.
    ###L: however, since 7BF/C we do this all the time
    * Never touch teflon pans at all:
        Do not try to stack them, do not try to clean them, do not try to use them.
    * [...]

¶(W/WT+) Help with idea dictation

When you finish writing, say “finished writing”, and report
Especially for critical fragments, including corrections

¶(ENV-) Maintain space clean
#clown
(== KEEP ENVIRONMENT)

Taking out the trash? Set it up as it was before.
You took tools out? Put them back to the same place immediately.

¶(ENV+) 🤜 Maintain space functional & predictable
#antianarchist

Maintain the environment stable, change nothing.
Put things back where they are supposed to be.

Don't randomly "inventing" any core environment changes.
The environment is "FEATURE FREEZE", meaning any smart new ideas need to be discussed.

If you make a change, this means it's a permanent proposal.
There is no "temporary".

__________

¶(ENV/WT+) 🤜 Don't fuck up the technical parts of the equipment & core infrastructure

Examples:
    * Don't unplug the internet phone
    * Double check battery polarity before connecting anything
    * Don't get water on stuff

¶(WT+) Task queue & prioretization: Handling multiple instructions
### ties to @@QUEUE , also @@protocol-planning

What to do when you're already doing something, and you get more instructions?

A) STRONG FIFO ("First in, First out"):
    Finish before first. Remember the others, and do them sequentialy.

B) STRONG FILO ("First in, Last out"):
    Implied that if I told you to do something later, it means I want you to switch to doing that.

C) USE COMMON SENSE:
###AWK ...... C) Don't be a moron:
    Understand that it's usually FILO, but don't leave stuff to break.
    -----------
    General:
        * "Do not leave another person working to wait."
    Problems:
        * "It's difficult to know with these maintenance tasks, which one is more urgent."
    Examples:
        * "Get out" also means "Take the trash out on the way"
        * [...] !!!

_______________________________

How to react when given a task, when you're already working?
    * Ack ("OK a moment!" if queued - can be overriden: "Now!")
    * Obviously: Do NOT repeat
    * [...]

¶(WT) 🤜 To help, first LOOK AROUND for work, only then ASK
Just asking is lazy & violent to the other.

Make yourself useful, don't defer and become a burden.
Do you already *see yourself* anything that need-can be done? :
Yes: go and do that !
No: make yourself useful:
    * Be nearby and ready !
    * Watch and learn !
    * Cue: "What s next" ###

¶(T) 🤜 Don't defer responsibility by "asking questions"
#p.a.

DO NOT:
    * "Should/shall I do xxx?" (←puts the responsibility of decision with the other)
    * "Should we watch a film?" (←you want to, but don't want to select etc?)

DO:
    * "I want to do xxx, is that ok?" (←includes your own consideration of the problem, and doesn't passive-agressively defer it, to evade responsibilty).
    * "I think we need to go to a shop. X seems closest and open, but could also go to a Y, what do you think?"
    ___
    <<<L:
        in dutch we use "shall I " in a more decisive way, while simultaniously keeping space for corrections from the other
        e.g.: "zal ik alvast xxx doen, dan kan jij yyy doen"

¶(ENV-) Use sink without splashing

Especially with salt water, you can ruin someone's laptop with a single drop.

¶(H/CHEF-) 🤜 Don't mess up hygiene domains
#clown

When cooking, use stations to separate different foods (raw meats, salads, etc.)
Respect other people's reasonable expectation of hygiene.

:
    * Dirty clothes <> clean bags
    * Kitchen counter <> floor broom
    * Trash bag <> Kitchen counter
    * Edge of my glass <> Your fingers
    * [...]

###[!→] lies level
###L: AWK - NP
Case: trash on the kitchen surface:
    Trash is DIRTY
    Kitchen is CLEAN
    == NO FIT
_______
Case: touching my food OR touching my glass at where I drink it:
    Your fingers COULD BE DIRTY
    My food MUST NOT BE DIRTY
    == NO FIT

¶(ENV~) 🤜🤜 Don't use gas while others are in van

(B1)
Using the gas kitchen seems to take up all the oxygen in the van, making people ill.
Don't just do it when other people need the van.
Either:
    * ask and get consent
    * do it when others are not around

¶(T/WT+) When coordinating, speak terse — clearly & directly
B1+
###L: Merge with "(T/WT) Give CLEAR AND DIRECT commands, not chatter." fragment
"Can you please make space so i can sit down here"
→ Make space

"Can you maybe please pass me the uhm the hammer"
→ Hammer

"Can you sit up straight, so I can move this up"
    Can I? Do I want to?
    Move what up?
→ Sit up
(I can think about it parallel while doing it, deciding to waste words, etc.)
(This way, chatter only if needed)
------------
In general & to correct, use cue entries:
    * "right..."
    * "listen, ..."

¶(W+) Don't leave your writing in a shit state

Fragments, on pad or paper need to be presentable.
Especially on documents that we are discussing and are coming up for overview.
Ties to ^XXX🔗editorial.

¶(T/H) 🤜 Don't say stupid religious shit
:
    * "oh my god"
    * "jesus"
    * "bless you"

¶(WT+) Delegate tasks further
#newc

Keeper -> Crew -> Newcomers

    * Keeper is overburdened
    * Crew MUST pass on simple tasks, develop more responsibility, assume bigger workloads
    * Newcomers MUST assume reproductive work & report their work contributions

In larger crews, this is managed by >Onboarding.

¶(ENV+) 🤜🤜 Don't leave any stuff that might spill

Undrunk water in a glass on counter ?
Open bottles in the lab ?
Coffee in the front ?

¶(WT+) 🤜 Don't break my workspace

Do NOT fuck around with personal setups:
    * Do NOT move around chargers, take pens, reorder tools, etc.
    * There might be parts of those setups you don't understand.

... or risk it:
    keep the lab clean
    * put it on a surface
    * put it in a box
    * [...]