01
One Source, Three Durability Tiers: How Noorle's Program Runtime Is Built
Durability isn't one mechanism — it's a spectrum. A well-built orchestration runtime picks a different point on it for each kind of state it owns, on purpose.
Read dispatchThe engineering journal Vol. 01 · 2026
Field notes from the Agent OS.
Architecture, runtimes, durability, governance, and what autonomous systems actually require in production.
Written from the work—not around it.Entries006
Latest filingAug 13, 2026
OrderNewest first ↓
Latest dispatches Architecture · Runtime · Agents
02Outside the Sandbox: Why Production Agent Runtimes Need a Hybrid Architecture
Most agent platforms force you to choose between security and state — orchestration inside the sandbox is convenient but unsafe; orchestration outside with ephemeral sandboxes is safe but stateless. The hybrid pattern resolves the trade-off.
Read dispatch
03Frameworks vs. Runtimes: The Next Shift in AI Agent Infrastructure
Frameworks taught us how to build agents. Runtimes are where agents actually run. Understanding this distinction is the key to shipping agents that work in production.
Read dispatch
04Compute Engines for AI Agents: Why One Size Doesn't Fit All
When deploying AI agents that execute code, choosing the right compute engine becomes critical. Understanding the trade-offs reveals why successful AI agent platforms need multiple compute options working in tandem.
Read dispatch
05The Perfect Fit: MCP + WebAssembly Components
MCP wants modular, sandboxed, language-agnostic tools with clean contracts. WebAssembly Components and WASI P2 deliver exactly that—turning fragmented toolchains into a unified, secure, polyglot platform.
Read dispatch
06What AI Agents Really Need: Fundamental Requirements for Effective Agent Systems
The gap between AI agent promise and performance isn't about language model power—it's about understanding what individual agents actually need to work effectively.
Read dispatch