5 May 2026

1 note

TLDR Tech

AI Agents Built in Markdown: Why That Matters

Flue is a TypeScript framework where you define agent logic and context in Markdown files. That sounds like a footnote in a GitHub readme, but it points to something worth taking seriously if you're building automated decisioning or customer journey tooling in financial services.

The interesting shift here is who gets to author agent behaviour. When agent logic lives in code, only engineers touch it. When it lives in Markdown, business analysts, compliance teams, and product managers can read it, review it, and potentially edit it. That changes the governance conversation entirely.

Why This Matters for Consumer Credit

In a regulated environment, explainability and auditability of automated decisions are not optional extras. The FCA expects firms to understand and evidence how their systems make decisions that affect consumers. Right now, most AI agent implementations are opaque by default. Logic is buried in Python scripts or prompt strings scattered across a codebase.

A framework where the decision logic is declared in human-readable files offers a different approach:

  • Compliance reviewers can interrogate the agent's reasoning context without needing a developer present
  • Changes to agent behaviour create readable diffs that can sit in a change management process
  • Version control becomes a natural audit trail

Flue is experimental. You would not ship a loan decisioning agent on it tomorrow. But the design philosophy it represents, separating agent logic from runtime implementation and making that logic readable by non-engineers, is exactly the direction production tooling needs to travel.

The firms that will struggle with AI agents in 2025 and 2026 are those treating agent behaviour as a pure engineering concern. When your agent is declining credit applications or triggering collections contacts, that behaviour is a regulated activity. It needs the same oversight rigour as any other policy.

The question worth sitting with is whether your current AI tooling produces artefacts that your compliance function can actually review, or whether you're asking them to take engineers' word for it.

  • AI agents
  • AI
  • automation