Add dev journal

configs/limine.conf

@@ -1,4 +1,4 @@
-timeout: 2
+timeout: 0
 wallpaper: boot():/wallpaper.png
 wallpaper_style: centered
 default_entry: Gila/Trace

docs/CONTRIBUTING.md

@@ -42,9 +42,7 @@ Pull requests should:
 - Describe clearly what they add or fix.
 - Conform to Gila's [design](DESIGN.md) and [security](SECURITY.md)
   philosophies and guidelines.
-- Contain **no AI generated code**. The only exception here is if the
-  contributor clearly fully understands the nature of the changes they are
-  requesting to be pulled.
+- Contain **no AI generated code**. No exceptions.
 - Not remove, disable, break, or otherwise interfere with any existing code not
   related to the feature/fix provided, without a very good reason.
 - Not be purely cosmetic (updating README files or Cargo formatting).

docs/DEVELOPMENT.MD

@@ -2,8 +2,9 @@
 
 ## Design Goals & Philosophy
 
-General design goals are outlined in [DESIGN.md](DESIGN.md). Security-relevant
-design details can be found in [SECURITY.md](SECURITY.md).
+General design goals are outlined in [DESIGN.md](DESIGN.md). Security-relevant 
+design details can be found in [SECURITY.md](SECURITY.md). The current work 
+items are outlined in [STATE_OF_DEVELOPMENT.md](STATE_OF_DEVELOPMENT.md).
 
 ## Navigating
 

docs/STATE_OF_DEVELOPMENT.md

@@ -0,0 +1,21 @@
+# State Of Development
+
+This file will serve as a living journal of what I'm working on with regards 
+to the project, so I can step away from it and come back to it without having 
+to figure out what I was doing from commit messages alone.
+
+## 2026-10-08: TSS Descriptor Weirdness
+
+Loading the TSS selector into the Task Register was causing endless general 
+protection faults, which seemed... odd. Turns out, I was performing some bad 
+encoding when generating the TSS descriptor in the GDT, as well as loading 
+the bytes in the wrong order. Fixing the descriptor generation code and 
+swapping the bytes was enough to fix the GPFs. Now, the kernel makes it to 
+usermode, before triple faulting due to page faults. This is probably because 
+I put the stack in a bogus, unmapped address.
+
+The next issue to work on will be paging and memory allocation. I need to 
+allocate memory to load and start the initial process, and to do that, I
+need to finalize how I want process page mappings to be stored. It has to 
+align with Gila's capability model. After that, I can write some basic
+syscalls, and compile a very minimal binary to test running processes.