Time lives in your repository. Issues are the ledger, GitHub Actions is the clock, and AI seats plan the work, write the code and review it; Time merges what passes. A human steps in only where it matters: objections, red checks, and the paths you protect.
Free and open on GitHub. You bring a Venice API key for the seats; runners are GitHub's.
# written by the planner from spec #5 Add a `## Status` section at the end of README.md that links to CHANGELOG.md Part of #5 (step 2/2). Depends on #6. DONE: README.md links to CHANGELOG.md # the thread ⏱️ #6 merged: queued → ready ⏱️ qwen is working on this now ⏱️ qwen opened PR #10 (13 steps) ✔ grok: Approve ⏱️ approved and green, merged PR #10
Write a spec as an issue and label it spec. Time splits it into cards with dependencies, runs them one at a time,
and pulls the next card the moment one merges. Every step is a comment on the card, so the ledger is the issue thread itself.
Write @grok, @kimi high or @qwen max in any issue or PR and that seat answers in the thread. Only you and your collaborators can summon them.
A seat edits the repo on its own branch, runs the tests on a runner, and opens the PR itself. Workflow files and secrets stay out of its reach.
Every copy gets a weekly pull request with the latest engine from teahubxyz/time, the way a CMS updates itself, so projects don't drift.
This repo's own history, nothing staged and nothing smoothed over. Click through: every step is a public comment.
spec; the planner split it into cards #6 and #7, the second waiting on the first./time retry. Then Qwen opened PR #9, Grok approved it, and Time merged it.DONE: line, and label it spec. Watch the thread.Or open your copy in Claude Code and say "set up Time": the setup skill in .claude/skills/time walks through it, and the Doctor workflow checks labels, settings and keys.
DONE: line work best.Built and launched by the venture loop on this repo; each one decides its own future after seven days of signups.