diff --git a/AGENTS.md b/AGENTS.md index d3a9d51..86cd3d2 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -13,12 +13,14 @@ record; nothing here is scaffolding from before 2026-10-14. Time acts as the Gitea user `time` (its own token, TIME_TOKEN) for every write except comments and commit statuses, which stay with the Actions identity (`gitea-actions`); code goes in as git pushes. Seats post as themselves: a review by `haiku` is a Gitea review by the user `haiku` (one Gitea user per model line, TIME_SEAT_). - Rhythm: Astra (daily, 13:13 UTC) queues cards; the heartbeat (hourly, and on demand) builds `ready` cards with a + Rhythm: Astra (daily, 13:13 UTC) is the router: its seat judges every candidate card (kind, value, size) and + `router.py` ranks them with the owner's weights per kind in time `time/router.json` (mode dry: it posts the ranking on + the Astra log; live: it queues from the top and the heartbeat promotes in ranked order). The heartbeat (hourly, and on demand) builds `ready` cards with a seat, gets each PR reviewed by the council, and merges on approve + green CI, engine code included. Only the workflow directories (`.github/workflows/`) stay a human's merge: the CEO batches them. A card whose PR already exists (Codex, a chat, the CEO) is adopted: labelled `ready`, it is reviewed and landed, never rebuilt. Housekeeping sweeps daily (13:17). - Ventures: one a day, built for quality (`venture.yml` ticks every 6 hours, TIME_VENTURE=on); the day's card starts - once every other venture card is launched or held. Opus leads alone: a research round over the trending repos and the + Ventures: paused since 2026-10-19 (TIME_VENTURE=off; the launched ones are still measured) until the router starts + them (time#170). When on: one a day, built for quality; the day's card starts once every other venture card is launched or held. Opus leads alone: a research round over the trending repos and the studio's track record, one pick, the plan, the build (`claude:opus`) and the judging (a 1-10 score: under 8 earns polish rounds, then it launches with its score); sonnet drafts the launch posts. No fable. Batches (off) keep the board. Each venture lives at .yolopreneur.lol (gh-pages `ventures//`); the portfolio at yolopreneur.lol is gh-pages `ventures/index.html`, made by hand, and reads `ventures.json`.