The Illusion of Continuity - Why Every Sensitive Request Needs Its Own Check The problem I built an IT helpdesk chatbot handling scripted multi-turn conversations, the kind where a caller states who they are once, early on: "I'm an admin on the finance team." Out of fifty scripted sessions, I built fifteen where the caller asks, mid-conversation,
The Gate That Only Ever Learned One Question The problem I had a fulfillment pipeline running with a quality gate sitting between an order-parsing agent and a warehouse-dispatch agent. I called it the inventory-check gate. It had a test suite, that suite ran on every change, and it had been passing clean for months. Everyone
The Gate That Learned to Downgrade Itself The Gate That Learned to Downgrade Itself The problem I built a six-step insurance claims pipeline, extract, validate, classify, price, approve, notify, and shipped it with quality gates at every transition, because the launch-era model held roughly 90% per-step accuracy, and six compounding steps at 90% each
The Frozen File - Keeping the CRM Export From Touching the Rules The Frozen File - Keeping the CRM Export From Touching the Rules The problem A sales-enablement tool generates each rep's daily account briefing by combining two very different kinds of text in one prompt. The first kind is fixed: always include a disclaimer, always use a three-section
The Fraud Model That Never Got a Rematch The Fraud Model That Never Got a Rematch I ran a fraud-scoring model against ninety days of e-commerce transaction traffic once, five thousand accounts, real enough patterns to matter. Around day forty-five, fraudsters started using a new device-fingerprint evasion technique. I'd already trained a
The Flattened Block - Carrying Metadata Into the Prompt Instead of Just Text The Flattened Block - Carrying Metadata Into the Prompt Instead of Just Text The problem An HR policy assistant I built for a 2,000-person company retrieved from three sources: the official employee handbook, an archive of individual managers' Slack and email guidance, and a benefits vendor portal export.
The Firewall Between the Number and the Words The Firewall Between the Number and the Words The problem Picture an auto insurer that built a claims-adjuster assistant. Feed it a claim record: the repair estimate, the deductible, the coverage cap, the depreciation schedule, the count of prior claims. Ask it to compute the payout per the policy
The Field That Renamed Itself Without Saying So The problem I built a partner-facing inventory-lookup agent that consumes a product-info API owned by a different internal team. Call it InvAgent. The client parsed fields directly by name, price and quantity available, with no version marker checked on either side of the connection. Midway through a
The Feature That Already Knew How the Loan Would Turn Out The Feature That Already Knew How the Loan Would Turn Out I built a retail lending risk model once whose only job was predicting ninety-day default probability. Two of its features were a borrower's average thirty-day balance and their count of late payments in the trailing
The Envelope That Told a Reviewer How Sure the Pipeline Was The problem I built an internal assistant for a procurement team that reviews vendor contract clauses and flags each one as low, medium, or high risk. Call it ContractCheck. Behind the API, a real pipeline runs: retrieve the relevant clause, extract its terms, classify the risk, and pass that classification
The Endpoint That Was Never in the Room The Endpoint That Was Never in the Room The problem I built a router for a loyalty-program chat assistant serving customers in the United States, Canada, and the European Union. Three model endpoints stood behind it, each with its own cost per thousand tokens, quality score, latency profile, and
The Elbow in the Curve - Where Extra Reasoning Stops Paying For Itself The Elbow in the Curve - Where Extra Reasoning Stops Paying For Itself The problem I had an internal agent estimating engineering effort from a written requirements doc, the kind of task where the model has to read a paragraph of ambiguous scope and turn it into a number of days.
The Drift Gate - Catching Budget Creep the Day It Happens The Drift Gate - Catching Budget Creep the Day It Happens The problem I set up a contract-summarization workflow to run cheap. A small model tier, a declared cost of $0.015 per document, and a team that felt good about the number because they had picked it deliberately. Then
The Dollar-Threshold Patch That Never Touched the Classifier The problem I was running a customer-support refund workflow built from four agents chained together: a Stage 3 eligibility classifier that labels each incoming ticket, a policy-matching agent that applies the refund rules for that label, an approval-routing agent that finalizes the decision, and a coordination layer
The Delta That Traveled Through Two Different Weeks The Delta That Traveled Through Two Different Weeks The problem I built an order-fulfillment agent, FulfillBot, that calls a flaky inventory-check tool, and shipped it with a retry-classification gate that decides whether a tool failure is a transient blip worth retrying or a systemic bug worth escalating,
The Defect Classifier With No Feature Vector to Check The Defect Classifier With No Feature Vector to Check I built a manufacturing visual defect-detection model once, classifying part images on an assembly line, with an injected gradual lighting-condition shift starting on day thirty-five, standing in for a camera housing that had started letting in more ambient
The Cycle Counter - Capping a Two-Agent Loop Before It Runs Away The problem I ran twenty synthetic pull requests through a code-review setup where a Reviewer agent and a Fixer agent work a queue together, like two coworkers who each think the other one is holding up the release. Most of the twenty resolve inside one or two passes. Reviewer
The Constraint That Needed Its Own Section The Constraint That Needed Its Own Section The problem I built a contract-review helper for a paralegal team, meant to summarize indemnification and liability clauses in plain language. The prompt I started with was one paragraph. Who the assistant is, what to do, the clause text itself, and the
The Confidence Ceiling - Capping What a Thin-Data Model Gets to Claim The problem I built a symptom-intake classifier for a telehealth triage flow. Feed it a description of what's wrong, and it sorts the case into routine, urgent, or emergency. The training set had a thousand synthetic cases, and nine hundred of them were the presentations you'
The Coarse Gate - Why Login-Level Permission Isn't Enough for a Shared Knowledge Base The Coarse Gate - Why Login-Level Permission Isn't Enough for a Shared Knowledge Base The problem I built an analytics copilot for a small consulting firm that shared one knowledge base across three clients' project data: CRM notes, tickets, and deliverables, all sitting in the same index
The Closest Match - Blocking a Duplicate Skill Before It Ships The Closest Match - Blocking a Duplicate Skill Before It Ships Picture a platform team running a DevOps agent with skills like restart-service, rotate-credential, and provision-vm. Different engineers write these in isolation from each other, and nothing at publish time checks whether a capability already exists under a
The Close Report That Could Not Say Who Was Wrong The problem I built a four-agent month-end close workflow for a finance back office: a data-extraction agent that pulls general-ledger entries, a matching agent that reconciles them against bank statements, a variance-explanation agent that drafts explanations for discrepancies over a threshold, and an approval-routing
The Claim Ticket - Making Case Ownership a Recorded Event The problem I built a telecom billing-dispute support system that routes disputed-charge cases through three agents in sequence: an Intake agent, a Billing agent, a Resolution agent. Forty synthetic cases, each one a customer disputing a charge, moving from one agent to the next as the case gets
The Chunk That Forgot What "This Limit" Meant The Chunk That Forgot What "This Limit" Meant Chunking a document sounds like the most boring possible step in a retrieval pipeline, right up until it quietly wrecks your retrieval accuracy. I built a developer-support retrieval agent once that answered questions against a thirty-chapter API reference
The Categorization Skill That Never Changed The Categorization Skill That Never Changed The problem An internal expense-report assistant I worked on started with exactly one job: categorize expense line items, meals, travel, software, other, against a fixed policy. It worked well, and it stayed simple because it only had to do the one thing. Then,
