moose-lab · moose-lab · Jun 2, 2026 · Jun 2, 2026
diff --git a/.agents/product-marketing.md b/.agents/product-marketing.md
@@ -1,12 +1,12 @@
 # Product Marketing Context
 
-*Last updated: 2026-05-15*
+*Last updated: 2026-06-03*
 
 ## Product Overview
 
 **One-liner:** QuickFork turns a GitHub repository into a launch-ready story and shareable marketing asset package.
 
-**What it does:** QuickFork accepts a GitHub repository URL, extracts repository and README evidence, builds a curated project brief, generates aligned launch copy, and produces prompt/image/quality artifacts for README pages, slide decks, and social distribution. The product emphasizes traceability: generated claims, metrics, identity assets, and visual prompts should come from repository evidence or explicit user input.
+**What it does:** QuickFork accepts a GitHub repository URL, extracts repository and README evidence, builds a curated project brief, maps launch materials across README/social/deck/visual/outreach channels, generates aligned launch copy, and produces prompt/image/quality artifacts for README pages, slide decks, and social distribution. The product emphasizes traceability: generated claims, metrics, identity assets, channel mappings, and visual prompts should come from repository evidence or explicit user input.
 
 **Product category:** GitHub-to-launch asset generator; developer marketing automation; open-source launch storytelling tool.
 
@@ -25,12 +25,14 @@
 **Jobs to be done:**
 - Turn a repository into a clear public-facing project story.
 - Produce launch visuals and copy for README, PPT, X/LinkedIn, and social posts.
+- Map each launch material to the target user, source evidence, review question, and success signal before publishing.
 - Preserve evidence, identity assets, metrics, and locale alignment so generated marketing can be reviewed before publishing.
 
 **Use cases:**
 - Launch a GitHub project with README cover imagery and concise positioning.
 - Prepare multilingual launch copy in English, Chinese, and Japanese.
 - Generate a marketing-card prompt and visual output with source-backed identity rules.
+- Create a launch materials map for README, social, deck, visual, and outreach channels from one repository brief.
 - Create project showcase pages from successful generations.
 - Build reusable proof and case-study content from generated launch packages.
 
@@ -117,7 +119,7 @@
 - "Repo URL in, shareable project assets out."
 - "A traceable marketing-card workflow for open-source projects."
 
-**Words to use:** GitHub repository, launch-ready story, source-backed, traceable, curated brief, README cover, launch package, marketing card, localized copy, artifact manifest, quality report, official logo, GitHub avatar.
+**Words to use:** GitHub repository, launch-ready story, source-backed, traceable, curated brief, launch materials map, README cover, launch package, marketing card, localized copy, artifact manifest, quality report, official logo, GitHub avatar.
 
 **Words to avoid:** Magic, fake proof, random logo, one-click publish, guaranteed rankings, autonomous launch, invented metrics.
 
@@ -126,6 +128,7 @@
 | Term | Meaning |
 | --- | --- |
 | Launch package | The combined brief, copy, prompt, image, QA, and manifest artifacts created from a repo |
+| Launch materials map | A channel plan that assigns README, social, deck, visual, and outreach materials to target users, source evidence, review questions, and success signals |
 | Curated brief | A compact source-backed summary used as the factual base for generated assets |
 | Marketing card | A visual project explainer suitable for README, PPT, and social distribution |
 | Identity asset | Official project logo, README asset, homepage asset, or GitHub avatar used to represent the project |
@@ -155,6 +158,7 @@
 | Theme | Proof |
 | --- | --- |
 | Repo-to-story speed | Current app accepts GitHub URL and runs `/api/generations` to produce launch artifacts |
+| Channel planning | The generated launch brief includes a source-backed launch materials map for README, social, deck, visual, and outreach outputs |
 | Traceability | Workflow stores brief, prompt, image, quality report, and manifest paths |
 | Brand safety | Identity rules prefer official assets or GitHub avatar and forbid random generated logos |
 | Multilingual readiness | Current workflow supports English, Chinese, and Japanese output slots |

