Without Good and Evil: Military AI and the Architecture of Refusal
The Pentagon designated Anthropic a security threat over two AI guardrails. What 'any lawful purpose' means depends entirely on who defines 'lawful.'

Notes on building with AI, agents, and infrastructure
The Pentagon designated Anthropic a security threat over two AI guardrails. What 'any lawful purpose' means depends entirely on who defines 'lawful.'
Anthropic disclosed three Chinese labs ran 16M exchanges to extract Claude. The model layer isn't a moat — it's a source. What can't be distilled?
OpenClaw's creator joined OpenAI the same week the project hit 200K stars. Every major open-source project faces this pattern. The ClosedClaw moment is here.
WebMCP just landed in Chrome Canary — the first browser-native signal that every website is becoming an API. The frontend was always an interface.
Current builds — agents, infrastructure, and the systems connecting them.
Building personal infrastructure for running AI services locally. The goal: own the stack, control the data, understand what's actually happening under the hood. Privacy-focused setups that don't depend on someone else's API staying cheap.
Building agents with the Anthropic Agent SDK and OpenAI Agents SDK. The background in marketing and strategy means these aren't toy demos — they're built around real workflows, real constraints, and the kind of problems that eat entire afternoons if you do them manually.
Designing agent systems that go beyond demos — multi-agent coordination, tool use, human-in-the-loop patterns. Exploring what it takes to build agents that handle real workflows reliably.
The tools and frameworks powering everything I build.
Philosophy, linguistics, and German Studies at HHU Düsseldorf — Wittgenstein, pragmatism, philosophy of language. I went in expecting academic philosophy and came out with a different question: not "what do words mean?" but "what do they do?" How framing shapes what's possible. How the same problem dissolves or solidifies depending on how you describe it. That question turned out to be the most practical thing I've ever studied.
It runs through everything. Building agentic systems is a language problem before it's an engineering problem. A system prompt isn't code — it's a behavioral contract written in natural language, where every word carries weight because the model takes you literally. Tool design isn't API design — it's communication design, writing for a reader that pattern-matches on descriptions. The gap between an agent that works and one that doesn't is almost always a gap in clarity, not capability. Wittgenstein argued that philosophical problems dissolve when you examine the language that created them. The same move works on broken agent architectures.
I work full-time at a digital marketing agency in Düsseldorf — 5.5+ years as the first full-time employee, building operational structures from the ground up. Strategy, concept development, copywriting, SEO, client consulting, project management, and delivery across 100+ projects. Three years ago, AI changed how I deliver that work — not as a shortcut, but as a multiplier. The judgment and the relationships are still mine. AI handles the execution bottlenecks that used to cap what one person could ship.
The work I'm most interested in now sits between the model and the world. System prompts, tool architectures, multi-agent orchestration, the infrastructure that turns generic AI capabilities into systems that solve specific problems. That layer — where domain expertise meets agent infrastructure — is where the actual value lives. Not in the models themselves. Models get commoditized. The orchestration layer doesn't, because it encodes knowledge that can't be prompted out of any model.
I write about what I build. The blog covers agent architecture, infrastructure economics, open-source dynamics, and what happens when you take philosophy of language seriously in a field that runs on language. Every public text now has three audiences — human readers, the writer, and future AI models that will compress it into training data. I write for all three.
Want to connect? Drop me a DM on X or reach out on LinkedIn — happy to talk about AI agents, infrastructure, or whatever you're building.