A working map of Kyle Durepos projects: agent planners, microVM infrastructure, browser instruments, emulators, live-show tools, and intentionally weird software with real internals.
This is not a polished agency reel. It is a public machine room for experiments that ship: some stable, some research-grade, some funny on purpose, all built to expose the machinery instead of hiding it behind generic portfolio copy.
The Ussyverse is a long-running workshop for software that feels operated, not merely viewed. The projects share a taste for local-first control, traceable agent work, strange-but-usable interfaces, and browser experiences that treat WebGL, WebAudio, WebSockets, and WASM as raw creative material.
Each sector is a different pressure test: can agents produce inspectable work, can small infrastructure stay understandable, can AI feel supervised, and can a browser still become a weird little computer instead of another landing page?
"Pipelines, terminals, dashboards, and protocols for turning vague software intent into artifacts a human can review, interrupt, and hand off."
"Firecracker sandboxes, tiny control planes, routing glue, and static-web infrastructure that prefer legibility over cloud theatre."
"Translation rooms, retrieval surfaces, policy gates, and cyber-range arenas where AI systems are watched as tools, not worshipped as magic."
"DAWs, emulated desktops, tabletop bots, horse genetics, improv scoreboards, and media studios built like toys that know they are systems."
Most projects here are built as small systems with visible seams. Instead of one giant platform, the work is split into tools that can be inspected independently: a planner writes artifacts, an agent runtime enforces policy, a dashboard shows state, a VM controller owns machines, and browser apps turn local APIs into playful interfaces.
Agent projects revolve around explicit plans, logs, permissions, and review points. The goal is not to make automation invisible; it is to make the handoff between human intent and machine execution legible enough to debug.
The infrastructure projects prefer primitive building blocks: Firecracker VMs, SQLite, SSH keys, static JSON, local disks, and simple routing. They are meant to be operated by a person who can still understand the whole shape.
Creative projects use the browser as a full workbench: WebAudio for instruments, WASM for emulation and DSP, WebSockets for live rooms, and canvas/WebGL for interfaces that feel more like control panels than templates.
The console is not just decoration. Every node maps to a repository or deployed experiment. Edges connect projects that share infrastructure, research lineage, tags, or operating style. Selecting a node highlights nearby work, moves the camera to that project, and loads the inspector with source links, runtime links, technical specs, and implementation notes.
Use the left panel when you want a stable index. Use the graph when you want spatial relationships. Drag to rotate, wheel to zoom, click a node to inspect, and double-click the scene to reset the view.
The inspector shows what the project does, how it works, key technical specs, core capabilities, source links, live runtimes where available, and telemetry-flavored notes that match the project’s role in the constellation.
Open the graph for the spatial version, or jump directly to the source/community links. This final dock stays readable now; nothing auto-launches until you choose it.
Bring weird systems, agent orchestration notes, local infrastructure questions, browser API experiments, and half-finished demos. The dock is for builders who like the strange parts of software as much as the finished screenshots.
Connect to Discord ServerPatch armor plating by +20 hull, capped at maxHull.
Add +1 maxShieldHp pip for enemy-style shield buffering.