The Assistant That Remembered Too Much —Retesting an AI Agent After a Memory UpgradeNote on this case study: The company, team, and numbers below are an illustrative composite built from publicly documented failure patterns. They do not describe a named BotGauge customer. TL;DR A sa2d ago · 10 min readvivekchhediya.hashnode.dev
The Day the Approval Step Went Away — Retesting an AI Agent After Its Autonomy ExpandedTL;DR An IT-provisioning agent had earned the team's trust over three months of supervised work. So the team proposed the obvious next step: stop asking a human to approve the routine requests. No new1A2d ago · 11 min readvivekchhediya.hashnode.dev
37 Agents, One Platform Team, and a Matrix That Decided How Much Testing Each Change DeservedBackground "Tessellate Health Systems" is a fictional mid-size company that had adopted AI agents the way many organizations do: from the bottom up. A finance team built a reconciliation agent. Custom2d ago · 10 min readvivekchhediya.hashnode.dev
The Knowledge Base That Talked BackBackground "Foxglove Logistics" is a fictional company with about 4,000 employees. Its internal helpdesk agent, nicknamed "Fern," handles questions on three topics: IT access, expense policy, and time3d ago · 9 min readvivekchhediya.hashnode.dev
The Coding Agent, the Code Freeze, and the Command Nobody ApprovedBackground "Brightline Payments" is a fictional payments-processing company with a platform team of about a dozen engineers. Like many teams in 2026, they adopted a coding agent early. It was not a to3d ago · 9 min readvivekchhediya.hashnode.dev
