From 26479e7d47b2f88bf4147f29699dbbee7509e9b9 Mon Sep 17 00:00:00 2001 From: teahubxyz Date: Sun, 11 Oct 2026 15:56:59 -0700 Subject: [PATCH] Pages: a landing page for Time --- index.html | 258 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 258 insertions(+) create mode 100644 index.html diff --git a/index.html b/index.html new file mode 100644 index 0000000..2a63f31 --- /dev/null +++ b/index.html @@ -0,0 +1,258 @@ + + + + + +Time · an agent factory that lives in your GitHub repo + + + + +
+
+ + + TIME + + +
+ +
+
+
Drawing 01 · a GitHub-native agent factory
+

Label an issue.
Get a merged PR.

+

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.

+
+ Use this template → + See it work ↓ +
+

Free and open on GitHub. You bring a Venice API key for the seats; runners are GitHub's.

+
+
+
Fig. 1 · card #7, as it ran
+ 
# 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
+
+
+
+ +
+
+
Drawing 02 · the loop
+

One spec in, merged cards out

+

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.

+
+ + + + + + + + + spec issuelabel: spec + plannercards + deps + workera seat with hands + PR"Closes #N" + reviewerApprove/Object + auto-mergechecks green + + + + + merged → the next card starts + + + needs-human + objection · red checks · protected paths + + one Actions run per beat · every beat is a comment on the card + + +
Clock GitHub Actions: hourly, and right away on labels and reviewsBrains Venice seats: Kimi, Grok, Qwen, DeepSeek, GLM, GeminiLedger the issue thread
+
+
+
Seats

@mention a model

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.

+
Hands

The worker codes

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.

+
Updates

One engine, many repos

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.

+
+
+
+ +
+
+
Drawing 03 · receipts
+

Proof, not promises

+

This repo's own history, nothing staged and nothing smoothed over. Click through: every step is a public comment.

+
    +
  • Spec#5 was labelled spec; the planner split it into cards #6 and #7, the second waiting on the first.
    • +
  • First card#6 hit four setup problems on its way (a model without tool calling, Actions not yet allowed to open PRs, no CI check, a missing permission). Each was fixed in the engine or the settings, and the card was retried with /time retry. Then Qwen opened PR #9, Grok approved it, and Time merged it.
    • +
  • Second card#7 was promoted the moment #9 merged. Qwen opened PR #10 a minute later, Grok approved, and Time merged it and closed the card. No human comment, label or click on the card or its PR.
    • +
  • VenturesThe same machinery runs a small venture studio: it reads what's trending on GitHub, the seats pitch and vote, write a launch plan, build the page and measure signups. See the ventures →
    • +
+
+
+ +
+
+
Drawing 04 · start
+

Running in four steps

+
    +
  1. Use the template. Create your copy of teahubxyz/time; it's yours, public or private.
    2. +
  2. Give the seats a key. gh secret set VENICE_API_KEY
    3. +
  3. Turn it on. gh variable set TIME_MODE --body live, TIME_WORKER --body "venice:qwen coder", TIME_REVIEW --body venice:grok, and TIME_AUTOMERGE --body on when you're ready to let it merge.
    4. +
  4. Write a spec. Open an issue that lists the cards, each with a DONE: line, and label it spec. Watch the thread.
    5. +
+

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.

+
+
+ +
+
+
Drawing 05 · tolerances
+

Honest limits

+
    +
  • The seats are as good as the models behind them. Small, well-scoped cards with a clear DONE: line work best.
    • +
  • You pay Venice for the seats. GitHub's runners are free for public repos and metered for private ones.
    • +
  • GitHub won't let Actions edit workflow files, so changes there (and anything under paths you protect) wait for a human.
    • +
  • Dry-run is the default and there is a daily cap; turning on auto-merge is your call, per repo.
    • +
  • On a public repo, only you and your collaborators can trigger seats or count as a reviewer. Never attach a self-hosted runner to a public repo.
    • +
  • It's young software: the engine changes weekly, and the update pull request tells you what changed.
    • +
+
+
+ +
+
+
Drawing 06 · output
+

Latest ventures

+

Built and launched by the venture loop on this repo; each one decides its own future after seven days of signups.

+ +
+
+ + + + + +