Marco Patzelt

Marco Patzelt

Integration Engineer | Agentic Systems Builder

I translate complex requirements into fast, scalable solutions — from architecture to deployment.

By night: Brunnfeld — LLM agents in a medieval economy with no goals, just world physics.

Marco Patzelt
Architecture
Serverless
Backend
Node.js

Lean Architecture:
Less code. More leverage.

I build software infrastructure that doesn't require an IT department to maintain. Use existing infrastructure over custom backends. Architect value, not complexity. Maximum speed, no unnecessary license costs, full independence from sluggish systems.

Infrastructure &
Type Safety

Serverless instead of Server Farms

No maintenance, no downtime. Deployment in serverless environments (e.g., Vercel) means you only pay for compute when it's actually used.

TypeScript Logic

Strict typing prevents errors before they happen. The result is an extremely stable codebase that doesn't break even with complex features.

import { NextResponse } from 'next/server';

import { createClient } from '@supabase/ssr';

export async function POST(req: Request) {

// Typsichere Validierung

const body = await req.json();

const { id } = Schema.parse(body);

const supabase = createClient();

const { data } = await supabase

.from('events')

.select('*');

return NextResponse.json(data);

}

System Status

API Gatewayeu-central-1
24ms
Postgres Replicaread-only
12ms
REALTIME SYNC

Backend & Data

Backend-as-a-Service with Supabase (PostgreSQL).

The Advantage: The same power as enterprise systems, but without the overhead. Data is synchronized in real-time – extremely fast and scalable.

Modular Architecture

Independent components, flexibly connected.

The Principle: It's not just about APIs, but true decoupling. Parts of the system can function independently, be swapped out, or scaled.

Built with

TypeScript end-to-end, from integration middleware to deterministic game engines. These are the tools I actually ship with.

TypeScript
Node.js
Next.js
OpenRouter
SSE Streaming
LLM Orchestration
Game Engine
Vercel
Git
Tailwind
03
Frontend Engineering

Design Implementation & System Integration.

I realize complete web interfaces that are visually convincing and merge seamlessly with the underlying architecture.

Visual Fidelity

"Static layouts turn into functional, responsive websites. I translate designs exactly into code."

Pixel-Perfect
Implementation

Type Safety

"I breathe life into design. How do filters behave? What happens on click? I develop the interaction logic."

Interaction Logic
Behavior

User Experience

"The frontend is not an isolated coat of paint, but the precise counterpart to the backend. Data structures mesh perfectly."

Architecture
Integration

Brunnfeld Medieval Village Economy.

Autonomous multi-agent simulation where LLM agents operate inside a deterministic game engine through structured tool calling. No behavioral prompts, no strategy instructions. Agents receive a ~300 token perception of world state and return JSON action arrays that the engine validates and resolves against live state. Engine owns physics. LLM owns decisions.

Engine vs Agent Split

The engine enforces hunger, tool degradation, supply chains, and seasonal yields. The LLM decides what to do with that reality. Neither alone produces what you see.

agent_runtime.log
> TICK_017: Spring, Monday 08:00
> BUILD_PERCEPTION: anselm → Bakery
> AGENT: inventory=[flour×2, bread×3] wallet=32c

Perception Builder

Each tick the engine builds a ~300 token world snapshot per agent: location, inventory, wallet, marketplace orders, body state. The agent reads only this — never raw world state.

wheat ×4
Mill (Gerda only)
flour ×2
flour ×1
Bakery (Anselm only)
bread ×4
[BOTTLENECK] Gerda missing → bread halted

Hard Supply Chains

Wheat → Mill (Gerda only) → Flour → Bakery (Anselm only) → Bread. One missing link halts production. No instructions needed — the engine makes it structurally necessary.

01
Perception
LLM
03
Resolution

Emergent Governance

Village concerns accumulate in the elder's perception when real thresholds are crossed: broken tools, hunger, wealth concentration. Agents can petition. When pressure builds, Otto calls a meeting. Council votes pass laws that take immediate effect.

Supply Chain Check
ACTIVE
Engine (Recipe)
flour ×1 req.
Engine (Inventory)
flour ×2 avail.
SUPPLY_CHECK (PASS)

Scalable

Generate worlds with up to 1000 agents across 5 villages via a single API call. Runs on any OpenRouter model or locally via Claude CLI. Free models supported.

Architecture Logic

High-Performance
Integration Layer

The Challenge

Architecting the integration layer between a modern marketing platform and Microsoft Dynamics 365 CRM. Technical client coordination, API orchestration, and serverless infrastructure on Vercel.

The Architecture

Middleware Engineering
Node.js on Vercel — decoupling frontend from CRM logic.
Data Synchronization
Dynamics 365 entity reconciliation in real-time.
High-Performance Caching
Upstash (Redis) to minimize latency.
Processing Pipeline
Automated content handling.
FrontendEnterprise Core
Middleware
Vercel Serverless
POST /api/ingest
Redis Lock

"key": "sys_123_lock",

"ttl": 60,

"status": "acquired"

Processing API

"text": "Complex Entity",

"source": "RAW",

"target": "NORM"

Core Sync
Enterprise Core System
await crm.create(data)
Engineering Logs

Latest Thoughts.

View all posts

Let's
connect.

I build middleware by day and autonomous agent systems by night. If you're working on something serious in agentic infrastructure, I'd like to hear about it.

Email me
Email me