Arthur Rozhinskiy · AI operations
Konrad is my AI operations system: one orchestrator, about fifteen agents working in parallel, and me in the loop approving everything that matters.
Through it I ship games, AI video, creator search, automations and the paperwork in between, with the speed of a team and the judgment of one accountable person.
01 · How it works
From the desktop, or from my phone through Konrad’s Telegram bot and Mini App: a typed task, a voice note, a file, a meeting recording.
The orchestrator plans the work, splits it into pieces, picks the right model for each one and hands the pieces out. Routine work goes to lighter models, hard calls stay with the strongest.
Around fifteen agents run side by side: code, research, design, video, documents. Each has a clear brief, its own project folder and the tools it needs, and reports back with the result, not the noise.
Anything that leaves the system waits for my yes: a message, a post, a push, a deploy, a deletion. Every generated frame and build is shown to me before the next step.
02 · Work
Projects are described without client, brand or product names. Numbers are real and come from the projects themselves.
Creator search
An always-on pipeline: it collects creators for a brief, measures median views and engagement, screens topics with a language model and sends shortlists to a Telegram Mini App for swipe review, with a small CRM behind it.
Games
A Unity 6 horror prototype built with the author of the comic it adapts: I pick mechanics, accept test builds and decide merges, agents write the code to my specs. Next to it, a first-person multiplayer game on Roblox with two worlds, quests and daily rewards.
AI video
English channels made end to end by one pipeline: script, image generation, parallax animation, voice and subtitles. The flagship is interactive horror, where viewers pick the next turn of the story in the comments.
Career ops
A LinkedIn profile rewritten against the language of 27 real job postings, a daily shortlist of roles, and drafted applications that go out only after I read them.
Documents
Long, scattered chat histories turned into dated timelines where every line points back to the message it came from. Nothing is added that the source does not say.
Konrad itself
Live progress of every agent, voice input, files, project topics, guest access, local search over chats and automatic model routing. Konrad maintains and extends its own tooling under the same rules.
03 · Principles
Messages, posts, pushes, deploys and deletions are prepared by agents and released by me. Konrad never answers anyone on my behalf on its own.
Voice recognition and search over my chats run on my own machine. Keys and tokens live in files, never in chats, logs or prompts.
Each project has its own folder and its own facts. Client work is kept separate and described without names.
Facts are checked against the source before they reach anyone. If something is unknown, the agent asks instead of guessing.
Agents draft, build and test. I review, decide and answer for what ships.
Why Konrad
The name is German, from kuoni and rat: bold counsel. It also nods to Konrad Zuse, who built the Z3 in 1941, the first working programmable computer. The owl is drawn from the same three shapes as everything else here: a circle, a triangle and a square.
04 · Contact
Hiring for AI operations, product or production, or need a pipeline built and run? Write to me directly.