Fundraising: Clarifications FAQ section (VI) - #20
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ytics Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Duplicate questions and prose before the first heading now fail the build loudly instead of producing duplicate React keys or vanishing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Five items now, including the new raise-size question. No em dashes, no repeated raise figure (the ask stays in Section V only), Pew stat now linked to its source. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ading The raise figure may now appear once in the md as a question heading; answer bodies still cannot restate the ask. Spec updated to match. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Rails no longer compete with the SectionHeader dividers (fi-green-500/50). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a Clarifications accordion as Section VI of /fundraising, answering the investor objections from recent feedback (price, subscriptions, narrow use case, industrial design, chip supply, raise size, stack reusability).
How
www/app/fundraising/clarifications.md. Each##heading is a question, the body below is the answer. Extending the FAQ = editing this file only.page.tsxis now a thin server component that reads + parses the md at build time (www/lib/clarifications.ts, marked-based). The previous client page moved wholesale toFundraisingClient.tsx.ClarificationItemrenders native<details name="clarifications">: exclusive-open, keyboard accessible, inert-able by the email gate, zero client JS added.Copy
All seven answers are final copy (Hugh's words, polish pass applied). The raise figure appears in the md only as the "Why $15M?" question heading; answer bodies cannot restate the ask (test-enforced).
Tests
87 passing: parser unit tests, copy-contract extensions (section order, gating, objection coverage), all pre-existing contracts intact. Verified via
npm test,tsc --noEmit, production build (static prerender), and SSR smoke check.Spec and plan docs included under
docs/superpowers/.🤖 Generated with Claude Code