Every post below is driven by data we can point at on disk — our own dogfood trip log first, then the loops, context overflows, and budget breaches our SDK catches inside customer apps. If a post's data isn't there yet, it stays gated. No vibes; no fabricated stats.
Cadence is a target, not a contract. If the gate hasn't opened, we slip the day rather than ship filler. The credibility of the 30-day series is the whole point.
The dogfood story: our own launch script looped against a shared upstream infra blocker. We instrumented the detector between failures. By the time the script retried a seventh time, the SDK opened the breaker before the API call went out.
Signups, installs, referrers, and star counts at the 24-hour mark — with delta columns against the launch hour. Honest about whether the launch sustained or fizzled.
A customer's agent looped. Our SDK opened the breaker. What the signature looked like, what the breaker defaults were, and what the customer's retry logic did next — anonymized, with permission.
Pattern-matching across 72 hours of customer trips. Categorized by trigger kind (loop / budget / context) and then by signature shape. One redacted example per category — code blocks, not prose.
When the breaker shouldn't have opened. What the user's legitimate workflow looked like, which default exposed the false positive, and whether we're shipping a version bump or a doc clarification.
Five days of npm install @runguard/sdk vs pip install runguard. Two integers, one ratio, and three plausible explanations — not a "the Python community prefers X" from a week of data.
The IDENTITY headline — "How we caught $X in runaway agent runs" — with the math shown. Customer-reported dollar figures where shared, token-pricing estimates otherwise, and every line tagged so readers can audit.
Three concrete things we'd do differently, with the planned fix for each. One thing we got right and want to keep. Honest about cadence — did the gates hold, did we slip a day, did we publish anyway and now regret it?
After day-7, the 30-day promise continues at a weekly cadence. Week-2 through week-4 stubs will be scaffolded once week-1 is actively publishing, so the structure matches what we've actually seen rather than what we imagined on day 0.
First post drops the hour RunGuard's launch channel fires. Stay close — or join the waitlist and we'll email when the SDK ships and the log starts.
