@tomako/tools-runtime 0.1.0

package/src/i18n/messages/en/tools/koko-codex-assistant.ts

@@ -0,0 +1,171 @@
+const kokoCodexAssistant = {
+  meta: {
+    title: "KoKo Codex Desktop Assistant Beta",
+    displayTitle: "KoKo Assistant",
+    description: "Download the KoKo Codex Desktop Assistant Mac Beta and turn brand start, code sync, Skill prompts, and completion reminders into quick floating-window actions. Invite code required.",
+    intro: "KoKo gives your recurring Codex prompts and Skills a floating desktop entry point. Enter the internal invite code to download the Mac Beta, then turn brand start, code sync, repeat workflows, and completion reminders into quick KoKo actions.",
+    category: "Codex Tools",
+    keywords: [
+      "Codex desktop assistant",
+      "KoKo Codex Assistant",
+      "Mac floating launcher",
+      "Skill shortcut launcher",
+      "Codex git pull push assistant",
+    ],
+    inputSignal: "Internal invite code",
+    outputSignal: "Mac Beta installer download",
+    boundarySignal: "Windows version coming soon; internal beta only",
+  },
+  widget: {
+    betaBadge: "Beta",
+    macTitle: "Mac Beta download",
+    macBody:
+      "This is the KoKo Codex Desktop Assistant Mac Beta. It adds a floating desktop entry point for the Codex prompts, Skills, and brand parameters you reuse every day.",
+    macPoints: [
+      "Hover the floating window to reveal shortcut buttons",
+      "Bind each button to a prompt, Skill, or preset parameter set",
+      "Open Codex and send the action to the right brand automatically",
+      "Get a helper reminder when Codex finishes the task",
+    ],
+    downloadMac: "Download Mac Beta",
+    downloadAgain: "Download Mac Beta again",
+    verifiedHint: "Invite code verified. The next click downloads directly.",
+    comingSoon: "Coming soon",
+    windowsTitle: "Windows version",
+    windowsBody:
+      "The Windows entry is reserved on the right, but it is not available yet. We will open it after the installer and launch flow are stable.",
+    windowsStatus: "Windows version coming soon",
+    workspaceAlt: "Pixel preview of KoKo opening floating shortcut buttons",
+    dialogTitle: "Enter internal invite code",
+    dialogDescription:
+      "KoKo is currently available as an internal Beta. Enter the invite code to download the Mac installer.",
+    inviteLabel: "Invite code",
+    invitePlaceholder: "Enter invite code",
+    wrongCode: "That invite code is not correct. Please check and try again.",
+    cancel: "Cancel",
+    confirmDownload: "Verify and download",
+  },
+  guide: {
+    betaBadge: "Beta",
+    heroVisualAlt: "KoKo pixel tomato assistant with floating shortcut buttons and a Mac Beta installer",
+    workspaceHeading: "Download KoKo Mac Beta",
+    workspaceHint:
+      "This build is for internal testing. Click the Mac download button and enter the invite code. The Windows entry is reserved but not open yet.",
+    resultHeading: "What you get",
+    resultBody: [
+      "After installation, KoKo gives you a lightweight floating desktop window. You can turn recurring actions such as starting a brand, pulling code, pushing code, or launching a Skill into buttons that are available from any screen.",
+      "When Codex finishes a task, KoKo can also send a helper reminder so you know it is time to review the result. You do not have to keep watching the terminal or repeatedly switch back to Codex while the work is running.",
+      "KoKo is not another web generator and it does not ask you to fill out a long form. Its value is saving the Codex chats, brand paths, prompts, Skills, and completion reminders you already trust, then making them reachable with one hover and one click.",
+    ],
+    workspaceVisualAlt: "Product preview of KoKo opening multiple floating shortcut buttons",
+    scenarioHeading: "Workflows worth turning into buttons",
+    scenarioIntro:
+      "The first Beta focuses on high-frequency Codex workflows that can be preset and then left to run. The first two scenarios are developer essentials; the other two help teams package repeatable Skill flows.",
+    scenarioItems: [
+      {
+        title: "Start a code brand",
+        body: "Store the brand path, start command, and checks in one button. Hover KoKo, click Start, and let Codex enter the right brand while you wait for the service to be ready.",
+      },
+      {
+        title: "Pull and push code",
+        body: "Split pull, branch checks, commit summaries, push, or draft PR prompts into shortcut buttons. It helps developers who sync code many times a day without wanting to retype the same instructions.",
+      },
+      {
+        title: "Launch a fixed Skill",
+        body: "Turn SEO, brand materials, document cleanup, email drafts, or other Skill calls into buttons. KoKo sends the preset prompt to the right Codex chat or brand.",
+      },
+      {
+        title: "Hand off routine tasks",
+        body: "Teams can package review checklists, launch checks, retrospectives, or asset generation into shared configurations so teammates can trigger the same Codex flow without memorizing the prompt.",
+      },
+    ],
+    configHeading: "Customize the left-side hover buttons",
+    configBody: [
+      "KoKo is not a fixed feature list. Each shortcut can point to a prompt, a Skill, a brand path, a target chat, or a preset parameter set, so the buttons that appear on hover match your actual workflow.",
+      "One button might start local services, another might pull the latest branch, and another might call `$programmatic-seo` for a page brief. The closer the buttons are to your daily actions, the more KoKo feels like a desktop Codex dispatcher.",
+    ],
+    configVisualAlt: "KoKo arranging prompts, Skills, and checklist modules into floating buttons",
+    flowHeading: "Click once, send to Codex",
+    flowBody: [
+      "When you click a button, KoKo opens Codex based on your configuration and sends the right content to the target chat or brand. The workflow becomes hover, click, and wait instead of switching windows, finding the brand, copying a prompt, and rebuilding context.",
+      "That makes KoKo a good fit for tasks that do not need improvisation but do need Codex to act in the right brand: start, sync, check, generate, organize, review, and prepare for release.",
+    ],
+    valueVisualAlt: "Scattered developer chores becoming start, pull, and push actions through KoKo",
+    notificationHeading: "Get reminded when the task is done",
+    notificationBody: [
+      "Many Codex tasks do not finish the moment you click: starting services, cleaning documents, generating assets, and running checks can all take a while. KoKo can notify you through a small helper when the task is complete, so you know the result is ready to review.",
+      "The reminder brings your attention back to the result, but it does not decide whether code is safe, a document is ready to publish, or generated output should ship. You still review the Codex result, ask follow-up questions, and choose the next step.",
+    ],
+    notificationVisualAlt: "Pixel illustration of the KoKo helper reminding a user to review a completed Codex task",
+    standardsHeading: "What a good Codex desktop assistant should do",
+    standardsItems: [
+      {
+        title: "Be fast",
+        body: "The entry point should be available from anywhere and jump straight into the configured Codex context without making you find the brand, Skill, or prompt again.",
+      },
+      {
+        title: "Stay controllable",
+        body: "Every prompt, Skill, and parameter behind a button should be visible, editable, and reusable. KoKo is designed to deliver the actions you already approved.",
+      },
+      {
+        title: "Keep results visible",
+        body: "For waitable tasks, the helper reminder brings you back to Codex when the result is ready, reducing window switching and missed reviews.",
+      },
+      {
+        title: "Keep boundaries clear",
+        body: "The Beta focuses on Mac desktop, internal invite access, and fixed workflows. Code, commits, and release actions that need judgment should still keep human confirmation.",
+      },
+    ],
+    boundaryHeading: "Beta download and platform boundaries",
+    boundaryBody: [
+      "The current Mac installer is a Beta build for internal use. Download requires an internal invite code, which is entered in the download dialog and not exposed in page copy.",
+      "The Windows entry is visible on the right but marked coming soon. That sets platform expectations without implying that a Windows installer is already available.",
+      "KoKo helps send configured content to Codex and can remind you when the task is done, but it does not decide whether code is safe, commits should ship, or generated output is production-ready. Developer buttons should keep necessary checks and human confirmation.",
+    ],
+    betaVisualAlt: "KoKo Mac Beta installer, invite-code lock, and coming-soon Windows entry",
+    faq: "FAQ",
+    faqItems: [
+      {
+        question: "How is KoKo different from a normal launcher?",
+        answer:
+          "A normal launcher usually opens apps or runs commands. KoKo is built around Codex workflows: it can combine prompts, Skills, brand paths, and preset parameters into buttons that send work to a target Codex chat or brand.",
+      },
+      {
+        question: "Why does the KoKo Mac Beta require an invite code?",
+        answer:
+          "This build is still in internal Beta, so download access is limited while we collect feedback on installation, floating-window behavior, Codex launch, and button configuration. If you have an invite code, enter it in the download dialog.",
+      },
+      {
+        question: "Can KoKo start my code brand?",
+        answer:
+          "Yes. You can configure a button with the brand path, start command, and checks. KoKo sends that action to Codex, while the final result still depends on your local environment, dependencies, and brand scripts.",
+      },
+      {
+        question: "Can I use KoKo for git pull and push workflows?",
+        answer:
+          "Yes. You can split pull, checks, commit summaries, push, or PR draft prompts into buttons. Keep branch checks, change summaries, and confirmation steps in the prompt for actions that affect shared code.",
+      },
+      {
+        question: "When will the Windows version be available?",
+        answer:
+          "The Windows version is not open for download yet. The page keeps the entry visible and marked coming soon until installer behavior, floating-window permissions, and Codex launch flow are stable.",
+      },
+      {
+        question: "Can I configure other Skills as KoKo buttons?",
+        answer:
+          "Yes. KoKo is best for frequent, fixed, waitable Skill flows such as SEO briefs, brand assets, document cleanup, launch checks, email drafts, and brand retrospectives.",
+      },
+      {
+        question: "When does the helper reminder appear?",
+        answer:
+          "When a Codex task triggered through KoKo finishes, the helper reminder brings you back to the matching result. It is designed for waitable tasks such as starts, checks, generation, and cleanup; you still review the result before committing, publishing, or using it.",
+      },
+    ],
+    ctaHint:
+      "KoKo is still an internal Beta. You can return to the tool list to explore current Tomako tools, or continue with product naming if you are preparing launch content.",
+    ctaPrimary: "Back to all tools",
+    ctaSecondary: "Try product naming",
+  },
+} as const;
+
+export default kokoCodexAssistant;

