info/teamwork.md

+To monitor fair division of work in your groups, we ask that each of you sends us an _individual_ email, from your EPFL address, to both PhD assistants and the instructor via **email**.
+The email should contain an estimate how much you and your team mates contributed to each of the four common projects and to the self-chosen final project, with * next to your name, in the form of a table with percentages rounded down, e.g., with a perfect split:
+
+Person1 Lab1:33%, Lab2:33%, Lab3:33%, Lab4:33%, Lab5: 33%, Project: 33%
+Person2* Lab1:33%, Lab2:33%, Lab3:33%, Lab4:33%, Lab5: 33%, Project: 33%
+Person3 Lab1:33%, Lab2:33%, Lab3:33%, Lab4:33%, Lab5: 33%, Project: 33%
+
+Every column should add to 99 or 100; if you each repeated the same work (e.g. each of you solved Lab1 entirely on your own but only one solution was taken), please renormalize and devide "redundantly" done work evenly.
+
+After that, please add any specific clarifications and explanations _if_ you feel it is helpful, but try to keep them no longer than 10 sentences.
+
+We leave it to each of you whether you discuss and reconcile these numbers and claims within the group. In any case, we would like to receive emails from _individual_ students, without CC or BCC to the remaining group members. Hence, in some cases we may see contradictory information if that reflects how people feel. The email title should be "My Teamwork Statement CS-320". If you have any issues or questions regarding this, please ask here on Ed, or directly to the same emails (but a clarification email should have a somewhat different title, like "Question on Teamwork Statement").
+
+If we get nearly 33% for everything from every group member of a 3-person group (with or without explanations), we will trust this group did a fair split and leave it at that. Else, we may follow up with you in the following weeks. We will try to use this information in a positive way, and we hope that this final step will not ruin any otherwise working group dynamics.
+
+We ask you to submit teamwork statements twice:
+  * on the day after the deadline for Lab 3
+  * on the day after the deadline for the final lab (extension project)
+  

labs/amy_reference_compiler.md

-# The Amy Reference Compiler
-
-We provide you with a reference compiler for the Amy language that you can use to explore the expected behavior of your own compiler.
-
-The reference compiler is [available here](https://gitlab.epfl.ch/lara/cs320/-/blob/main/labs/amyc-assembly-1.7.jar).
-
-You can run it as follows:
-  java -cp amyc-assembly-1.7.jar amyc.Main [options] [input files]
-
-To see the list of available options do 
-  java -cp amyc-assembly-1.7.jar amyc.Main --help
-
-The easiest way to execute a program is to run it in `--interpret` mode. If you want to generate WebAssembly binary code, you should follow these steps:
-  * Install `nodejs`. We have tested amyc with Node version 12, though other versions might work. See the [Node website](https://nodejs.org/en/) for installation instructions.
-  * Make sure the `wat2wasm` executable is visible, i.e., it is in the system path or, for Linux or Mac, you are at the toplevel of the `amyc` directory.
-  * Run `npm install deasync` in the directory you plan to run `amyc`.
-  * Run `amyc` without options. You will get a few output files.
-  * Run `nodejs <output file>.js`
-
-
-# Bug Reports
-
-We welcome bug reports! Please use the forum on Moodle for this purpose.

labs/amy_specification.md

-# The Amy Specification 
-
-You can access the Amy specification document [here](https://gitlab.epfl.ch/lara/cs320/-/blob/main/labs/amy_specification.pdf).