01
GOPNIK
Checks whether your AI agent is merely convinced. Automated reviews, validation, and common sense.
INDEPENDENT ENGINEERING WORKSHOP
WE BUILD
THINGS
THAT PROBABLY
SHOULD EXIST.
Open-source tools, experiments,
and notes on building with AI.
AI / TOOLS / AUTOMATION / EXPERIMENTS / QUESTIONABLE IDEAS
SAME IDEAS.DIFFERENT DUCK. BUILD
AUTOMATE
BREAK
REPEAT
PROJECTS
ALL PROJECTS →
02
KONSTRUKTOR
An autonomous engineer that takes a task and tries to solve it all the way to a result.
NOTES
ALL NOTES →
The fly in DOOM: what does it mean to digitise a brain?
What researchers digitised in a fruit fly brain, how they test its computational model, and how we turned one part of the idea into a walk through DOOM.
READ →
Doomguy, but a fly: no way out
A fruit fly in a Doomguy helmet is trapped on E1M1. A preview of our experiment: tiny legs, an endless base, and a little digital horror.
READ →
Konstruktor: when writing code is not enough
How Konstruktor turns a coding-agent task into a specification, plan, verifiable result, and report.
READ →
An AI Garden: a local agronomist for the greenhouse
An experiment with a local model, an ESP32, and a greenhouse: can AI help plants grow by monitoring and managing their conditions?
READ →
Everything → OCI? Do We Need Separate Maven, PyPI, and npm Repositories?
Helm and OpenTofu already use OCI registries for more than containers. Maven, PyPI, and npm may eventually share a universal storage layer too.
READ →
Agentic Development and IDPs: Why Platform Engineering Matters More
Autonomous coding agents need more than code generation: they need engineering context. An Internal Developer Portal can provide it.
READ →
Gopnik-Driven Development
Why agents struggle to verify their own work and how Gopnik turns self-checking into a reproducible attempt to break the result.
READ →