Time already has a seed path on github.com/teahubxyz/time (venture day seed-idea mode: skip the vote, keep the planning counsel; AICharts was the first seed, deployed by labs-aicharts.yml to Cloudflare). What's missing is the second half: a seeded venture must land on prod as a first-class thing, not only as a Pages folder on GitHub.
Define "landing":
A seed is an issue on time labelled seed (title = venture name, body = the idea, optional domain). Time runs the normal plan → build → check stages but skips the vote. That part exists; verify it still works after the audit fixes (#45/#46 on time).
When a seed launches, Time also creates its home on prod: an org on teahub.xyz named after the venture, with a site repo holding the built page and a README with the LAUNCH.md. This needs one prod credential on Time's side (a Gitea token for a time seat user, scoped to org/repo creation) — that is a secret on GitHub, not on prod; record it in docs/decisions.md.
The venture's domain (if given) points at the org's site (pages model, #2), not at time's gh-pages.
AICharts is the test: re-seed it, watch it land as org aicharts on prod with its site live on its domain.
DONE: seed label + flow documented in time's SKILL.md; aicharts org exists on prod with site + README created by Time, domain live; decision line for the time seat token. Send to @review.
Time already has a seed path on github.com/teahubxyz/time (venture day seed-idea mode: skip the vote, keep the planning counsel; AICharts was the first seed, deployed by `labs-aicharts.yml` to Cloudflare). What's missing is the second half: a seeded venture must **land on prod** as a first-class thing, not only as a Pages folder on GitHub.
Define "landing":
1. A seed is an issue on `time` labelled `seed` (title = venture name, body = the idea, optional domain). Time runs the normal plan → build → check stages but skips the vote. That part exists; verify it still works after the audit fixes (#45/#46 on time).
2. When a seed launches, Time also creates its home on prod: an org on teahub.xyz named after the venture, with a `site` repo holding the built page and a `README` with the LAUNCH.md. This needs one prod credential on Time's side (a Gitea token for a `time` seat user, scoped to org/repo creation) — that is a secret on GitHub, not on prod; record it in docs/decisions.md.
3. The venture's domain (if given) points at the org's `site` (pages model, #2), not at time's gh-pages.
4. AICharts is the test: re-seed it, watch it land as org `aicharts` on prod with its site live on its domain.
DONE: seed label + flow documented in time's SKILL.md; `aicharts` org exists on prod with site + README created by Time, domain live; decision line for the time seat token. Send to @review.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Time already has a seed path on github.com/teahubxyz/time (venture day seed-idea mode: skip the vote, keep the planning counsel; AICharts was the first seed, deployed by
labs-aicharts.ymlto Cloudflare). What's missing is the second half: a seeded venture must land on prod as a first-class thing, not only as a Pages folder on GitHub.Define "landing":
timelabelledseed(title = venture name, body = the idea, optional domain). Time runs the normal plan → build → check stages but skips the vote. That part exists; verify it still works after the audit fixes (#45/#46 on time).siterepo holding the built page and aREADMEwith the LAUNCH.md. This needs one prod credential on Time's side (a Gitea token for atimeseat user, scoped to org/repo creation) — that is a secret on GitHub, not on prod; record it in docs/decisions.md.site(pages model, #2), not at time's gh-pages.aichartson prod with its site live on its domain.DONE: seed label + flow documented in time's SKILL.md;
aichartsorg exists on prod with site + README created by Time, domain live; decision line for the time seat token. Send to @review.