TL;DR: Cronos — my open-source methodology for human-validated vibe coding — just shipped v2.1. It's the first release grounded in production evidence: four full cycles on real systems at a regulated SaaS company, and every amendment in the release cites the cycle that forced it. Here's the tour.
What Cronos is, in one paragraph
Five-day engineering cycles where an AI agent does the heavy implementation and humans hold the gates: a plan approved before any code (Gate 1), an independent human validation before any ship (Gate 2). v2.0 defined the loop. v2.1 fixes what production broke — and adds the layer v2.0 was missing.
What's new in v2.1
The rhythm is no longer Monday–Friday. A cycle is five relative working days — D1 through D5 — starting any day; weekends and holidays pause the clock. A Thursday start runs Thu, Fri, Mon, Tue, Wed. Kickoff on D1, Path Sync D2, verification D4, demo + release decision D5. The fixed five-day length stays: calendar independence is not permission to stretch to six.
