Repository navigation
project(public-launch): Public Launch — the project-spec (never merged) - #2359
Conversation
…fore the first build The project-spec mirror will replace the Linear project's content field. This is the field exactly as read on 2026-09-29, so every fold-or-drop call made in the build is reversible from git. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HNTQkGXCUryuVD2TEBLi6G
The outcome, the territory and the epics table (FIX-1161 in flight, FIX-1635 filed, two placeholders), three cross-epic decisions and one open ask (1.0 or 0.x), one rule with an owner, and the arc. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HNTQkGXCUryuVD2TEBLi6G
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Second look: PR #2359 (project-spec, docs only)Scope of the review. Seven files under Findings, ranked
What I checked and would leave alone
No changes are needed to merge-readiness, since this PR is never merged. Items 1 to 3 are the ones I'd fold before the FIX-1635 objective gate. Generated by Claude Code |
|
Coherence check (FSD Architect) — not owner approval / not the gate. Shared Verdict: No two-direction fork. This is the sole open
Absorbed Linear content → fence + PD-2 is intentional narrowing, not a silent second launch definition. Closed FIX-1161 epic #1301 correctly noted as surface-only (epic still in flight). Placeholder epics (docs/brand/demo bar; launch cut) are holds, not competing streams. No open competing Open ask already on the PR (1.0 vs 0.x): product call; when Jake settles it, record via Decision Manager (D-n), then fold the answer back here before FIX-1635’s objective gate. Architect does not own that issue. |
There was a problem hiding this comment.
Simplify / architecture read
This PR is not an over-built code change — it is the first spec/_projects/* stand-up, and the shape matches project-spec-template.md, project-agent.md, and spec-figures.md (four docs, territory + arc SVGs, mermaid epic graph, absorbed/linear-content.md). Compared to the absorbed Linear checklist (six launch bullets including kitchen-sink polish and tier 2/3 harness), splitting FIX-1161 vs FIX-1635 (PD-1) and narrowing “launch-blocking” to harm/defect (PD-2) is the simpler product story, not extra complexity. I would not recommend collapsing back into one epic or one mega-checklist.
Where complexity still shows up (doc hygiene, not wrong approach)
- The read vs PD-2 — Check (5) (“demo works on the public deploy”) still sounds like the old Linear “kitchen-sink demo-quality” bar, while PD-2 explicitly excludes polish (FIX-1631–1633, etc.) from gates. Worth one crisp sentence on whether (5) means functional showcase paths (docs/demo epic) vs visual polish (not a veto). That removes ambiguity without reopening scope.
- Dropped checks — Tier 2/3 testing (old #6) and hybrid search (FIX-107) disappear from the five-check read; only traces in
PLAN.md/ absorbed. A single decided once line (“FIX-488/489/107 are not one of the five checks unless Jake adds them”) would be cheaper than re-deriving from absorbed content. - Duplication — Status counts (
0 done · 1 in flight…) appear in the outcome table and again under the epics table; the fence question appears inSPEC.md, territory SVG, PD-2, andPLAN.md. Template wants the epics table to own status once; PD-2 can own the gate definition with(PD-2)links elsewhere. - Figures — Hand-authored arc/territory SVGs with duplicated
:rootblocks are template-intended (spec-figures.md: position is the content). Maintenance cost is real (dates,FIX-XXX, six surfaces) but the alternative (mermaid for the arc) would violate the doc. Optional nit: drop unused--prosetokens in both SVGs when you next touch them. - Open 0.x vs 1.0 — Full six-part ask in
DECISIONS.md → Openmatchesproject-agent(“record it there”).project-spec-template.mdalso wants live asks visible in the PR body under Reviewers · look here; if the body does not mirror this fork yet, add a short pointer there so epic-lifecycle callers do not have to scrapeDECISIONS.md. PLAN.mdissue laundry — The long unassigned-issue paragraph will stale quickly; linking the Linear project filter + naming only launch-cut placeholders might be enough.
Approaches I considered and would not take
- Single epic for launch — Rejected by PD-1; would mix stranger path and defect closure and make “done” untestable.
- Keep all six Linear bullets as launch gates — Re-expands scope; PD-2 is the simplification.
- Shared external CSS for SVGs — Breaks self-contained figure rule in
spec-figures.md; duplicate inline CSS is the repo norm (see epic figures like FIX-1553). - Skip arc until hard-gates objective approval — Valid bootstrap shortcut; keeping an mostly-empty arc is still template-correct.
Third-party / reuse
No custom tooling needed; the “package” here is the documented project-spec stack. absorbed/ is the prescribed verbatim capture, not extra ceremony.
Verdict: Direction and structure look right for a never-merged project-spec. Approving; inline comments are the highest-leverage simplifications if you want a follow-up edit on this branch.
Sent by Cursor Automation: Review For Best Approach
There was a problem hiding this comment.
Code Snob — too small / already tight. No POC.
I read spec/_projects/public-launch/SPEC.md, DECISIONS.md, BUSINESS-RULES.md, PLAN.md, absorbed/linear-content.md, figures/territory.svg, and figures/arc.svg, against the project-spec template.
A rewrite would not shrink the contract. The template already requires the four documents, the territory figure, the arc figure, and the mermaid graph. Those are containment, time, and handoff, not five copies of one status board. Prose is on the budgets (SPEC 760 vs ~700, decisions 767 vs ~900, plan 480 vs ~700, rules 172 vs ~600). The opening paragraph of SPEC.md repeats the Winning when row; deleting it leaves the required table saying the same thing. The theme blocks repeated in the two SVGs cannot be shared, because each figure has to stay self-contained. absorbed/linear-content.md is the verbatim Linear snapshot, so folding it would drop the reversible read.
Sent by Cursor Automation: Code Snob
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f36fe82911
ℹ️ 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".
… bot review Status: hard gates' objective is in review (PR #2360, closure FIX-1636 filed); the epics table carries epic state only, counts live once in Now. Folded from #2359 review: check 5 means the showcase paths run, not polish; the docs, brand and demo bar gates the cut on checks 3 and 5 only; framework simplification is the one exception to whatever-landed; a decided-once line for tier 2/3 testing and FIX-107; PR-1's checked where points at FIX-1636's closure run; the territory figure holds no live status; the open 1.0-vs-0.x fork gets its trade-off figure. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HNTQkGXCUryuVD2TEBLi6G
Process guards fails on main since #2359 put spec/_projects on it; #2392 removes it. Same deletion here, a no-op once #2392 merges. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014LohgYyHsXCYQd6kABH11N
|
This PR was merged by mistake on 2026-09-29, and Generated by Claude Code |


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. As of 2026-09-29 · head
bd55748a.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 first hour is the only bar so far. Hard gates' objective is in review, and its bar starts when that objective is approved.
The epics (live table): FIX-1161 first hour, in flight · FIX-1635 hard gates, not started, objective in review on #2360 · docs, brand and demo bar, not filed · the launch cut, not filed.
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, which widens hard gates from a defect list into an API review. 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. Worth answering before FIX-1635's objective gate, which is now open on #2360. Full ask, with its trade-off figure: DECISIONS.md → Open. It comes down to FIX-1635's scope: 1.0 turns a defect list into a full API review.
Reviewers · look here
absorbed/linear-content.md. Its definition of launched, its scope, what it excluded, and its dependencies were folded in. Two open questions were left for the epics that own them: the scaffold's package name (FIX-1162) and the number of starters (FIX-548).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:
That question can only be asked here.
DECISIONS.mdthat binds several epics, or a rule inBUSINESS-RULES.mdwith noowner or two.
Out of scope — owned by the epic specs below it:
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