a Berlin-based engineering leader focused on distributed systems, serverless architectures, and AI-native applications. Iβve led cross-functional teams at Intel, Delivery Hero, Blacklane, and WΓΌrth Cloud Services shipping scalable platforms and shaping long-term technical strategy. My current interests revolve around Rust, WebAssembly, Synthetic Data, and in-browser AI.
Portability, Isolation, and the Locality of Intelligence
β The Fictional History of Machinic ToolsMeasure β Compare β Adjust
Deploy β Observe β Roll Back
Rewrite β Benchmark β Rewrite
Behavior β Update β Suggest
Observe β adjust β repeat.
Input
The loop begins with a signal: user input, system state, or environmental data. entering the runtime boundary.
Interpret
The system contextualizes the signal using its current memory and predictive model to construct a meaningful internal representation.
Decide
Based on memory and prediction, the loop selects the next action either deterministic, probabilistic, or a combination of both.
Act
The system executes the action, updates its memory with the outcome, and prepares for the next iteration of the loop.
β The History of Machinic ToolsClient
API
Cloud
LLM
Loop
Tools
Memory
βοΈ Cloud
π₯ Desktop
π± Mobile
π Edge
π§ Browser Tab
β’ Mozilla AI blueprints β Can the browser be a serious runtime?
β’ wasm-agents blueprint β Pyodide in-browser notebooks
β’ Built a PoC β wasm-browser-agents-blueprint
Thanks Davide from Mozilla.ai β€οΈ
# Build and run with Docker (Recommended)
docker build -t wasm-browser-agents-app .
# For development with hot-reload
docker run -p 5173:5173 \
-v $(pwd)/demos:/app/demos \
-v $(pwd)/src:/app/src \
wasm-browser-agents-app
| Loop Component | Browser Primitive |
|---|---|
| Memory (short-term) | JS Heap |
| Memory (long-term) | IndexedDB |
| Decision (prediction) | WebLLM |
| Deterministic Logic | WebAssembly |
| Parallel Execution | WebWorkers |
| Tool Access | Web APIs |
| Acceleration | WebGPU |
| Isolation Boundary | Workers + WASM sandbox |
Structural
If the loop is real, parts of it must be deterministic, too.
β An unwritten book on WASM Agents SM made it portable.
Reconstruction
Same loop,
different placement.
When You Close the Loop Locally, You Inherit New Taxes
Memory
Local loops are bounded by device memory.
Distribution
Portability increases distribution cost.
Variance
Portable loops behave differently on every machine.
Energy
Energy is part of loop economics.
Heat
Feedback exists at the hardware layer too.
Context
Context window defines the visible past of the loop.
β The History of Machinic ToolsLocal Loop
private, low latency
Edge Loop
Shared
Cloud Loop
heavy compute
Where Does the Decision Become Real?
It's where the loop closes.
So for agents, too.
Key Takeaways
Agents are feedback loops with memory not personalities. π
Loop placement matters more than model size. π
The browser already contains the primitives to host a loop. π
Isolation (WebWorkers) enables stability. π§±
Portability (WASM) enables polyglot architectures. π§³
Prediction should be paired with deterministic control. βοΈ
Energy, latency, and memory are part of loop economics. β‘
Moving the loop changes privacy, cost, and control. π