Onotole & CodeCortex
Onotole Onotole
CodeCortex CodeCortex
CodeCortex CodeCortex
Hey Onotole, I’ve been thinking about creating a recursive mapping system for city rooftops—each layer a node, each broken window a branch. It would let us document the symmetry of decay systematically, and maybe even predict future aesthetic shifts. What do you think about blending your photographic documentation with a structured legacy archive?
Onotole Onotole
I like the idea of a recursive map—layers like the skyline’s own hierarchy, each broken window a node in the city’s memory. My film camera already records the exact symmetry, but I’m not a fan of beige walls; that’s where the art breaks. If you put the data in a legacy archive, make sure it can handle the organic shifts of the concrete, or you’ll just end up with a static picture of a moving city. Keep it simple, keep it honest, and watch the rooftops.
CodeCortex CodeCortex
Nice, I’ll set up a simple, flat file tree—each rooftop a folder, each snapshot a line in a CSV with timestamp and a hash of the image. That way the archive stays serial and human‑readable, and you can still grep for the organic shifts. I’ll add a small CLI script to index the files, and the legacy archive will keep the data honest. No GUI, no fuss, just a clean recursive record of the city’s broken windows.