package/src/i18n/messages/en/tools/logo-generator.ts

@@ -0,0 +1,173 @@
+const logoGenerator = {
+  meta: {
+    title: "Logo Generator",
+    description: "Turn a product URL, name, context, reference image, and palette into downloadable PNG logo schemes.",
+    intro: "Generate downloadable PNG logo schemes from product context.",
+    category: "Brand tools",
+    keywords: [
+      "logo generator",
+      "AI logo generator",
+      "free logo generator",
+      "startup logo generator",
+      "PNG logo",
+    ],
+  },
+  guide: {
+    heroImageAlt:
+      "Logo generator transparent hero visual showing a product URL, product brief, online logo image, and review checklist.",
+    workspaceHeading: "Generate a logo from product context",
+    workspaceHint:
+      "Product name is the only required field. Add a product URL, description, keywords, reference image, or custom palette if useful; logo format lives under brand constraints.",
+    workspaceVisualAlt:
+      "Logo generator workspace visual showing a product URL and brief becoming online logo image candidates.",
+    valueHeading: "What you get",
+    valueIntro:
+      "This logo generator does not use front-end fake images or templates. It returns downloadable, reviewable brand directions through the online image workflow.",
+    valueVisualAlt:
+      "Logo generator output visual showing a PNG source image, product context, and review checklist.",
+    valueCards: [
+      {
+        title: "PNG source image",
+        body: "The result comes from the image service imageUrl and can be downloaded as the generated logo image.",
+      },
+      {
+        title: "Product context",
+        body: "Product URL, description, and keywords enter the brief; the URL may be used to read public title and description metadata.",
+      },
+      {
+        title: "Brand constraints",
+        body: "Industry, audience, and logo format can be added in the collapsed area. Custom palette is separate; if left empty, the Agent infers color direction.",
+      },
+      {
+        title: "Review checklist",
+        body: "Check small-size recognition, color usability, trademark risk, and rights review before treating a logo as final.",
+      },
+    ],
+    howToUse: "How to use",
+    howToUseIntro:
+      "Start with the smallest useful brief, compare directions, then use a reference image, custom palette, or brand constraints when you need a tighter result.",
+    howToUseSteps: [
+      "Enter the product name; optionally add a product URL plus product description and keywords.",
+      "Optionally upload a reference image or choose a custom palette; if you do not, the Agent infers direction from URL, context, and product name.",
+      "Open brand constraints only when you need industry, audience, or logo format.",
+      "Submit and wait for the online Agent to call image generation and write back a real imageTaskId and imageUrl.",
+      "Pick a direction, download the PNG source image, then refine it in a design tool.",
+    ],
+    resultGuidance: "How to judge the result",
+    resultGuidanceIntro:
+      "Treat each result as a pre-launch design direction. Check clarity, fit, and reviewability before deciding which direction is worth refining.",
+    resultVisualAlt:
+      "Logo generator result guidance visual showing score, context fit, and review checks.",
+    guidanceBullets: [
+      "Check recognition at small sizes: the mark should still work as a favicon, app icon, or avatar.",
+      "Match the context: websites, apps, social profiles, and pitch decks need different spatial balance.",
+      "Keep two or three directions for refinement instead of picking only because of color.",
+      "Use the PNG source image for quick sharing and page previews; vectorization and brand-system cleanup should happen before commercial use.",
+    ],
+    standardsHeading: "Why use Tomako",
+    standardsIntro:
+      "A good AI logo generator should keep inputs light, return results from a real generation workflow, make downloads easy, and state what it cannot verify.",
+    standardCards: [
+      {
+        title: "Low-friction input",
+        body: "Start from a product name. Add URL, product context, industry, and audience only when you need a more precise direction.",
+      },
+      {
+        title: "Traceable result source",
+        body: "The front end only displays imageUrl values written back by Skills-OL, not browser templates or placeholders.",
+      },
+      {
+        title: "Built for indie launches",
+        body: "Results are organized around websites, app icons, social avatars, and pitch decks: the first surfaces most builders need.",
+      },
+      {
+        title: "Clear boundaries",
+        body: "It does not promise trademark clearance, rights review, or a full brand system. Commercial use still needs human review.",
+      },
+    ],
+    useCases: "Use cases",
+    useCasesIntro:
+      "People searching for a logo generator usually want usable visual directions quickly, not a design essay. This page maps common indie-builder jobs to output and download actions.",
+    useCasesVisualAlt:
+      "Logo generator use case visual showing launch assets for a website, app icon, and social avatar.",
+    useCaseCards: [
+      {
+        title: "Shape the first identity after naming",
+        description: "Once the product name is stable, generate symbol, wordmark, and icon directions to test whether the name can carry a brand.",
+        label: "0 to 1",
+      },
+      {
+        title: "Prepare a landing page or waitlist",
+        description: "Create a consistent first mark for website navigation, hero sections, favicons, and social avatars.",
+        label: "Launch",
+      },
+      {
+        title: "Compare brand directions in a proposal",
+        description: "Turn one product brief into multiple comparable directions for internal review or client discussion.",
+        label: "Pitch",
+      },
+      {
+        title: "Hand off for refinement",
+        description: "Download the PNG source image and continue vectorization, spacing, and brand cleanup in Figma, Illustrator, or a design workflow.",
+        label: "Review",
+      },
+    ],
+    boundaryHeading: "Scope and boundaries",
+    boundaryIntro:
+      "This version generates images from the brief you submit. If you provide a product URL, it may read public metadata, but it does not replace rights review.",
+    boundaryVisualAlt:
+      "Logo generator boundary visual showing an online image result, URL metadata, and human review.",
+    boundaryGroups: [
+      {
+        title: "Supported",
+        items: [
+          "Product URL, product name, product description and keywords, reference image, custom palette, industry, audience, and logo format.",
+          "Image-service imageUrl, PNG source download, and review guidance.",
+          "First visual directions for websites, app icons, social avatars, and pitch decks.",
+        ],
+      },
+      {
+        title: "Not supported",
+        items: [
+          "No guarantee that restricted, logged-in, or anti-crawling pages can be read.",
+          "No trademark search, copyright review, similar-brand search, or commercial-use guarantee.",
+          "No complete brand system, brand book, transparent-background pack, or final vector trademark handoff.",
+        ],
+      },
+      {
+        title: "If the result misses",
+        items: [
+          "Add product differentiation, target users, and keywords before trying again.",
+          "If the small-size result is unclear, choose a simpler logo format or wordmark direction.",
+          "Before commercial use, run design review and rights-risk checks.",
+        ],
+      },
+    ],
+    faq: "FAQ",
+    faqIntro:
+      "These questions keep the main trust boundary visible: the tool creates image candidates, but it does not replace trademark search, rights review, or a full brand identity system.",
+    faqItems: [
+      {
+        question: "Does this create a commercial logo?",
+        answer:
+          "The goal is a near-production logo image candidate, but it does not check trademarks, copyright, or similarity to existing brands. Run design review, vectorization, and rights review before commercial use.",
+      },
+      {
+        question: "Why does it output a PNG source image?",
+        answer:
+          "The real image workflow returns a raster PNG from the image service. It is useful for choosing a direction, previewing it in product surfaces, or handing it to a designer for vector refinement.",
+      },
+      {
+        question: "Do I need to provide a product URL?",
+        answer:
+          "No. Product URL is optional. If provided, the script tries to read public page title and description metadata; if that fails, generation still uses your product description and keywords.",
+      },
+    ],
+    ctaPrimary: "Generate product names first",
+    ctaSecondary: "Back to all tools",
+    ctaHint:
+      "If the product name is not stable yet, generate name candidates first, then return to create logo directions.",
+  },
+} as const;
+
+export default logoGenerator;

