diff --git a/chapters/00. Coding Contingencies.md b/chapters/00. Coding Contingencies.md
index f0698d4..0acb7d2 100644
--- a/chapters/00. Coding Contingencies.md	
+++ b/chapters/00. Coding Contingencies.md	
@@ -8,7 +8,7 @@ Notes for the intro
 -   Could be interesting to read What the Dormouse Said
 ```
 
-## Setup
+## Simulation overview
 
 Notes:
 
@@ -28,7 +28,7 @@ How did they choose a particular programming language, a coding paradigm, a deve
 
 Personal decisions, trending technologies, curiosity and boredom, to name a few. A talk on esolangs as form of frugality, a collegue passionate about live coding that drags you to an algorave night, a crypto-boyfriend, the tech stack of a company, a drastic turn of events, etc. etc.
 
-These contingencies are situated in precise contexts.
+These contingencies are situated in contexts.
 Programming then is not just sharing code, but sharing context.
 It's providing a point of view and a perspective to look at the world, before attempting to get some grip onto it with a script.
 
@@ -53,22 +53,54 @@ Using the simulation as a writing machine we can articulate these CC with some b
 
     Partecipants entangle gradually, and do not come as a monolithic block.
     They can be imagined as lines: merging together and branching away, tying and loosening knots. (Ingold)
-    This leads to multi-facets characters, where not all the elements needs to interact with each other all the time.
-    Their interfaces can be loose, they don't need to be one hundred percent compatible to come together.
+    This leads to multi-facets and situated (Haraway) subjects, where not all the elements needs to interact with each other all the time. Their interfaces can be loose, they don't need to be one hundred percent compatible to come together.
 
 4. Orientation
 
     Zooming in and out from the particular, we get a glimpse of a more gradual and diffuse process.
     A subtle sense of direction emerge from the initial randomness.
-    (By design) the simulation sees software as a mean to orientate these trajectories.
+    By design, the simulation articulates software as a mean to orientate, as well as being oriented by, these trajectories.  
     How does certain programming languages facilitate certain ways of thinking, and totally block some others?
 
 This procedure helps us to think about software as cultural object. Something "deeply woven into contemporary life –economically, culturally, creatively, politically– in manners both obvious and nearly invisible." (Software Studies, 2009), and not just as technical tool existing in a vacuum.
 
 [structure of the simulation]
+
+After this overview, the simulation follows a series of steps:
+
+1. Requirements
+
+Where we decide and define the elements involved in the simulation.
+
+2. Setup
+
+Where we join these actors together in small combinations.
+These will be the starting worlds of the simulation.
+
+To keep things simple, each world will be a closed ecosystem, and there won't be explicit interaction between different ones.
+
+2. Worlds simulation
+
+At this point each world will be really dry and synthetic, defined just by some labels that state that an actor is a musician, the name of a programming language, etc.
+
+The structure of the simulation resembles a nested loop: for each world visit each participant, and ask for updates. Actually, we can save resources simulating just the combinations we want to explore, and not all the worlds of the initial dataset.
+
+The more a world is iterated, the more in depth its simulation becomes.
+
+```
+loop through worlds
+ for each world
+  visit each participant
+  ask for update
+```
+
+3. Insert documentation element
+
+Throughout some iterations, the worlds will develop network of relations between actors.
+
 [software documentation as entry point]
 
-## Requirements
+## Requirements and setup
 
 Notes: