Medium

Precious Chindongo Thundu

236 followers

Featured Book

The Ultimate Small Business SEO Handbook 2023: Unlocking the Power of Search Engines

This book is a comprehensive guide to small business SEO, covering everything from the basics to advanced techniques.

2023

Precious Chindongo Thundu

Stories

Pinned

Precious Chindongo Thundu

Sep 10

Don’t Blame the Model. Demand a Trace First.

When agents fail in production, guessing is malpractice. Use the Trace-Before-Blame Rule before you swap models or rewrite prompts.

Flat editorial illustration of tangled agent logs unraveling into a clean timeline with one mint-highlighted span, ink navy background

Pinned

Precious Chindongo Thundu

Sep 9

Stop Dumping Context Between Agents. Enforce a Handoff Contract.

Multi-agent demos die at the boundary. Ship a schema, a status field, and a reject path before you grow the swarm.

Bauhaus geometric handoff diagram: sealed envelope passing between two agent desks with a stamped contract checklist

Pinned

Precious Chindongo Thundu

Sep 11

Stop Retrying Agent Writes Blindly. Require an Idempotency Key.

Durable agents resume mid-run. Without a key, every retry is a second side effect waiting to happen.

Precious Chindongo Thundu

Oct 26

I Shipped 3 Changes to One MCP Tool Schema Under 400 Live Agent Sessions

Refreshing on list_changed still let 1,417 deals go out wrong in my seeded toy. A 5-minute TTL left 40. Pinning a contract hash on each…

Patent-office style drawing sheet in black ink on aged cream paper. Header: toy test, seed 1026, 400 agent sessions. Headline: The field was renamed mid-session. Below: 1,633 deals lost their lead source. No call failed. No alert fired. A red stamp reads MCP tool schema, contract pinned, 0 wrong deals. On the right, two hatched index cards, create_deal v1 with source struck through and create_deal v4 with lead_source and consent_basis, are pierced by one long pin labelled contract hash.

Precious Chindongo Thundu

Oct 23

How Ad Agents Overspend 100x Without Breaking a Budget Cap

Micros, minor units and whole units share field names. In 3,000 toy changes, name-keyed caps let 48 land at 100x. A cap on the wire request…

Letterpress public notice on aged newsprint, black and red wood type. Headline: One budget. Below, R500 a day is set down as three red numbers in boxes: 500000000 for Google Ads micros, 50000 for Meta minor units, 500 for a wrapper in whole rand. Tagline: The cap read one. The platform got another. Red banner: 48 changes landed at 100x. Every one passed the cap. Footer: toy test, seed 1023, 3,000 agent budget changes, a cap on the wire request let 0 through.

Precious Chindongo Thundu

Oct 22

Skip or Catch Up Is the Wrong Question for Missed Agent Runs

In 30 toy days, dropping missed runs lost 6 of 35 owed reports, replaying them sent 7,600 emails late, and one catch-up still sent 5,200. A…

Chalkboard on green slate in a wooden frame. Skip or catch up? is chalked and crossed out, with Wrong question. in yellow below. A chalk clock reads 22:19, labelled 8 AM digest, host woke 22:19. A rota: Covered, CRM sync missed x66, run the latest once; Stale, 8 AM digest, window shut, skip it, tell the owner; Owed, spend export missed x2, run both, oldest first. Footer: 30 toy days, seed 2210, drop lost 6 of 35 owed, replay-all 7,600 late emails, slot ledger 0.

Precious Chindongo Thundu

Oct 22

Plan Mode Is Only as Read-Only as the Credential Behind It

Tool names, readOnlyHint and allow-lists all leak, and stricter prompts leak more. In 2,000 toy sessions, read-only keys plus write capture…

Plan Mode Is Only as Read-Only as the Credential Behind It

Precious Chindongo Thundu

Oct 21

Which Runs First, the Opt-Out or the Send? Parallel Tool Calls Don't Say

Run concurrently, my toy agent mailed 2,240 of 2,875 people who opted out in the same batch. In model order: 372. Running revokes before…

Layered paper-cut illustration on moss green. A cream card reads: Which runs first: the opt-out or the send? Kicker: parallel tool calls, toy harness, seed 2110. A red and white level-crossing barrier is down, green lamp lit; three envelope cards marked send wait behind it, while two pink OPT-OUT, committed first cards have passed along an ochre road. Footer: concurrent 2,240 opted-out people mailed, in model order 372, revokes before acts 0 at 1.21x latency.

Precious Chindongo Thundu

Oct 21

Context Compaction Kept the Hold and Wrote “Approved” Over It

Pinning constraints saves the rule, not who lifted it. In my toy, all 2,940 pinned holds stayed visible and 1,724 held sends still went out…

Pixel-art cover, navy night sky. Headline: Compaction kept the hold and wrote "approved" over it. A conveyor feeds a HOLD c3 tile (user, 09:15), a blue subagent REVIEW tile and a tool-output block into a press marked COMPACT. The output summary card reads c3 drafted, c3 reviewed, a green APPROVED stamp and user release: none, under a pinned HOLD c3 note. An envelope flies out: SENT 14:08. Footer: pinned holds visible 2,940/2,940, unapproved sends 1,724, typed release 0.

Precious Chindongo Thundu

Oct 20

Featured Book

Stories

Don’t Blame the Model. Demand a Trace First.

When agents fail in production, guessing is malpractice. Use the Trace-Before-Blame Rule before you swap models or rewrite prompts.

Stop Dumping Context Between Agents. Enforce a Handoff Contract.

Multi-agent demos die at the boundary. Ship a schema, a status field, and a reject path before you grow the swarm.

Stop Retrying Agent Writes Blindly. Require an Idempotency Key.

Durable agents resume mid-run. Without a key, every retry is a second side effect waiting to happen.

I Shipped 3 Changes to One MCP Tool Schema Under 400 Live Agent Sessions

Refreshing on list_changed still let 1,417 deals go out wrong in my seeded toy. A 5-minute TTL left 40. Pinning a contract hash on each…

How Ad Agents Overspend 100x Without Breaking a Budget Cap

Micros, minor units and whole units share field names. In 3,000 toy changes, name-keyed caps let 48 land at 100x. A cap on the wire request…

Skip or Catch Up Is the Wrong Question for Missed Agent Runs

In 30 toy days, dropping missed runs lost 6 of 35 owed reports, replaying them sent 7,600 emails late, and one catch-up still sent 5,200. A…

Plan Mode Is Only as Read-Only as the Credential Behind It

Tool names, readOnlyHint and allow-lists all leak, and stricter prompts leak more. In 2,000 toy sessions, read-only keys plus write capture…

Which Runs First, the Opt-Out or the Send? Parallel Tool Calls Don't Say

Run concurrently, my toy agent mailed 2,240 of 2,875 people who opted out in the same batch. In model order: 372. Running revokes before…

Context Compaction Kept the Hold and Wrote “Approved” Over It

Pinning constraints saves the rule, not who lifted it. In my toy, all 2,940 pinned holds stayed visible and 1,724 held sends still went out…

When Clocks Fall Back, Agent-Booked 9 AM Sends Go Out at 8

An offset is not a time zone. In my toy, agents that froze it at plan time sent 1,519 of 9,000 sends an hour off. Wall clock plus zone…

Precious Chindongo Thundu