diff --git a/docs/marketing/data/semantic-link-inventory.csv b/docs/marketing/data/semantic-link-inventory.csv
@@ -2,6 +2,7 @@ status,funnel_stage,buyer_stage,persona,intent_cluster,page_type,slug,canonical_
 published,top,consideration,open_source_maintainer,github_repo_to_launch_package,product,github-repo-to-launch-package,https://seekersai.com/product/github-repo-to-launch-package,github repo to launch package,generate_launch_card,google,organic,seo_foundation,product_category,2026_q2_seo_foundation,https://seekersai.com/product/github-repo-to-launch-package?utm_source=google&utm_medium=organic&utm_campaign=seo_foundation&utm_content=product_category
 published,top,consideration,product_marketer,source_backed_launch_assets,product,source-backed-launch-assets,https://seekersai.com/product/source-backed-launch-assets,source backed launch assets,generate_launch_card,perplexity,ai_search,ai_visibility,source_backed_assets,2026_q2_ai_visibility,https://seekersai.com/product/source-backed-launch-assets?utm_source=perplexity&utm_medium=ai_search&utm_campaign=ai_visibility&utm_content=source_backed_assets
 published,top,consideration,ai_project_builder,cold_start_launch_materials,product,cold-start-launch-materials,https://seekersai.com/product/cold-start-launch-materials,cold start launch materials,generate_launch_card,google,organic,cold_start_materials,product_page,2026_q2_cold_start_materials,https://seekersai.com/product/cold-start-launch-materials?utm_source=google&utm_medium=organic&utm_campaign=cold_start_materials&utm_content=product_page
+published,top,consideration,ai_project_builder,github_repo_launch_materials_map,product,github-repo-launch-materials-map,https://seekersai.com/product/github-repo-launch-materials-map,github repo launch materials map,generate_launch_card,google,organic,launch_materials_map,product_page,2026_q2_launch_materials_map,https://seekersai.com/product/github-repo-launch-materials-map?utm_source=google&utm_medium=organic&utm_campaign=launch_materials_map&utm_content=product_page
 published,top,consideration,design_lead,readme_marketing_cards,product,readme-marketing-cards,https://seekersai.com/product/readme-marketing-cards,readme marketing cards,generate_launch_card,google,organic,readme_assets,product_page,2026_q2_readme_assets,https://seekersai.com/product/readme-marketing-cards?utm_source=google&utm_medium=organic&utm_campaign=readme_assets&utm_content=product_page
 published,top,consideration,ai_project_builder,github_repo_visual_explainer,product,github-repo-visual-explainer,https://seekersai.com/product/github-repo-visual-explainer,github repo visual explainer,generate_launch_card,google,organic,visual_explainer,product_page,2026_q2_visual_explainer,https://seekersai.com/product/github-repo-visual-explainer?utm_source=google&utm_medium=organic&utm_campaign=visual_explainer&utm_content=product_page
 published,top,consideration,founder,github_repo_to_launch_deck,product,github-repo-to-launch-deck,https://seekersai.com/product/github-repo-to-launch-deck,github repository pitch deck generator,generate_launch_card,google,organic,launch_deck,product_page,2026_q2_launch_deck,https://seekersai.com/product/github-repo-to-launch-deck?utm_source=google&utm_medium=organic&utm_campaign=launch_deck&utm_content=product_page

