CONTEXT.md: record pending decisions (klog ring, disk-recognition scope)

1 files changed, 16 insertions, 0 deletions

diff --git a/CONTEXT.md b/CONTEXT.md
index 0d43b9f..68d2368 100644
--- a/CONTEXT.md
+++ b/CONTEXT.md
@@ -246,6 +246,22 @@ Single Rust crate (`x86_64-unknown-uefi` target).  Module breakdown:
 - **ramfs only for `/`**: the root filesystem is still the ramfs (lost on
   reboot); persistent files live under `/disk` (AHCI/FAT32).
 
+## Pending decisions (agreed, not yet implemented)
+
+- **`klog` kernel log ring**: capture all boot/low-level messages by
+  appending to a RAM ring buffer inside `serial_println!` (one choke
+  point, every existing message captured for free).  Ring: 128 lines ×
+  128 chars ≈ 16 KB, sequence numbers, wrap/drop accounting.
+- **`klog` command** = thin alias for `cat /dev/klog` plus filters
+  `-h` (head) and `-t` (tail); no log levels, no timestamps, nothing
+  fancier.  `/dev/klog` is a char device so `klog > /disk/…/boot.log`
+  persists a boot log via the existing redirection.
+- **Disk recognition scope — keep simple for now**: no pre-EBS UEFI
+  block-device census, no GPT/MBR partition parsing, no NVMe driver.
+  (Revisit later: Linux-style recognition = PCI scan → ahci/nvme →
+  partitions → superblock autodetect → by-label/by-uuid naming; our
+  `/disk/<LABEL>-<SERIAL>` already mirrors the by-label/by-uuid idea.)
+
 ## Target audience
 
 Learning exercise and toy.  Not a Linux replacement.  Not POSIX-compatible.