ACTIVE SYSTEMS // SELECTED WORK
Current projects spanning systems software, adaptive interfaces, data recovery, local AI, and digital audio. Each one is a working investigation, not a fictional product screen.
The umbrella computing ecosystem: Arcology OS, ArcoBASIC, ArcoFission, executable forms, Contracts, and the polymorphic substrate being designed as one human-centered environment -- now typing back at a real keyboard, on a real laptop, with nothing left underneath it but the machine itself.
An offline imaging, recovery, and hardware-migration system built for the moment someone realizes what they are about to lose -- it protects source media, creates resumable verified images, and makes repair-bench work clear enough to trust with what cannot be replaced.
A research architecture for intelligence that answers to the person who owns the hardware it runs on, not a distant server -- private, local-first AI infrastructure, specialized agents, constrained tools, and memory that never has to leave the room.
A collection of effects, synthesis experiments, and performance tools built to make sound do things air and wood were never going to do on their own -- spatial, tactile, and slightly impossible.
An engineering prototype being built to treat a guitar as what it actually is -- one continuous physical conversation from string motion to speaker cone -- connecting pickup construction, electrical circuits, amplifiers, cabinets, and microphones into a single inspectable signal path.
An experimental text input system that attempts to reconstruct complete language from abbreviated input, reducing the distance between a thought and its expression.
A family shopping, pantry, recipe, and meal-planning system that lets one household actually think like a household -- turning shared state into useful, reviewable actions across Android, Firebase, and the web.
An ArcoBASIC biological-emulation substrate exploring DNA-like data encoding, gene expression, mutagen exposure, persistent cell state, and ethical simulation of interference effects on developing intelligence.
I favor inspectable systems, direct prototypes, and frequent contact with the actual problem. Architecture matters, but only when it helps a tool become safer, clearer, or more capable.