diff --git a/docs/marketing/research/2026-06-03-launch-materials-map.md b/docs/marketing/research/2026-06-03-launch-materials-map.md
@@ -0,0 +1,80 @@
+# 2026-06-03 Launch Materials Map Research Note
+
+## Summary
+
+The launch materials map packages QuickFork's repo-to-launch output into a channel plan: README, social, deck, visual, and outreach. It turns the free launch brief from "generated assets" into a reviewable product workflow with target user, job, artifact, source evidence, review question, and success signal per channel.
+
+This is a product activation hypothesis, not validated market demand.
+
+## Why This Slice Matters
+
+- QuickFork already generates multiple launch artifacts from one repository URL.
+- Builders need help deciding which artifact belongs on which channel before public publishing.
+- A map makes the product easier to explain in landing pages, AI-search answers, and sales conversations.
+- A map creates a paid-packaging wedge: the free product can show the plan, while a paid package can offer reviewed execution across the same channels.
+
+## Target User Hypotheses
+
+- AI project builder: needs a launch story without writing a blank marketing prompt.
+- Open-source maintainer: needs README and social assets that remain tied to repository evidence.
+- DevRel operator: needs channel-specific launch material for docs, social, and community posts.
+- Technical founder: needs a deck and outreach narrative before requesting a fuller launch package.
+- Product marketer: needs traceable claims and a reusable artifact map for cross-channel review.
+
+## Product Lifecycle Position
+
+- Discovery: public landing route explains the problem and source-backed workflow.
+- Activation: generated brief now includes a launch materials map and copy event.
+- Validation: compare page and artifact behavior against existing repo-to-launch routes.
+- Monetization: only after evidence shows repeated full-package interest should QuickFork package reviewed channel execution as a paid product.
+
+## Growth Contract
+
+Primary activation metric:
+
+- `launch_materials_map_copied` after a successful free repo launch brief.
+
+Supporting metrics:
+
+- `page_view` for `/product/github-repo-launch-materials-map`.
+- CTA clicks with `intent_cluster=github_repo_launch_materials_map`.
+- Repo URL submissions from the route.
+- Generation completions and failures.
+- Artifact copy/download events by type.
+- Full launch package requests after materials-map exposure.
+
+Guardrails:
+
+- Do not claim search placement, financial outcomes, adoption, Product Hunt outcomes, exact pricing, or automatic publishing.
+- Do not send raw README text, artifact bodies, source notes, secrets, tokens, or email to browser analytics.
+- Keep every launch material tied to repository evidence, official assets, generated reports, or explicit user input.
+
+## Source-Backed Inputs
+
+- GitHub README docs define README as the repository explanation surface: https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes
+- GitHub social preview docs make repository preview visuals part of launch packaging: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview?apiVersion=2022-11-28
+- Open Source Guides finding users connects audience discovery and feedback loops to open-source launches: https://opensource.guide/finding-users/
+- Product Hunt launch guidance frames story, media, maker context, and launch-day copy as review surfaces: https://www.producthunt.com/launch/preparing-for-launch
+
+## Implemented Surface
+
+- `RepoLaunchBrief.launchMaterialsMap`
+- `RepoLaunchBrief.artifacts[]` item with type `materials_map`
+- Landing result section labeled `Launch materials map`
+- Copy tracking event `launch_materials_map_copied`
+- Product route `/product/github-repo-launch-materials-map`
+- Public discovery assets in `sitemap.xml` and `llms.txt`
+
+## Current Verification
+
+- Baseline `npm test`: 24 files passed, 158 tests passed before implementation.
+- Focused generation verification passed.
+- Focused hero generator verification passed.
+- Focused route, semantic link, and public growth verification passed.
+- Full verification passed: `npm test` returned 24 files passed and 160 tests passed.
+- Build verification passed: `npm run build` completed TypeScript build and Vite production build.
+- Diff hygiene passed: `git diff --check` returned no whitespace errors.
+
+## Next Validation Step
+
+Run a 14-day comparison against `/product/github-repo-to-launch-package` and `/product/cold-start-launch-materials`. Prioritize this slice only if visitors who see or copy the map show stronger generation completion, artifact export, or full-package request behavior.
diff --git a/docs/plans/2026-06-01-quickfork-growth-lifecycle-prioritization.md b/docs/plans/2026-06-01-quickfork-growth-lifecycle-prioritization.md
@@ -1518,3 +1518,67 @@ Decision:
 Next action:
 
 - Run the manual baseline using the four prompt rows, then fill evidence rows only after real Search Console exports and AI-answer observations exist.
