Skip to content

project(public-launch): Public Launch — the project-spec (never merged) - #2585

Draft
jhoffner wants to merge 1 commit into
mainfrom
project/public-launch
Draft

jhoffner wants to merge 1 commit into
mainfrom
project/public-launch

Conversation

@jhoffner

@jhoffner jhoffner commented Oct 1, 2026

Copy link
Copy Markdown
Collaborator

Public Launch takes FSD from "the framework runs" to "a stranger can install it, build with it, and not be hurt by it". This PR is the project's standing spec. It is never merged and stays open for the life of the project. It replaces #2359, which was merged by mistake on 2026-09-29 (cleanup on main: #2392). It is a draft so it can't be merged again. As of 2026-10-01 · head 960934c4.

Winning when A stranger goes from one command to a working app streaming from a real model, in a new or existing project, without cloning our repo. Every public package installs and imports from npm, and there is no known cross-user leak or silent data loss
The read Five checks of "launched" from a clean machine: packages import · one command to a streaming app · a first flow from docs alone · no open hard gate · the showcase paths run on the public deploy (working, not polished: PD-2). None shown from npm yet
Now 1 done · 1 in flight · 2 not filed. Hard gates wrapped on Oct 1
Kill line If the hard-gates list grows faster than it closes, shrink the cut (a 0.x release to a small cohort). Don't relax the gates

The territory: four launch tracks inside the project, the framework's own projects as substrate below a fence with simplification the one the launch waits for, and polish, parked bets and post-launch growth outside

The fence asks whether a stranger would hit it, or be harmed by it, the day the doors open. Anything else ships on its own project's timeline, except framework simplification, which the launch waits for.

The arc: the first hour in flight since Aug 20, hard gates closed Sep 29 to Oct 1, two unfiled lanes, the now line at Oct 1

Hard gates closed in three days. The first hour is now the only open bar, and it is what the launch cut waits on.

The epics (live table): FIX-1161 first hour, in flight · FIX-1635 hard gates, done (closure QA passed on #2543) · docs, brand and demo bar, not filed · the launch cut, not filed.

Settled at the hard-gates wrap, binding every later epic (decided once): the packed-install job keeps running the two-users suite against installed tarballs, its workspace-link control must fail, and its queue leg refuses without Redis · BullMQ session concurrency is enforced by a Redis lease (FIX-1634) · FIX-1665 and FIX-1658 are standalone follow-ups, not hard gates.

Need your sign-off

Launch as 1.0, or as 0.x? A 1.0 launch promises installers we won't break them without a major version. It also turns every public API shape into a launch gate. Hard gates wrapped as a defect list, so 1.0 now means a separate API review before the cut. I recommend 0.x, stated plainly in the announcement, with 1.0 as its own milestone after the first cohort. I'd change my mind if a design partner or launch channel needs a stability promise on day one. Being wrong is one-way: 0.x to 1.0 later is cheap, breaking a 1.0 API costs trust. Full ask, with its trade-off figure: DECISIONS.md → Open. It comes down to the hard-gate bar: 1.0 turns a defect list into a full API review.

Reviewers · look here

  • Is the outcome the right finish line, and are the two placeholder epics (docs, brand and demo bar; the launch cut) the right way to hold the launch items that have no epic yet?
  • PD-2, what counts as a hard gate, binds every epic that calls something launch-blocking. The docs, brand and demo bar gates the cut on launch checks 3 and 5 only.
  • The project's earlier Linear description is kept word for word in absorbed/linear-content.md.

Spec · Decisions · Rules · Plan · Linear project

How to review this

This is a project-spec: the standing outcome, the cross-epic decisions, and the live state of
one Linear project, in four documents. It is not an implementation plan, not any one epic's
objective, and not a design.

In scope to challenge:

  • The outcome — is this what the project should be driving at, and would we know if we got there?
  • Whether the project overbuilds. Each epic can earn its place while the whole is too much.
    That question can only be asked here.
  • A decision in DECISIONS.md that binds several epics, or a rule in BUSINESS-RULES.md with no
    owner or two.
  • A missing epic the outcome implies, or one listed that does not serve it.

Out of scope — owned by the epic specs below it:

  • Any single epic's objective, issue division, or internals. Those are its epic PR.
  • The figures at the pixel level, and the status in the epics table, which is refreshed as
    the project moves and is never a review finding.

Feedback in the second list is routed to the epic it concerns, not folded in here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HNTQkGXCUryuVD2TEBLi6G


Generated by Claude Code

Hard gates is done (Linear Done 2026-10-01; closure QA FIX-1636 passed
on #2543). Its row moves to done, its graph node goes heavy, its arc bar
closes Sep 29 to Oct 1, and the now line moves to Oct 1.

Decided once gains three entries that bind sibling epics: the
packed-install job permanently runs the two-users suite on installed
tarballs (workspace-link control must fail, leg c refuses without
Redis); BullMQ session concurrency is enforced by a Redis lease
(FIX-1634); FIX-1665 and FIX-1658 are standalone follow-ups.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HNTQkGXCUryuVD2TEBLi6G
@vercel

vercel Bot commented Oct 1, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
flow-state-dev-docs Ignored Ignored Oct 1, 2026 5:04pm UTC
flow-state-dev-kitchen-sink Ignored Ignored Oct 1, 2026 5:04pm UTC
flow-state-dev-ui Ignored Ignored Oct 1, 2026 5:04pm UTC

Request Review

@jhoffner

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-31T22:58:36.309557Z 960934c Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Chef's kiss.

Reviewed commit: 960934c463

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants