Meharban Singh

Meharban Singh

← portfolio

Notes on building and operating agentic systems.

Most writing about AI engineering is technique and theory — how to get an agent working. This is about operations: what happens after it ships, and what you do when it is confidently wrong. Everyone publishes what worked; this publishes what broke, and the rule it became.

Posts

  • I Built an AI Software Factory. Here Are the Failure Modes Nobody Puts in the Demo. How a real multi-agent build system fails: stale state, tests that can't turn red, reviewers agreeing without new evidence, and what fixed it.
  • 'Done' Is a Claim, Not a Fact An installer shipped green with two unsubstituted placeholders. The fix that closed it required a different verifier, a RED/GREEN probe, and a database that refuses self-certified closes.
  • The Writer Never Approves An orchestrator wrote 2,968 lines directly, then reviewed its own work. A bug in its own checker survived that review. What the role lock that followed actually changed.
  • The Day I Rotated 15 Credentials A names-only secrets listing printed real values into a transcript, a redaction attempt made it worse, and the rule written afterward was broken again six days later.
  • Shipping in a Domain I Knew Nothing About Building Astro Rattan meant shipping Vedic astrology without knowing the subject. The fix: take the model out of the answer path and let an expert verify.
  • I Don't Prompt AI. I Run a Factory. A blueprint reviewed by a second model, hooks that block instead of advise, gates that read evidence not summaries, and a sentinel watching production — measured against 893 tracked issue rows.
  • An Instruction Is Not a Guarantee Why a spec isn't enough once an agent does real implementation — and the process (skills, hooks, gates, independent review) I built around Claude Code instead.

Each post takes one real incident from the issue ledger — the failure, the root cause, and the rule or hook it became.

The ledger, right now

55 projects in the registry
893 tracked issue rows
22 (2.5%) reported by a human user — the machine caught the rest
557 closed · 544 (97.7%) verified by a different agent than the fixer · 0 self-verified
225 found by the production sentinel after go-live
1,160 evidence rows · 3,741 audit-trail events

Read from a live SQLite database (factory_rules/factory.db) at 2026-08-31T22:07Z (2026-09-01 03:37 IST). The ledger is written to continuously, so this is a point-in-time read — the counts have moved on since.

This blog runs through the same loop it writes about: every post passes a pre-publish gate that scans for secrets and refuses any number that isn't traceable to a recorded source.