+
+## 2026-06-03 Launch Materials Map Product Activation Slice
+
+Hypothesis:
+
+- If QuickFork adds a source-backed launch materials map to the generated brief and gives the same intent a crawlable product route, AI project builders can understand which launch material belongs on README, social, deck, visual, and outreach channels before requesting a full package.
+
+Lifecycle stage:
+
+- Activation and Validation.
+
+Target user:
+
+- AI project builders preparing a cold-start repository launch.
+- Open-source maintainers who need source-backed README, social, and visual materials.
+- DevRel operators and product marketers who need traceable channel assets.
+- Technical founders evaluating whether a reviewed launch package is worth requesting.
+
+Changed surface:
+
+- `src/server/generation/types.ts`
+- `src/server/generation/launch-brief.ts`
+- `src/components/landing/HeroSection.tsx`
+- `src/lib/analytics.ts`
+- `src/styles/app.css`
+- `src/marketing/link-catalog.ts`
+- `src/marketing/page-content.ts`
+- `public/sitemap.xml`
+- `public/llms.txt`
+- `docs/marketing/data/semantic-link-inventory.csv`
+- `docs/superpowers/plans/2026-06-03-launch-materials-map.md`
+- `docs/marketing/research/2026-06-03-launch-materials-map.md`
+
+Metric:
+
+- Primary: `launch_materials_map_copied`.
+- Supporting: page views, CTA clicks, repo submissions, generation completions, artifact copy/download events, and full launch package requests by `intent_cluster=github_repo_launch_materials_map`.
+
+Guardrail:
+
+- Do not claim search placement, financial outcomes, adoption, Product Hunt outcomes, exact pricing, automatic publishing, or willingness to pay.
+- Do not send raw README text, artifact bodies, source notes, secrets, tokens, email, or private launch notes to browser analytics.
+
+Evidence observed:
+
+- Baseline `npm test` passed before changes: 24 test files, 158 tests passed.
+- RED generation test failed first because the launch brief did not include `launchMaterialsMap` or a `materials_map` artifact.
+- GREEN focused generation verification passed: `npm test -- src/server/generation/generation.test.ts -t "source-backed free repo launch brief"`.
+- GREEN focused UI verification passed: `npm test -- src/App.test.tsx -t "Hero generator"`.
+- RED route tests failed first because `/product/github-repo-launch-materials-map` was not in the marketing catalog, sitemap, or `llms.txt`.
+- GREEN route verification passed: `npm test -- src/App.test.tsx -t "launch materials map"`.
+- GREEN semantic-link verification passed: `npm test -- src/seo/semantic-links.test.ts -t "launch materials map|canonical page paths"`.
+- GREEN public-growth verification passed: `npm test -- src/seo/public-growth.test.ts -t "sitemap|machine-readable AI context"`.
+- Full verification passed: `npm test` returned 24 files passed and 160 tests passed.
+- Build verification passed: `npm run build` completed TypeScript build and Vite production build.
+- Diff hygiene passed: `git diff --check` returned no whitespace errors.
+
+Decision:
+
+- Treat this as a product activation and validation slice, not validated demand. The materials map is ready for production smoke, Search Console review, AI-answer checks, and artifact-behavior comparison.
+
+Next action:
+
+- Run full verification, merge, production smoke, then compare `/product/github-repo-launch-materials-map` behavior against `/product/github-repo-to-launch-package` and `/product/cold-start-launch-materials` over a 14-day window.
diff --git a/docs/superpowers/plans/2026-06-03-launch-materials-map.md b/docs/superpowers/plans/2026-06-03-launch-materials-map.md
@@ -0,0 +1,57 @@
+# 2026-06-03 Launch Materials Map
+
+## Objective
+
+Turn QuickFork's free repo launch brief into a clearer product activation surface by adding a source-backed launch materials map. The map explains which generated material belongs on README, social, deck, visual, and outreach channels, who it is for, what source evidence supports it, what a human should review, and what activation signal QuickFork should measure next.
+
+## Skills And Rules
+
+- Use `superpowers:*` skills when the task matches their trigger rules.
+- Keep the growth loop source-backed: repository evidence, official project assets, README content, public metadata, generated reports, and explicit user input.
+- Keep analytics payloads behavioral and aggregate. Do not send raw README text, artifact bodies, secrets, tokens, email, or private launch notes.
+- Use the Obsidian growth note to record the hypothesis, validation evidence, and next lifecycle decision after implementation.
+
+## Product Hypothesis
+
+If QuickFork makes the launch materials map first-class inside the generated brief and gives the same intent a crawlable product page, AI project builders can understand the value faster and QuickFork can measure whether artifact planning creates stronger activation than isolated copy/download events.
+
+## Target Users
+
+- AI project builders preparing a cold-start GitHub launch.
+- Open-source maintainers who need a reviewable README, social, and visual package.
+- DevRel operators and product marketers who need traceable channel assets.
+- Technical founders evaluating whether a paid launch package is worth requesting.
+
+## Implementation Plan
+
+1. Add a typed `launchMaterialsMap` to `RepoLaunchBrief`.
+2. Generate five channel mappings: README, social, deck, visual, and outreach.
+3. Add a `materials_map` artifact to the export manifest.
+4. Render the map in the landing generator result and support copy tracking with `launch_materials_map_copied`.
+5. Add `/product/github-repo-launch-materials-map` to the semantic link catalog, page narrative, sitemap, `llms.txt`, and CSV inventory.
+6. Record the growth hypothesis and lifecycle plan in repo docs and Obsidian.
+
+## Source Notes
+
+- GitHub README docs: https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes
+- GitHub social preview docs: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview?apiVersion=2022-11-28
+- Open Source Guides finding users: https://opensource.guide/finding-users/
+- Product Hunt launch guide: https://www.producthunt.com/launch/preparing-for-launch
+
+## Verification Notes
+
+- Baseline `npm test` passed before implementation: 24 test files, 158 tests.
+- RED generation test failed before `launchMaterialsMap` existed.
+- GREEN generation focused test passed: `npm test -- src/server/generation/generation.test.ts -t "source-backed free repo launch brief"`.
+- GREEN UI focused test passed: `npm test -- src/App.test.tsx -t "Hero generator"`.
+- RED route tests failed before `/product/github-repo-launch-materials-map` was added to the catalog and public assets.
+- GREEN route focused test passed: `npm test -- src/App.test.tsx -t "launch materials map"`.
+- GREEN semantic-link focused test passed: `npm test -- src/seo/semantic-links.test.ts -t "launch materials map|canonical page paths"`.
+- GREEN public-growth focused test passed: `npm test -- src/seo/public-growth.test.ts -t "sitemap|machine-readable AI context"`.
+- Full verification passed: `npm test` returned 24 files passed and 160 tests passed.
+- Build verification passed: `npm run build` completed TypeScript build and Vite production build.
+- Diff hygiene passed: `git diff --check` returned no whitespace errors.
+
+## Lifecycle Decision
+
+Treat this as an Activation plus Validation slice, not proof of demand. The next decision should use page views, CTA clicks, repo submissions, generation completions, materials-map copy events, artifact exports, and full-package requests before expanding or pricing the capability.