Medical coding is a high-stakes extraction and verification problem, not a simple text generation task. Asking an LLM to read a long clinical note and directly output ICD codes risks hallucinated mappings, missed comorbidities, and results that are difficult for human coders to audit. A reliable medical coding system should be built as an LLM-assisted workflow: extract clinical evidence, retrieve candidate codes, verify mappings, validate against the taxonomy, and route uncertainty to human review. The model should not be expected to memorize every code. Its job is to help produce auditable evidence inside a controlled workflow.

Building Auditable LLM Workflows for Medical Coding

Agent world models are emerging as an important simulation layer between reasoning and execution. Early LLM agents followed a fragile loop: prompt, think, call a tool, wait for the result. In production, that loop is expensive and risky because the agent often cannot predict whether an action will move the workflow forward, fail silently, or mutate state in an unsafe way. A world model acts as a surrogate environment. Given a current state and candidate action, it predicts likely next states, failure modes, and observations. This allows agents to rank possible actions before touching real systems.

World Models are becoming the simulation substrate for Agents

A layered framework for scaling production AI systems begins with the SLA: latency, throughput, reliability, cost per resolved task, fallback behavior, and quality targets. Those requirements drive the architecture of the runtime — spanning the edge gateway, safety and governance, orchestration and routing, inference serving, compute scheduling, context and state management, model lifecycle operations, and observability.

The Runtime Behind Production AI

Production agents are hard to operate because teams need to understand why they acted. Traditional observability tracks service health: latency, errors, throughput, CPU, and memory. Agent observability must go further. It must capture intent, workflow state, retrieved context, model and prompt versions, tool proposals, policy checks, approvals, state mutations, and final outcomes. Enterprise trust requires replay. A reliable agent system must be able to prove which decision, context bundle, and policy check allowed an autonomous action to happen.


Agent Observability Is Not Optional

As AI agents move from short-lived chat interactions to long-running autonomous systems, the hardest engineering problems are no longer about prompts or model quality. They are about state management, replay safety, memory hierarchy, checkpointing, and transactional execution. Production agents need a cache-aware, transactional runtime. Agent state should not be a probabilistic byproduct of a chat log; it should be a deterministic projection of validated events.

State Is the Hard Part of Production Agents

Production agents should not be designed around the fantasy of full autonomy. In real environments, agents face brittle interfaces, evolving user preferences, security gates, ambiguous state, and irreversible actions. The goal is not to remove humans entirely, but to build systems that know when autonomy is safe and when control should be reduced. A reliable agent is not one that never needs help. It is one that knows when to slow down, ask for confirmation, or hand control back.

Production Agents Run on an Autonomy Spectrum

In production, agent behavior is shaped by the runtime around the model: which tools are visible, when retrieval happens, how retries are handled, what state is persisted, and who is allowed to commit mutations. Reliable agents require more than better prompts or stronger models. They need runtime architecture. Framework defaults, tool visibility, retry policies, and context assembly rules can change behavior even when the underlying model stays the same.

Agent Reliability Lives in the Runtime

Chat is a useful interface, but it becomes a weak system design primitive once agents are expected to complete real work. A reliable agent should advance a process, not merely generate text. That requires routing simple requests to deterministic paths, using retrieval when grounding is needed, reserving reasoning for ambiguous tasks, and separating planning from execution. For repeatable workflows, LLMs can generate structured plans while deterministic engines handle tool calls, retries, and state transitions. Production agents should be designed around explicit, inspectable, and evaluable workflow state—not reconstructed from chat history every time.

Design Agents Around Workflows, Not Chat Turns

Production agents should not send every request to the most expensive reasoning path. As reasoning models become more capable, they also introduce new production risks: higher latency, unpredictable cost, KV-cache pressure, and unnecessary “overthinking” for simple requests. Before invoking deep inference, tool use, or multi-step planning, a production agent should first decide which path is actually needed. Production agents are control systems. The real engineering value is not only in the model, but in the controller that decides when to reason, when to execute, and when to ask for human approval.

Routing Before Reasoning

A reliable agent is not just an LLM connected to tools. A production agent stack is a system of layered responsibilities.
The runtime owns execution state and governs workflow progression. The planner proposes next steps, but proposals are not execution. Memory provides contextual recall without serving as the source of truth. Agent interoperability enables structured delegation, while tools expose external capabilities through standardized protocols such as MCP.
Validation transforms probabilistic model outputs into structured, policy-constrained proposals that can safely enter the execution pipeline. Execution itself occurs inside isolated runtime environments where side effects can be controlled, audited, recovered, or rolled back.

