Founder & CTO
“Speaking the languages of humans and machines with equal precision.”
I build two companies. Atrium runs the operative day of a school and is in pilot at its first one. ProsaBridge translates whole books for publishers, with layout and terminology intact. Agents write most of my code, and strict quality gates decide what ships.
Portfolio
Founder
The operative day of a school in one place: class register, absences, sick notes, parent letters, cleaning rota. One typed contract from API to screen.
In pilot at its first school, the Freie Evangelische Schule Kirchheim. A public home at atrium.schule follows this autumn.
Co-founder & CTO
Whole manuscripts move through context-aware LLM pipelines and come back as Word documents with every heading, footnote, and italic in place.
In testing with the first publishing customer. At the Frankfurt Book Fair in October 2026.
Lead full stack developer
The digital home of a school: a fast, accessible website, the declarative infrastructure under it, and the groundwork that made FESK the first Atrium pilot school.
Cold boots eliminated, search impressions tripled, infrastructure cost down 60 percent. Now the first Atrium pilot school.
How I work
My engineering standards are public: one operating contract for humans and agents, strict lint and type configuration, accessibility testing, and the sync engine that keeps every repository aligned with it. The work is verified mechanically, so nothing relies on an agent’s word, including mine.
Lint, types, tests, and WCAG 2.2 AA accessibility run as one command. A gate that errors fails, and deploys run only for commits the gate has passed.
Agent review passes fix findings, then verify the fixes. Nothing merges on an agent’s self-report.
Every repository shares the same operating contract and skills, kept aligned by a sync engine. The gates strengthen over time and never weaken to let a change pass.
Capabilities
Typed end to end. Untrusted input is validated at the boundary, expected failures are typed errors, and the compiler enforces the contract between server and screen.
Agents write most of my code under strict quality gates, and LLM pipelines run in my products. Nothing ships on a model’s word.
Servers are described in code, changed through reviewed pull requests, and converged to match the repository. Secrets stay encrypted at rest.
Lint, types, tests, and accessibility run as one command that must pass before anything merges. The gates strengthen over time and never weaken.
Languages bridge cultures and enable global collaboration
Professional certifications as proof of competence
Building scalable, accessible web applications and complex UI architectures.
CI/CD pipelines, Docker, Kubernetes, and cloud-native development.
Concurrent programming and back-end architecture in Go.
Open source
Insights
Notes from building products and the systems behind them: architecture, measured results, and the occasional failed experiment.
View all postsAgent-written code can look finished long before it is safe to merge. This is the evidence system every change must pass before it reaches main.
Read articleAn experimental review workflow ran 39 passes, wrote most of its own defects, changed live repository settings, and still could not finish.
Read articleHow a school website went from a five-second cold start to instant responses, and cut its infrastructure cost by 60 percent on the way.
Read articleLet's connect
If you run a school that Atrium could serve, a publishing house with manuscripts to translate, or you want to compare notes on quality gates and agent workflows, write me.
david@vornholt.online