feat(report): add implementation sub-chapters

report/chapters/04_implementation/05_python_checking.typ

@@ -3,6 +3,33 @@
 
 = Python Type Checking <sec:impl-python>
 
+We have now built a type definition language and registry, but it is of no use if we cannot type-check our Python code. In a similar fashion to `MidasTyper`, we must now implement a `PythonTyper`. Its role is to take in some Python source code and the types registry, walk through each statement and expression, infer the type of each term and verify the program's soundness. We will need several tools to concretize this process, such as a resolver to keep track of which value each variable references, and an environment to store the inferred types of local variables.
+
+== Parsing Python <sec:python-parsing>
+#todo[]
+
+== Resolving References <sec:python-resolver>
+#todo[]
+
+== Type Checking Statements <sec:python-check-stmt>
+#todo[]
+
+== Type Checking Expressions <sec:python-check-expr>
+#todo[]
+
+== Type Checking Calls <sec:python-check-calls>
+#todo[]
+
+== Casts and Static Evaluation <sec:python-check-casts>
+#todo[]
+
+== Frames and Columns <sec:python-df-cols>
+#todo[]
+
+== Output <sec:python-output>
+#todo[]
+
+
 /*
 - Python type checking
   - Parsing (short paragraph about AST nodes)

report/chapters/04_implementation/06_generation.typ

@@ -3,6 +3,16 @@
 
 = Code Generation <sec:impl-generation>
 
+== Stubs <sec:gen-stubs>
+#todo[]
+
+== Output Code <sec:gen-code>
+#todo[]
+
+== Assertions <sec:gen-assertions>
+#todo[]
+
+
 /*
 - Code generation
   - Stubs