The Production Agent Stack

This post walks through the implementation of a minimal invoice-processing agent. The agent parses an invoice, verifies it against a ledger, requests approval when needed, and writes the final entry only after validation. The core pattern is simple: state constrains actions, the planner proposes one, validation gates it, tools return observations, the reducer updates state, and the runtime decides whether to stop. Before adopting complex orchestration frameworks, build this loop first.

Building a Simple Agent from Scratch

Search is no longer just a user-facing answer interface. In production agent systems, it is becoming the context acquisition layer of the agent runtime.
Traditional search returned ranked documents and left the user to interpret results. Early RAG systems followed a similar pattern: retrieve evidence, inject it into the prompt, and generate a response. But agents use search differently. They invoke search as an internal workflow step to clarify intent, retrieve evidence, choose tools, verify state, inspect logs, and recover from failures.

Search Is Becoming Agent Infrastructure

Agentic search engines—such as Google AI Mode, Perplexity, Bing Copilot, ChatGPT Search no longer means “type keywords, get ten blue links.” AI Search experience capable of understanding tasks, planning queries, calling tools, and synthesizing results and deliver a conversational response with inline citations, minimizing user effort.  In this post, I’ll walk through the stack from bottom to top, how it crawls and indexes pages, how it retrieves and ranks information, and how recent features like RAG and Agentic search build upon these foundations.

Demystifying Agentic Search Engines

Building Modern Recommendation Systems introduces a comprehensive, end-to-end pipeline that drives intelligent recommendations. The post walks through the full machine learning workflow — from raw data preparation and feature engineering to model training, deployment, real-time inference, and system monitoring. 

Modern Recommendation System Infrastructure

This post explores the full RecSys architecture, emphasizing the core models that drive each stage of the RecSys pipeline — from Retrieval for large-scale candidate generation, to Pre-ranking for efficient filtering, Ranking for fine-grained relevance modeling, and Re-ranking for balancing diversity and control.

Design a Modern Recommendation System

Building production ML systems is far more than selecting a model. Success requires thinking in terms of a full lifecycle: defining precise functional and non-functional requirements, designing robust data pipelines, splitting logic between models and rules, versioning and deploying models, prompts, and embeddings as coherent units, and continuously monitoring system performance and product impact.

The ML Factory: Building Production ML Systems

本文简要总结了深度学习在NLP、计算机视觉、信息检索和推荐系统四大主流领域的演进脉络：从早期RNN、CNN等专用模型，到Transformer全面主导，再到如今BERT/GPT、ViT、Diffusion等预训练大模型横扫各领域。核心趋势是预训练+生成式范式取代传统任务特定模型，统一建模与生成式架构正在加速推动各领域融合与新一轮创新。

各领域的深度学习模型

大模型（LLM）关键技术：从基础到落地

机器学习模型：从传统算法到生成式AI

ML 模型生产全流程

NLP技术与应用：从语言理解到智能生成

模型训练的方法与实践

本文系统回顾了深度学习的发展脉络，从基础神经网络到Attention 与 Transformer的出现，再到深度生成模型的兴起，最后介绍了多模态与统一建模架构的发展趋势，展示了当前主流的模型体系。

深度学习模型架构的演进

本文探讨了机器学习如何推动人与机器的自然交流，从早期的对话系统到如今能够理解意图、执行任务的智能助理。近年来的趋势是向LLM + Agent 化对话系统演进，LLM 可嵌入架构中各核心模块，增强系统的理解、生成与决策能力。最终，通过引入智能代理机制，让对话系统从“能说”进一步迈向“能做”。

对话系统：从人机交流走向理解与互动

Binary search is an efficient searching technique based on the divide-and-conquer principle. By repeatedly narrowing the search space, it guarantees a worst-case time complexity of O(log n). It is well-suited for sorted data, monotonic arrays, and optimization problems where the goal is to find the best value. Common use cases include exact matching, boundary and insertion point searches, finding the closest element, and performing binary search on the answer space. 

Shrinking the Search Space with Binary Search

The two-pointer technique is essential for optimizing operations on arrays, strings, and lists, often reducing time complexity from O(n²) to O(n). Common patterns include opposing pointers, sliding windows, fast–slow pointers, and dual-input pointers—each suited to different problem types such as finding pairs, subarrays, or merging sorted lists. 

Solving Problems with the Two-Pointers Technique

