Venture loop: launch products, not pages
Ported from the notplanned venture template: - launch round: every board seat writes a launch plan (positioning, first users, pricing, channels, 7-day success and kill lines); one seat synthesizes them into LAUNCH.md with where each idea came from - launch page brief: one primary call to action in the hero, the working product preloaded with a sample, why-this-exists with real star counts, pricing (free plus at most two honest early-access tiers), honest limits, a design direction that rotates and never repeats the last six - signups through a GitHub issue form prefilled with venture and plan; each signup is thanked on its own issue - checks: deterministic gates, then headless Chrome measuring at exactly 390x844 and 1280x800 (horizontal scroll, button below the fold, JS errors); two fix rounds, then andon with needs-human and /time retry - a contact-sheet screenshot of phone and desktop on the card - 7-day decision on distinct people: v2 card, kill, or one more week then park; a next version counts only signups after its own launch - scheduling: a card that is measuring never blocks the others; one new card a day; a tick runs light stages back to back and one worker run - the studio index at /ventures/ is generated from ventures.json Security: the worker's shell no longer sees tokens or keys, its checkout keeps no token in .git/config, and workflows don't persist credentials. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UpT7eWzeLhRwuYmsSQnbRb
This commit is contained in:
1 parent
66c427eba4
commit
cdfe4c7199
9 files changed
+1328
-163
No files matched your search
@@ -6,7 +6,7 @@ A GitHub-native agent factory. GitHub is the ledger, GitHub-hosted runners are t
|
||||
- **Heartbeat** (`heartbeat.yml`, hourly and whenever a card is labelled `ready`): moves cards forward. In `dry-run` (default) it only says what it would do; with `TIME_MODE=live` it dispatches each card to the worker (`TIME_WORKER`: a Venice seat such as `venice:kimi`, which edits the repo and opens the PR itself, or a Cursor cloud agent), which opens a PR that closes the card. An optional reviewer (`TIME_REVIEW`) checks the PR. At most `TIME_DAILY_CAP` launches a day.
|
||||
- **Mentions** (`mention.yml`): `@kimi`, `@grok 4.7`, `@qwen max high` in any issue, PR or comment gets that seat's reply (Venice).
|
||||
- **Hands-off** (`TIME_AUTOMERGE=on`): label an issue `spec` and Time splits it into cards that run one at a time. A card's PR merges itself once the reviewer approves and checks are green, then the next card starts. Objections, red checks and protected paths (workflows, deploy, secrets) go to a human.
|
||||
- **Venture loop** (`venture.yml`, every 20 min once `TIME_VENTURE=on`): scouts the repos that gained the most stars this week, seats pitch one small static-page product each, the board votes (Borda), a seat builds it on `gh-pages`, and GitHub Pages ships it at `/ventures/<slug>/`. One card per venture (label `venture`), progress as comments.
|
||||
- **Venture loop** (`venture.yml`, every 20 min once `TIME_VENTURE=on`): one venture card a day. It scouts the repos that gained the most stars this week; seats pitch; the board votes (Borda, quorum of two); every board seat writes a launch plan (positioning, first users, pricing, channels, 7-day success and kill lines) and one seat synthesizes them into `LAUNCH.md`; the worker builds a launch page around a working product on `gh-pages` in its own design direction; deterministic checks and headless Chrome (phone and desktop) gate it, with two fix rounds before an andon; GitHub Pages ships it at `/ventures/<slug>/`. Signups go through an issue form (`.github/ISSUE_TEMPLATE/early-access.yml`), each one thanked on its issue; after 7 days the count of distinct people decides: build v2, kill, or watch a week more. The studio index lives at `/ventures/`. Launch posts are drafts for a human; nothing is posted outside the repo.
|
||||
- **Doctor** (`doctor.yml`, manual): runs the tests and checks label, settings and keys.
|
||||
- **Update** (`update.yml`, weekly or manual): opens a PR with the latest engine from teahubxyz/time, so every project stays on one Time instead of drifting copies.
|
||||
|
||||
|
||||
Reference in new issue
Block a user