Fix: GC constraint is silicon design focused on C, not a fundamental Lisp limitation — Symbolics Genera proved Lisp as systems language with proper hardware support

projects/cl-modernization/_index.org

@@ -28,7 +28,9 @@ The central claim: Lisp's defects are not fundamental. They are deferred ecosyst
 - Ecosystem scale (a network effect, fixable with sustained effort)
 #+END_QUOTE
 
-The first category — GC pauses and shared-state concurrency — is real. Lisp will never be a systems language in the Rust sense for those two reasons. But for everything Passepartout does (knowledge management, protocol synthesis, agent coordination, verification), GC pauses at predictable intervals are acceptable. The second category is what this project fixes.
+The first category — GC pauses and shared-state concurrency — is a genuine engineering constraint, but it is contingent on hardware, not a law of nature. Symbolics' Genera OS was a full operating system written in Lisp — device drivers, window system, TCP/IP, file server, all running on the Ivory processor with hardware tag checking, generational write barriers at cache level, and single-cycle CONS allocation. Lisp was a systems language; the chip was designed for it. The reason Lisp struggles on modern silicon is that 40 years of CPU design — cache lines (64 bytes for C structs), prefetchers (linear access patterns), TLBs (contiguous layout), branch predictors (C's control flow) — has been optimized for C's memory model, not for tagged pointer architectures. A RISC-V extension with ~50K additional gates (CONS with write barrier, tag dispatch, read barrier, tag extract, GC check) eliminates the hardware mismatch, as analyzed in [[id:dddd52a7-adb8-470e-a459-614ade5f76af][Closing the Lisp Gap]].
+
+Without dedicated silicon, Lisp on commodity hardware has larger memory overhead and less predictable pause times on allocation-heavy workloads than C or Rust. For everything Passepartout does — knowledge management, protocol synthesis, agent coordination, verification — modern concurrent generational GCs (single-digit millisecond pauses) are entirely acceptable. The second category — the ecosystem gap — is what this project fixes.
 
 * Why Lisp Is a Uniquely Good Candidate