Hurl
Production Traffic Is the Spec
Legacy code has no documentation. No tests either. And yet it's running right now. A month of well-recorded logs is the spec — build Hurl integration tests that capture the current behavior from production traffic, and you can pin down what the legacy does and lay a safety net for refactoring without reading a single line of code.
Class 11. How to Rescue a Broken Vibe-Coded App
Your vibe-coded app just broke. You don't need to rebuild it. Diagnose it, lock it down, and step out one move at a time.
huma -- A Ratchet That Never Skips an Endpoint
When you ask an AI agent to test 42 endpoints, it declares 'done' around the 15th. huma turns the endpoint list into a ratchet session so the agent cannot skip a single one. scan, next, write, verify. Four commands, zero config.
Class 3. Apps That Don't Break — Hurl, Git, CI/CD
Declare API contracts with Hurl, create save points with Git, automate verification with CI/CD. When the three combine, they become a ratchet — a gear that only moves forward and never backward.
Reins Engineering — AI with Reins
Harness engineering is a fence. It keeps the agent from going outside, but doesn't ensure it reaches the destination. Reins Engineering is the reins — steer with deterministic contracts, lock with ratchets, separate decisions from implementation.
Hurl Stops Vibe Coding Drift
Vibe coding collapses under logic drift within 3 months. CMU, METR, DORA, and Amazon cases prove it. Declare API contracts in plain text with Hurl and lock them with a ratchet -- you suppress drift structurally without limiting AI's freedom.