ANTON+MATZKAIM

been building the whole visual package for our understav crew’s ritual event. logo, 3d poster, 2d poster, dj posts, teaser, all of it.

here’s the 2d poster. industrial goth meets techno ritual aesthetics. layered cyrillic type, distorted geometry, red-black palette with this cold blue accent in the center. kept it dark but structured, like the lineup itself.

the logo and 3d stuff push it further into bio-digital territory. building a coherent system that works across formats: instagram posts need to read instantly, a4 posters need to pull you in from across the bar.

i keep a private vault. everything lands there through a telegram bot: voice notes, links, half-formed thoughts, whatever i mumble into the phone while walking. that part works fine. this site sits still for a month at a time, because moving something from the vault to here means rewriting it, tagging it, committing it. even asking an ai to do it means opening a thing and explaining myself, and i never feel like it.

i orchestrate a pile of agents on big projects now, rave land and the school platform mostly, and i keep hitting the same wall. i see code appear. i don’t see the path. what they researched, what they tried and threw out, where they’re stuck, what they decided and why. all of it exists, in fifty markdown files nobody reads twice.

what i want is one screen over that. every component with a status: researching, building, works, blocked. blockers with numbers on them so i can point at one in a message. the last ten findings, not the whole journal since day one. goals, with what’s actually done. open questions sitting there waiting on my call. and a decisions archive, so in a month i still know why we took three.js and not babylon.

the pipeline i want for props: point a phone at a real object, and a few minutes later it’s in the library, ready to drop into the world. no downloading, no importing, no fixing normals at 2am.

scanning is the solved part. lidar on a pro iphone through polycam or scaniverse, photogrammetry through luma or meshroom if there’s no lidar. out comes a glb with a texture. for a stylized world it doesn’t even have to be clean, a rough scan after retopo does the job.

been thinking about documentation wrong this whole time. i treated it as a description of the code. when an agent does the work, it should be a panel where i watch the thing think.

code is the only output i get. the process evaporates. which libraries it rejected and why, where it hit an incompatibility, what it learned reading someone else’s repo, which parts are still half done. next session it doesn’t remember any of that either, so it re-researches what it already knew last tuesday.