package/src/i18n/messages/en/tools/market-forecast-report.ts

@@ -0,0 +1,228 @@
+const marketForecastReport = {
+  meta: {
+    title: "TAM, SAM & SOM Forecast Tool",
+    displayTitle: "TAM, SAM & SOM Forecast Tool",
+    description:
+      "Add product, buyer, pricing, and traction to build TAM, SAM, SOM, and three ARR scenarios with source notes, assumptions, and diligence questions for your deck.",
+    intro:
+      "Fundraising market forecasts should not rest on one consulting report. This tool combines public statistics, community activity signals, policy trends, competitor clues, and your real traction into a forecast range that can be checked.",
+    category: "Fundraising and market research tools",
+    keywords: [
+      "market size forecast",
+      "ARR forecast tool",
+      "TAM SAM SOM calculator",
+      "startup market research",
+      "startup user growth forecast",
+    ],
+    inputSignal: "Product context, current users, target users, market, revenue, pricing, conversion",
+    outputSignal: "TAM/SAM/SOM, three forecast scenarios, evidence wall, policy trends, diligence checklist",
+    boundarySignal: "Evidence-backed estimate, not investment advice or a guaranteed financial forecast",
+  },
+  widget: {
+    productLabel: "Product and use case",
+    productPlaceholder:
+      "Example: an AI support-ticket triage tool for North American SMB SaaS teams, integrating with Zendesk and Intercom to prioritize issues and detect repeated problems.",
+    targetUsersLabel: "Target users / buyers",
+    targetUsersPlaceholder: "Example: support leads and CX ops at 50-500 person SaaS companies",
+    marketLabel: "Target market",
+    marketPlaceholder: "Example: US / North America / global B2B SaaS",
+    currentUsersLabel: "Current users",
+    currentUsersPlaceholder: "Example: 2,000 workspaces, 120 daily active teams",
+    horizonLabel: "Forecast horizon",
+    horizon: {
+      oneYear: "1 year",
+      threeYear: "3 years",
+      fiveYear: "5 years",
+    },
+    metricsLabel: "Current business metrics",
+    metricsHint: "Optional",
+    metricsPlaceholder:
+      "Example: $8k MRR; Pro at $49/mo; paid conversion around 6%; user count grew 18% MoM for 3 months; competitors include Gorgias and Intercom Fin.",
+    inputHint:
+      "The tool uses public, attributable evidence and the data you provide. If evidence is thin, the report lowers confidence and lists gaps instead of making the answer sound certain.",
+    submit: "Generate market forecast",
+    submitting: "Submitting...",
+    running: "Researching...",
+    emptyTitle: "Your market forecast report will appear here",
+    emptyHint:
+      "After submission, you will get TAM/SAM/SOM, an evidence wall, community activity signals, policy trends, bear/base/bull user and ARR forecasts, sensitivity analysis, and an investor diligence checklist.",
+    runningTitle: "Collecting public market evidence",
+    runningHint:
+      "The agent prioritizes official statistics, company disclosures, policy text, public community discussion, and checkable web pages. Partial sections may appear before the full report.",
+    progressTitle: "Recent progress",
+    progressSteps: [
+      "Received the product context and started defining market boundaries, user segments, and searchable evidence questions.",
+      "Looking for official statistics, company disclosures, public community discussion, and policy trends.",
+      "Separating real activity signals from member counts, media heat, and secondhand report numbers.",
+      "Building bear/base/bull assumptions for users, paid conversion, ARPU/ACV, and ARR.",
+      "Organizing evidence strength, sensitivity variables, missing evidence, and investor diligence questions.",
+    ],
+    progressResultReady: "A structured report snapshot was written back. Reading and validating it now.",
+    status: {
+      default: "Researching",
+      PENDING: "Queued",
+      STREAMING: "Researching",
+      AWAITING_INPUT: "Analyzing",
+      AWAITING_RESULT: "Reading result",
+      SUCCEEDED: "Finishing",
+    },
+    retry: "Retry",
+    errors: {
+      invalid: "Add clearer product, buyer, and market context. Avoid test/demo/placeholder content.",
+      submit: "Submission failed. Check the connection and try again.",
+      task: "The market forecast task failed. Please try again later.",
+      timeout: "Research timed out. Current partial results were kept; retry for a full report.",
+      schema: "The returned report format was invalid. Please retry.",
+    },
+    analyzeAnother: "Analyze another market",
+    copy: "Copy report",
+    copied: "Copied",
+    boundaryFallback:
+      "This is estimate-grade research based on public information and user input. It is not investment advice, a fundraising promise, a guaranteed financial forecast, or a substitute for professional market research.",
+    confidence: { low: "Low", medium: "Medium", high: "High" },
+    strength: { weak: "Weak", mixed: "Mixed", strong: "Strong" },
+    scenario: { bear: "Bear", base: "Base", bull: "Bull" },
+    policy: { tailwind: "Tailwind", headwind: "Headwind", mixed: "Mixed" },
+    intent: {
+      clear: "Buying intent: clear",
+      weak: "Buying intent: weak",
+      not_observed: "Buying intent: not observed",
+      unknown: "Buying intent: unknown",
+    },
+    sourceStatus: {
+      source_linked: "Source linked",
+      source_named: "Source named",
+      needs_source: "Needs source",
+      user_provided: "User provided",
+    },
+    volatility: { low: "Low volatility", medium: "Medium volatility", high: "High volatility" },
+    checkStatus: { pass: "Pass", warning: "Warning", fail: "Fail" },
+    protocol: {
+      market: "Market definition",
+      boundary: "Market boundary",
+      recency: "Recency rule",
+      formula: "Forecast formula",
+      channelPlan: "Evidence channel plan",
+      archetype: "Market archetype",
+      geo: "Geo",
+      language: "Language",
+    },
+    channelRole: {
+      core: "Core",
+      supporting: "Supporting",
+      comparable_only: "Comparable only",
+      excluded: "Excluded",
+    },
+    forecast: {
+      users: "Users",
+      paidUsers: "Paid users",
+      conversion: "Paid rate",
+      arr: "ARR",
+      formula: "Formula path",
+      assumptions: "Key assumptions",
+    },
+    report: {
+      kicker: "Market forecast report",
+      partialKicker: "Partial report",
+      partialSummary: "The first report section is still being generated.",
+      confidence: "Confidence",
+      scenarios: "Scenarios",
+      sources: "Sources",
+      taskId: "Task ID",
+      inProgress: "In progress",
+      community: "Community activity signals",
+      policy: "Policy trends",
+      sensitivity: "Sensitivity variables",
+      checklist: "Investor diligence checklist",
+      missingEvidence: "Missing evidence",
+      evidenceStrength: "Evidence strength",
+      observedMetric: "Observed metric",
+      observedPeriod: "Observation period",
+      sourceStatus: "Evidence status",
+      researchProtocol: "Research protocol",
+      stabilityCheck: "Stability check",
+      varianceDrivers: "Variance drivers",
+    },
+    sections: {
+      market: "Market definition and TAM/SAM/SOM",
+      forecast: "Users, paid conversion, and ARR forecast",
+      dataVisuals: "Real data and charts",
+      evidence: "Real market evidence",
+      signals: "Community and policy signals",
+      comparables: "Comparable cases and limits",
+      diligence: "Sensitivity, gaps, and diligence",
+    },
+  },
+  guide: {
+    workspaceHeading: "Build a TAM, SAM, and SOM forecast you can challenge",
+    workspaceHint: "Enter product and traction details to generate an evidence-backed fundraising market forecast.",
+    workspaceBadge: "Evidence first",
+    valueKicker: "What you get",
+    valueTitle: "Not a single magic number, but a forecast base investors can question",
+    valueIntro:
+      "The value is not a bigger number. It is putting conclusions, evidence, assumptions, and gaps on the same page so your team can review and improve them.",
+    valueItems: [
+      {
+        title: "Layered market sizing",
+        body: "Break down TAM, SAM, and SOM with the user scope, region, pricing, and service boundary behind each estimate.",
+      },
+      {
+        title: "Three business scenarios",
+        body: "Generate bear, base, and bull forecasts for users, paid users, conversion, ARPU/ACV, and ARR instead of pretending one number is certain.",
+      },
+      {
+        title: "Investor-ready evidence wall",
+        body: "Separate official statistics, company disclosures, public community signals, policy documents, and user inputs. Reports are supporting evidence, not the whole argument.",
+      },
+    ],
+    evidenceKicker: "Evidence standard",
+    evidenceTitle: "Real evidence matters more than polished market reports",
+    evidenceIntro:
+      "Industry reports can help, but they cannot replace checkable public evidence. The report labels source type, relevance, and confidence.",
+    evidenceItems: [
+      "Prioritize official statistics, regulator or policy documents, company disclosures, public product pages, and accessible community discussions.",
+      "Community activity separates member count, recent discussion, repeated pain, buying intent, migration language, and workarounds instead of equating members with users.",
+      "Consulting reports, media rankings, and secondhand market-size numbers are treated as clues; opaque methods reduce confidence.",
+      "Growth assumptions without evidence are listed as missing evidence instead of being stated as facts.",
+    ],
+    boundaryKicker: "Boundary",
+    boundaryTitle: "Fundraising needs conviction, but also honesty",
+    boundaryIntro:
+      "Use this for pitch decks, internal operating models, and investor Q&A preparation. Do not treat it as a guaranteed financial commitment.",
+    boundaryItems: [
+      "Supports: early products, SaaS, AI products, developer tools, community-led products, and fundraising prep with some traction or revenue.",
+      "Does not support: guaranteed fundraising outcomes, private community scraping, logged-in data, fabricated competitor metrics, or replacement of a professional financial model.",
+      "How to use it: verify strong claims source by source, then test them with interviews, sales records, waitlists, ads, or landing-page experiments.",
+      "Best inputs: current users, active users, revenue, pricing, paid conversion, growth history, competitors, target region, and community keywords you already noticed.",
+    ],
+    faqKicker: "FAQ",
+    faqTitle: "TAM, SAM, and SOM forecast FAQs",
+    faqItems: [
+      {
+        question: "Will it give me a market size I can paste into a deck?",
+        answer:
+          "It will give a range and rationale you can adapt, but you still need to verify sources. The best use is as a market slide and investor Q&A draft.",
+      },
+      {
+        question: "How does it estimate active community users?",
+        answer:
+          "It looks at recency, repeated pain, buying or migration intent, alternatives, and the community boundary. Member count is a weak signal and is not treated as active users by itself.",
+      },
+      {
+        question: "How do policy trends affect the forecast?",
+        answer:
+          "Each policy trend is labeled as a tailwind, headwind, or mixed signal, with the expected impact on adoption, sales cycle, compliance cost, or budget release.",
+      },
+      {
+        question: "What if the market evidence is thin?",
+        answer:
+          "The report lowers confidence and lists missing evidence plus next diligence questions. That is useful because it shows where the story is not yet strong.",
+      },
+    ],
+    ctaHint: "Need deeper community evidence first? Run a social listening report. Ready to use the forecast? Move into a pitch deck.",
+    ctaPrimary: "Run social listening",
+    ctaSecondary: "Generate pitch deck",
+  },
+} as const;
+
+export default marketForecastReport;