Clojurians Log v2

Hello. I'm working on a solution to a problem that I think floats in a similar area to concepts I've heard discussed in this community in the past. Basically, doing stuff on the stack. For cljs-thread I wanted shared persistent data between web workers so I invented self-gcing stack-atom kind of things: https://github.com/johnmn3/cljs-thread/blob/eve/README.md I'm going to port it to clojure soon though and target mmap'd files. That should theoretically allow for uncoordinated OS processes to independently bash on 500GB clojure maps in parallel. I'm curious, given y'alls expertise and experience in this area, where you see this going - whether you have any advice or interest in planning. Here's a report on prior art from claude: https://gist.github.com/johnmn3/d2b60b3c6ed08d9972b83c7138e60a6e tl;dr: > The closest thing to EVE in the wild is LMDB on the mmap+multi-reader-epoch axis, combined with immer on the persistent-HAMT axis — but no single system fuses these. Specifically, cross-process epoch-based GC of persistent immutable HAMT nodes does not appear to exist as prior art outside of EVE. The academic EBR literature (DEBRA, PEBR, crossbeam-epoch) is all single-process/single-address-space. The mmap databases (LMDB, Metall) use different reclamation strategies (freelist B-trees, no GC respectively). The persistent structure libraries (immer, im-rs) are fully in-process. Basically, the way I look at it, these are like "stack atoms" and they provide consistent, low latency, writable windows into process independent data in a way that might be innovative and new. But I'm not entirely sure... I'm curious if claude is missing any prior art. Does this method seem similar to anything you've seen before?