Archive

Policy as code, without the risk team having to ship code

A tiny CEL-style DSL plus a board-approved YAML file. The risk team adds a governance rule by editing a config file; engineering ships the rule by restarting the service.

Observability

Turning an agent run into OpenTelemetry spans you can read in the console or ship to a collector.

Wiring OpenTelemetry into a Microsoft Agent Framework agent with configure_otel_providers, console vs OTLP export, and the enable_sensitive_data content trade-off.

Deterministic KYC, the LLM just talks

PAN check-digit validation, Aadhaar offline KYC, DigiLocker, PEP/sanctions — all in Go code, not in a prompt. The LLM's job is to translate the verdict into something a human can read.

Context And Memory

Context providers with two hooks — and file-backed history that survives restarts.

ContextProvider before_run/after_run hooks in Microsoft Agent Framework, plus FileHistoryProvider for on-disk transcripts and a per-session state dict for counters.

Production agentic AI on Kubernetes — Ch 9 patterns vs...

Field notes from running multi-agent AI on K8s. The patterns the book recommends, the ones that survived contact with production, and the ones that broke in interesting ways.

Mcp Tools

Borrowing tools from an external MCP server instead of writing them yourself.

Connecting a Microsoft Agent Framework agent to an external Model Context Protocol server via MCPStdioTool, entered with async with, so its remote tools merge into tools=[...].

Agentic architecture on the Microsoft Agent Framework —...

Microsoft's Multi-Agent Reference Architecture in Go. Protocol, registry, bus, governance, orchestration, observability, evaluation — and how the seven hold each other up.

Middleware

Wrapping an agent run to observe, guard, or short-circuit it — without touching the agent's logic.

Agent, chat, and function middleware in Microsoft Agent Framework: one middleware=[...] list, call_next() with no args, and short-circuiting via MiddlewareTermination.

Host Your Agent

Everything so far ran once and exited. To use an agent like a product, put a server in front of it — DevUI stands up a local web chat around any agent with one call.

serve() from agent_framework.devui wraps any agent in a local web chat; it blocks with its own event loop and ships as a separate install.

First Graph Workflow

The functional API hid the graph. Here it's explicit: executors are nodes, edges join them, and a message flows from the start executor along the edges.

Build a two-node graph with WorkflowBuilder: executors send_message or yield_output, and the type hint on WorkflowContext carries the routing intent.

Functional Workflow Basics

A workflow is not an LLM thing — it's a way to compose steps with checkpointing and events. This one has no agent and no model call, so it runs with zero credentials.

A credential-free workflow of two @step functions composed by a @workflow, isolating checkpointing, steps and outputs from any model call.

Functional Workflow With Agents

Compose several agents into a pipeline with the gentlest workflow API: decorate an async function with @workflow and call agents inside it with plain await.

Decorate an async function with @workflow and call agents inside it with plain await: a writer drafts, an editor tightens, one line of glue each.