---
schema: 1
type: video
title: >-
  Every Solo Agent Builder Eventually Reinvents a Worse Version of CI/CD -
  Sumaiya Shrabony
description: >-
  If you build agents alone long enough, you will independently reinvent five
  things software engineering solved decades ago. A way to test whether your
  agent's output is still correct after you changed something. A way to run it
  on a schedule and know if it failed. A way to prevent one skill's schema
  change from silently breaking three downstream skills. A way to roll back when
  today's run produces garbage. A way to validate outputs before they hit
  production. You just reinvented regression testing, cron monitoring, contract
  testing, version control, and staging. Badly. Without realizing it. The
  dangerous failure in an agent system is not bad output. Bad output is easy to
  catch. The dangerous failure is a polished artifact that looks ready but
  violates a production contract: it uses the wrong voice patterns, makes an
  unverified claim, repeats an old angle, and gets labeled "READY TO PUBLISH"
  anyway. That is the agent equivalent of shipping because the code compiled,
  even though the tests never ran. This talk uses a real, open-source 19-skill
  Claude Code agent system (github.com/safrin96/agentic-content-system) as the
  case study. Through an interactive live demo, I show three ways an agent
  system silently lies to you and what a boundary looks like that catches it.
  The takeaway is simple: the infrastructure gap in the agent ecosystem is not
  another framework. It is the equivalent of what CI/CD gave software teams in
  2015, a standard, boring, reliable way to test, deploy, and roll back agent
  behavior. Before you add another agent, add one boundary. Speakers: - Sumaiya
  Shrabony: Sumaiya Shrabony is a Technical Program Manager, enterprise AI
  practitioner, and content creator across LinkedIn, Instagram
  (@thedata_ai.girl), and Substack (Ground Truth) building toward thought
  leadership at the intersection of enterprise data infrastructure, AI adoption,
  and the immigrant-in-tech experience. LinkedIn:
  https://www.linkedin.com/in/sumaiya-shrabony GitHub:
  https://github.com/safrin96
canonical: >-
  https://liquidgold.cc/channel/aidotengineer/explore/video/every-solo-agent-builder-eventually-reinvents-a-wor-1725c7bfda9b
markdown: >-
  https://liquidgold.cc/channel/aidotengineer/video/every-solo-agent-builder-eventually-reinvents-a-wor-1725c7bfda9b.md
llms: null
parent: 'https://liquidgold.cc/channel/aidotengineer.md'
channel: aidotengineer
updated: '2026-10-24T08:15:41.985Z'
language: null
children: []
videoId: WLXxTaPagA8
durationSeconds: 651
publishedAt: '2026-07-11T16:30:04.000Z'
searchChunks:
  - ordinal: 0
    text: null
    startSeconds: 0
    endSeconds: 11
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=0'
    heldReason: rights
  - ordinal: 1
    text: null
    startSeconds: 11
    endSeconds: 144
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=11'
    heldReason: rights
  - ordinal: 2
    text: null
    startSeconds: 11
    endSeconds: 144
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=11'
    heldReason: rights
  - ordinal: 3
    text: null
    startSeconds: 144
    endSeconds: 155
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=144'
    heldReason: rights
  - ordinal: 4
    text: null
    startSeconds: 155
    endSeconds: 263
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=155'
    heldReason: rights
  - ordinal: 5
    text: null
    startSeconds: 155
    endSeconds: 263
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=155'
    heldReason: rights
  - ordinal: 6
    text: null
    startSeconds: 274
    endSeconds: 354
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=274'
    heldReason: rights
  - ordinal: 7
    text: null
    startSeconds: 365
    endSeconds: 476
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=365'
    heldReason: rights
  - ordinal: 8
    text: null
    startSeconds: 365
    endSeconds: 476
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=365'
    heldReason: rights
  - ordinal: 9
    text: null
    startSeconds: 487
    endSeconds: 624
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=487'
    heldReason: rights
  - ordinal: 10
    text: null
    startSeconds: 487
    endSeconds: 624
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=487'
    heldReason: rights
  - ordinal: 11
    text: null
    startSeconds: 635
    endSeconds: 651
    watch: 'https://liquidgold.cc/watch/WLXxTaPagA8?t=635'
    heldReason: rights
---


# Every Solo Agent Builder Eventually Reinvents a Worse Version of CI/CD - Sumaiya Shrabony

If you build agents alone long enough, you will independently reinvent five things software engineering solved decades ago. A way to test whether your agent's output is still correct after you changed something. A way to run it on a schedule and know if it failed. A way to prevent one skill's schema change from silently breaking three downstream skills. A way to roll back when today's run produces garbage. A way to validate outputs before they hit production. You just reinvented regression testing, cron monitoring, contract testing, version control, and staging. Badly. Without realizing it. The dangerous failure in an agent system is not bad output. Bad output is easy to catch. The dangerous failure is a polished artifact that looks ready but violates a production contract: it uses the wrong voice patterns, makes an unverified claim, repeats an old angle, and gets labeled "READY TO PUBLISH" anyway. That is the agent equivalent of shipping because the code compiled, even though the tests never ran. This talk uses a real, open-source 19-skill Claude Code agent system (github.com/safrin96/agentic-content-system) as the case study. Through an interactive live demo, I show three ways an agent system silently lies to you and what a boundary looks like that catches it. The takeaway is simple: the infrastructure gap in the agent ecosystem is not another framework. It is the equivalent of what CI/CD gave software teams in 2015, a standard, boring, reliable way to test, deploy, and roll back agent behavior. Before you add another agent, add one boundary. Speakers: - Sumaiya Shrabony: Sumaiya Shrabony is a Technical Program Manager, enterprise AI practitioner, and content creator across LinkedIn, Instagram (@thedata_ai.girl), and Substack (Ground Truth) building toward thought leadership at the intersection of enterprise data infrastructure, AI adoption, and the immigrant-in-tech experience. LinkedIn: https://www.linkedin.com/in/sumaiya-shrabony GitHub: https://github.com/safrin96

Canonical: https://liquidgold.cc/channel/aidotengineer/explore/video/every-solo-agent-builder-eventually-reinvents-a-wor-1725c7bfda9b · Channel: [AI Engineer](https://liquidgold.cc/channel/aidotengineer.md)

> Search chunk text is held until public-source provenance is verified.

## Document chunks

> Missing: no stored document chunks are available.