Topological Sorting Explained: Sorting Dependency Chains

Prefix search is a fundamental operation in computer science, typically implemented using a Trie (prefix tree). A Trie is a dynamic data structure for storing a collection of strings, supporting efficient insertion, lookup, and enumeration operations. Tries and their variants provide a powerful and efficient way to manage and query large volumes of string data.

Implementing Efficient Prefix Search with Tries

Depth-First Search: Exploring Deep Before Wide

Breadth-First Search: Level-Order Exploration

Recursion is a core computational concept where a problem is solved by calling itself on smaller instances. Recursion is key to many algorithms: DFS (Depth-First Search) is often implemented recursively, Dynamic Programming is fundamentally recursion with caching (memoization), and Divide & Conquer uses recursion to split problems into independent subproblems.

Understanding Recursion: Functions That Call Themselves

找出其中不含有重复字符的 最长子串的长度。

[Leetcode 3] 无重复字符的最长子串

找出并返回这两个升序数组的中位数 。

[Leetcode 4] 两个排序数组的中位数

找字符串 s 中最长的回文子串。

[Leetcode 5] 最长回文子串

找出数组 height中的两条线，使得它们与 x 轴共同构成的容器可以容纳最多的水。

[Leetcode 11] 盛最多水的容器

查找字符串数组中的最长公共前缀。

[Leetcode 14] 最长公共前缀

[Leetcode 17] 电话号码的字母组合

返回满足条件且不重复的四元组 [nums[a], nums[b], nums[c], nums[d]] 

[Leetcode 18] 四数之和

[Leetcode 19] 删除链表的倒数第 N 个节点

[Leetcode 20] 有效的括号

将两个升序链表合并为一个新的升序链表并返回

[Leetcode 21] 合并两个有序链表

将所有升序链表合并到一个升序链表中

[Leetcode 23] 合并 K 个升序链表

每 k 个节点一组进行翻转，返回修改后的链表。

[Leetcode 25] K 个一组翻转链表

找出最长有效（格式正确且连续）括号子串的长度

[Leetcode 32] 最长有效括号

找出给定目标值在排序数组中的开始位置和结束位置。

[Leetcode 34] 在排序数组中查找元素的第一个和最后一个位置

n 个柱子，下雨之后能接多少雨水。

[Leetcode 42] 接雨水

匹配字符串 (s) 和字符模式 (p), 支持 '?' 和 '*' 

[Leetcode 44] 通配符匹配

给定一个不含重复数字的数组 nums，返回其所有可能的全排列 。

[Leetcode 46] 全排列

位于网格左上角的机器人总共有多少条不同的路径达到网格的右下角

[Leetcode 62] 不同路径

[Leetcode 79] 单词搜索

删除已排序的链表中所有重复的元素

[Leetcode 83] 删除排序链表中的重复元素

柱状图能够勾勒出来的矩形的最大面积。

[Leetcode 84] 柱状图中最大的矩形

[Leetcode 88] 合并两个有序数组

[Leetcode 92] 反转链表II

[Leetcode 101] 对称二叉树

[Leetcode 105] 从前序与中序遍历序列构造二叉树

[Leetcode 116] 填充每个节点的下一个右侧节点指针

[Leetcode 121] 买卖股票的最佳时机

[Leetcode 122] 买卖股票的最好时间 II

[Leetcode 123] 买卖股票的最佳时机 III

[Leetcode 124] 二叉树中的最大路径和

[Leetcode 126] 单词接龙 II

[Leetcode 128] 最长连续序列

[Leetcode 138] 随机链表的复制

[Leetcode 143] 重排链表

[Leetcode 146] LRU 缓存

给出链表的头结点 head ，请将其按 升序 排列并返回 排序后的链表 。

[Leetcode148] 链表排序

[Leetcode 160] 相交链表

[Leetcode 171] Excel 列名转换为数字

[Leetcode 179] 最大数

[Leetcode 200] 岛屿数量

给定整数 n ，返回 所有小于非负整数 n 的质数的数量 。

[Leetcode 204] 质数计数

[Leetcode 206] 反转链表

实现 Trie 类：初始化、插入字符串 、检索、前缀检索

[Leetcode 208] 实现 Trie

给定一个二叉树, 找到该树中两个指定节点的最近公共祖先。

[Leetcode 236] 二叉树的最近公共祖先 

大小为 k 的滑动窗口从数组的最左侧移动到数组的最右侧，返回 滑动窗口中的最大值 。