teahubxyzandClaude Opus 5.5
32fa6ee49d
The schedule starts one venture card a day, and Run workflow only advanced the cards already open. Run workflow now has a "Start a new venture now" checkbox (gh workflow run venture.yml -f start=true) that opens a fresh card even when today's has run; a second card on the same day is titled "Venture <day> (2)". The schedule is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UpT7eWzeLhRwuYmsSQnbRb
2.0 KiB
2.0 KiB
Changelog
[Unreleased]
Security
- A venture build writes only inside its own
ventures/<slug>/folder on the Pages branch, which also carries the studio's site and every other venture: a fix round once wrote its page over the site's front page. - The Venice worker's shell no longer sees secrets: its environment drops tokens and keys, its checkout keeps no token in
.git/config, and the workflows check out without persisted credentials.
Added
- Venture loop launches products, not pages: a launch round where board seats write plans and one synthesizes
LAUNCH.mdwith attribution; launch pages where the working product fills the first screen under a slim header with one call to action, then pricing and honest limits, in a look that follows the product; early-access signups through a GitHub issue form, thanked on their issues; deterministic and headless-Chrome checks with fix rounds and an andon; a 7-day decision against success and kill lines; a studio index at/ventures/. - Start a venture whenever you like: Actions → venture → Run workflow → "Start a new venture now" (
gh workflow run venture.yml -f start=true); the schedule still starts one a day. - The board's taste: a delight anyone gets within a minute ranks above another developer utility, and when a product makes something people read (a deck, a card), its preloaded sample is the product's own pitch.
- The studio index at
/ventures/wears the Time site's blueprint theme (title block, grid paper, type), with each launched venture's laptop screenshot. - The headless-Chrome check fails a launch page where something sits on top of the product (a page fixed to the screen's height lets the next section slide over it).
- The board sees the studio's own ventures: pitches that repeat one (by slug, name or an earlier slug) are set aside before the vote, since the week's trending list barely moves from day to day.
- Hands-off upgrade support with spec planner, auto-merge, and Venice worker integration