Previous value: -"Optional: the user's own email, provided by them in chat for report delivery. Ask: 'Want the report emailed to you?' Only pass an address the user explicitly shared for this purpose. Leave blank if they have not shared it."New value: +"Optional: the user's own email, provided by them in chat for report delivery. Providing it gets them the full Market Research Report emailed to them - SAM, TAM, competitive landscape, GTM strategy and positioning, opportunities and risks; without it they only receive the teaser. Ask: 'Want the full Market Research Report emailed to you? Share an email address (optional).' Only pass an address the user explicitly shared for this purpose. Leave blank if they have not shared it."

Previous value: -"Optional: the user's email if they want the report deliverables sent there. Ask: 'Want the report emailed to you?' Leave blank if they have not shared it."New value: +"Optional: the user's own email, provided by them in chat for report delivery. Ask: 'Want the report emailed to you?' Only pass an address the user explicitly shared for this purpose. Leave blank if they have not shared it."

Removed value: -80

Removed value: -200

Removed value: -200

Removed value: -200

Removed value: -{
-  "description": "Optional - set this ONLY when polling an in-progress report. If a previous start_demand_report response had reportGenerating: true, pass back the reportId it returned (along with the same name/problem/solution and the email) to pull the finished brief inline. Leave blank on the first call for an idea.",
-  "type": "string"
-}

Previous value: -"True if only Part 1 was returned and no email was given yet. When true, ask the user for their email and call start_demand_report again with the same fields plus the email to unlock the rest inline."New value: +"True if the score-free Market Research summary was returned but no email was given yet. When true, show the summary verbatim, then ask the user for their email and call start_demand_report again with the same fields plus the email."

Previous value: -"Deep link to continue into the $49 Demand Discovery Report step. Omitted while the report is still generating."New value: +"Deep link to continue into the $49 Demand Discovery Report step."

Previous value: -"True if the full report was emailed to the user's address."New value: +"True if the full Market Research report has been emailed to the user's address."

Previous value: -"The free Market Research brief (Part 1 alone, or the full report), returned inline so the agent can read and use it without the user leaving chat."New value: +"The score-free Market Research summary, returned inline so the agent can show it to the user verbatim without them leaving chat. The full report is delivered by email."

Previous value: -"True if this is Part 1 only; an email unlocks the rest."New value: +"True if this is the score-free summary only; the full report is emailed."

Previous value: -"True only when the full report (both parts) was returned inline. False while only Part 1 has been delivered or while the rest is still generating."New value: +"True once the user has provided an email and the Market Research summary was delivered inline (the full report is then emailed). False while still awaiting the user's email, or when only a deep link was returned."

Previous value: -"True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, automatically call start_demand_report again (without waiting for the user) with the same fields, the email, and the reportId. Each call waits for the brief on the server and may take up to a minute to return; keep re-calling right away whenever reportGenerating is still true, until reportComplete is true, then show the finished brief inline (it usually completes in about 2 minutes but can run longer; if still generating after ~3 minutes, stop and tell the user the brief will arrive by email). Judge state from this flag, not the markdown — every generating response repeats the same Part 1 teaser by design, so seeing it again is not a loop or a reset; keep polling the SAME reportId, do not start over. Keep the report inline (a copy is also emailed as a backup) and do NOT offer the paid step until reportComplete is true."New value: +"Always false. The free Market Research is delivered as an inline score-free summary plus a full report sent by email; there is nothing to poll or wait for inline. Retained for output-schema stability."

Previous value: -"The DD identifier for this idea's report, present once Market Research has started. When reportGenerating is true, pass this back as the reportId argument on the next start_demand_report call to poll for the finished brief."New value: +"The DD identifier for this idea's Market Research record, present once it has started. Pass it to validate_real_demand to tie the paid $49 order to this exact record."

Previous value: -"Deep link to the free Market Research entry point with all form fields prefilled. Omitted while the report is still generating (reportGenerating: true) so the user is never sent to a link mid-stream."New value: +"Deep link to the free Market Research entry point with all form fields prefilled, used as a fallback when inline delivery was unavailable."

Previous value: -"True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, automatically call start_demand_report again (without waiting for the user) with the same fields, the email, and the reportId about every 10-15 seconds until reportComplete is true, then show the finished brief inline (it usually completes in about 2 minutes but can run longer; if still generating after ~3 minutes, stop and tell the user the brief will arrive by email). Judge state from this flag, not the markdown — every generating response repeats the same Part 1 teaser by design, so seeing it again is not a loop or a reset; keep polling the SAME reportId, do not start over. Keep the report inline (a copy is also emailed as a backup) and do NOT offer the paid step until reportComplete is true."New value: +"True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, automatically call start_demand_report again (without waiting for the user) with the same fields, the email, and the reportId. Each call waits for the brief on the server and may take up to a minute to return; keep re-calling right away whenever reportGenerating is still true, until reportComplete is true, then show the finished brief inline (it usually completes in about 2 minutes but can run longer; if still generating after ~3 minutes, stop and tell the user the brief will arrive by email). Judge state from this flag, not the markdown — every generating response repeats the same Part 1 teaser by design, so seeing it again is not a loop or a reset; keep polling the SAME reportId, do not start over. Keep the report inline (a copy is also emailed as a backup) and do NOT offer the paid step until reportComplete is true."

Previous value: -"True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, automatically call start_demand_report again (without waiting for the user) with the same fields, the email, and the reportId about every 10-15 seconds until reportComplete is true, then show the finished brief inline (it usually completes within ~90 seconds; if still generating after ~3 minutes, stop and tell the user the brief will arrive by email). Judge state from this flag, not the markdown — every generating response repeats the same Part 1 teaser by design, so seeing it again is not a loop or a reset; keep polling the SAME reportId, do not start over. Keep the report inline (a copy is also emailed as a backup) and do NOT offer the paid step until reportComplete is true."New value: +"True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, automatically call start_demand_report again (without waiting for the user) with the same fields, the email, and the reportId about every 10-15 seconds until reportComplete is true, then show the finished brief inline (it usually completes in about 2 minutes but can run longer; if still generating after ~3 minutes, stop and tell the user the brief will arrive by email). Judge state from this flag, not the markdown — every generating response repeats the same Part 1 teaser by design, so seeing it again is not a loop or a reset; keep polling the SAME reportId, do not start over. Keep the report inline (a copy is also emailed as a backup) and do NOT offer the paid step until reportComplete is true."

Previous value: -"True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, automatically call start_demand_report again (without waiting for the user) with the same fields, the email, and the reportId about every 30 seconds until reportComplete is true, then show the finished brief inline. Keep the report inline (a copy is also emailed as a backup) and do NOT offer the paid step until reportComplete is true."New value: +"True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, automatically call start_demand_report again (without waiting for the user) with the same fields, the email, and the reportId about every 10-15 seconds until reportComplete is true, then show the finished brief inline (it usually completes within ~90 seconds; if still generating after ~3 minutes, stop and tell the user the brief will arrive by email). Judge state from this flag, not the markdown — every generating response repeats the same Part 1 teaser by design, so seeing it again is not a loop or a reset; keep polling the SAME reportId, do not start over. Keep the report inline (a copy is also emailed as a backup) and do NOT offer the paid step until reportComplete is true."

Previous value: -"True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, do NOT offer the paid step and do NOT point the user at a link or their inbox - wait ~30-60s and call start_demand_report again with the same fields (plus the email, if you have it) to pull the next section inline; repeat until reportComplete is true."New value: +"True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, automatically call start_demand_report again (without waiting for the user) with the same fields, the email, and the reportId about every 30 seconds until reportComplete is true, then show the finished brief inline. Keep the report inline (a copy is also emailed as a backup) and do NOT offer the paid step until reportComplete is true."

Added value: +{
+  "description": "Optional - set this ONLY when polling an in-progress report. If a previous start_demand_report response had reportGenerating: true, pass back the reportId it returned (along with the same name/problem/solution and the email) to pull the finished brief inline. Leave blank on the first call for an idea.",
+  "type": "string"
+}

Previous value: -"Deep link to continue into the $49 Demand Discovery Report step."New value: +"Deep link to continue into the $49 Demand Discovery Report step. Omitted while the report is still generating."

Previous value: -"True if the full report (both parts) was returned inline. False while only Part 1 has been delivered."New value: +"True only when the full report (both parts) was returned inline. False while only Part 1 has been delivered or while the rest is still generating."

Added value: +{
+  "description": "True when the full report is still being generated and only the portion ready so far was returned inline (in `report`). When true, do NOT offer the paid step and do NOT point the user at a link or their inbox - wait ~30-60s and call start_demand_report again with the same fields (plus the email, if you have it) to pull the next section inline; repeat until reportComplete is true.",
+  "type": "boolean"
+}

Added value: +{
+  "description": "The DD identifier for this idea's report, present once Market Research has started. When reportGenerating is true, pass this back as the reportId argument on the next start_demand_report call to poll for the finished brief.",
+  "type": "string"
+}

Previous value: -"Deep link to the free Market Research entry point with all form fields prefilled."New value: +"Deep link to the free Market Research entry point with all form fields prefilled. Omitted while the report is still generating (reportGenerating: true) so the user is never sent to a link mid-stream."

Previous value: -[
-  "reportDelivered",
-  "reportComplete",
-  "awaitingEmail",
-  "freeReportLimitReached",
-  "emailed",
-  "reportUrl",
-  "continueUrl",
-  "namePrefilled",
-  "descriptionPrefilled",
-  "emailCaptured",
-  "targetMarketProvided",
-  "bundle",
-  "upsellTo",
-  "nextAction",
-  "productUrl"
-]New value: +[
+  "reportDelivered",
+  "reportComplete",
+  "reportGenerating",
+  "awaitingEmail",
+  "freeReportLimitReached",
+  "emailed",
+  "namePrefilled",
+  "descriptionPrefilled",
+  "emailCaptured",
+  "targetMarketProvided",
+  "bundle",
+  "upsellTo",
+  "nextAction",
+  "productUrl"
+]

Added value: +{
+  "description": "Optional: what the user's target customers currently use to deal with this problem - the manual or duct-tape workaround (e.g. 'they juggle spreadsheets + manual email reminders'). Populate it ONLY if the conversation already revealed how people cope today; do NOT ask an extra question for it and never block the call if it is unknown - empty is fine. Existing effort or spend is a strong demand signal, and it sharpens the downstream demand search in both the free Market Research and the paid Demand Discovery report.",
+  "type": "string"
+}

Previous value: -"One sentence describing the problem the idea solves. Ask the user: 'What problem are you solving?' Example: 'Early-stage SaaS founders waste 200+ hours hand-collecting SOC 2 evidence before their first audit.'"New value: +"One sentence describing the problem the idea solves. Keep it clear and specific - this answer shapes the full Demand Discovery report. Ask the user: 'What problem are you solving?' Example: 'Early-stage SaaS founders waste 200+ hours hand-collecting SOC 2 evidence before their first audit.'"

Previous value: -"Optional short phrase describing the target customer or ICP. Ask the user: 'Who is your target market?' Skip if they are unsure. Example: 'Pre-Series-A SaaS startups under 50 employees preparing for their first SOC 2 Type 1.'"New value: +"Optional short phrase describing the target customer or ICP; aim for a specific role plus company size or stage so the demand search can target the right people. Ask the user: 'Who is your target market?' Skip if they are unsure. Example: 'Heads of Ops at 50-200 person companies' or 'Pre-Series-A SaaS founders preparing for their first SOC 2 Type 1.'"

Added value: +{
+  "description": "True if only Part 1 was returned and no email was given yet. When true, ask the user for their email and call start_demand_report again with the same fields plus the email to unlock the rest inline.",
+  "type": "boolean"
+}

Added value: +{
+  "description": "Deep link to continue into the $49 Demand Discovery Report step.",
+  "type": "string"
+}

Added value: +{
+  "description": "True if the full report was emailed to the user's address.",
+  "type": "boolean"
+}

Added value: +{
+  "description": "True if the provided email already used its one free Market Research report; only the paid Demand Discovery Report remains.",
+  "type": "boolean"
+}

Added value: +{
+  "additionalProperties": false,
+  "description": "The free Market Research brief (Part 1 alone, or the full report), returned inline so the agent can read and use it without the user leaving chat.",
+  "properties": {
+    "markdown": {
+      "type": "string"
+    },
+    "partial": {
+      "description": "True if this is Part 1 only; an email unlocks the rest.",
+      "type": "boolean"
+    },
+    "reportId": {
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "markdown"
+  ],
+  "type": "object"
+}

Added value: +{
+  "description": "True if the full report (both parts) was returned inline. False while only Part 1 has been delivered.",
+  "type": "boolean"
+}

Added value: +{
+  "description": "True if any Market Research content was returned inline in this response (in `report`); false if only a deep link was returned, or the free-report limit was reached.",
+  "type": "boolean"
+}

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "founder",
+        "studio"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Set when the user has exhausted their current pack: 'founder' (Validate exhausted, 3rd report) or 'studio' (Founder exhausted, 6th report). Null when no upsell is active."
+}

Added value: +{
+  "description": "Upgrade checkout link, present only when upsellTo is set.",
+  "type": "string"
+}

Previous value: -[
-  "reportUrl",
-  "namePrefilled",
-  "descriptionPrefilled",
-  "emailCaptured",
-  "targetMarketProvided",
-  "bundle",
-  "nextAction",
-  "productUrl"
-]New value: +[
+  "reportDelivered",
+  "reportComplete",
+  "awaitingEmail",
+  "freeReportLimitReached",
+  "emailed",
+  "reportUrl",
+  "continueUrl",
+  "namePrefilled",
+  "descriptionPrefilled",
+  "emailCaptured",
+  "targetMarketProvided",
+  "bundle",
+  "upsellTo",
+  "nextAction",
+  "productUrl"
+]

Removed value: -{
-  "description": "Optional: extra context the user has shared about the idea, ICP, or what they have already tried.",
-  "maxLength": 1000,
-  "type": "string"
-}

Previous value: -"Optional: the user's email if they want their report deliverables sent there. Leave blank if they have not shared it."New value: +"Optional: the user's email if they want the report deliverables sent there. Ask: 'Want the report emailed to you?' Leave blank if they have not shared it."

Removed value: -{
-  "description": "Describe the user's startup idea. Before calling this tool, ask the user these three questions and combine the answers into this field: (1) What problem are you solving? (2) What is your solution? (3) Who is the target market or ICP? Problem and solution are the most important - target market is helpful but optional if the user is unsure. Two to four sentences is ideal. Example: 'Early-stage SaaS founders waste 200+ hours hand-collecting SOC 2 evidence before their first audit. We auto-generate the full evidence package from their existing cloud infrastructure, identity provider, and source-control systems. Target: pre-Series-A SaaS startups under 50 employees preparing for their first SOC 2 Type 1.'",
-  "maxLength": 800,
-  "minLength": 8,
-  "type": "string"
-}

Added value: +{
+  "description": "Short startup or product name. One sentence or less, ideally one to three words. Example: 'AgenticLaunch', 'SOC2 Auto-Evidence'. Ask the user: 'What is the name of your startup or product?'",
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}

Added value: +{
+  "description": "One sentence describing the problem the idea solves. Ask the user: 'What problem are you solving?' Example: 'Early-stage SaaS founders waste 200+ hours hand-collecting SOC 2 evidence before their first audit.'",
+  "maxLength": 200,
+  "minLength": 5,
+  "type": "string"
+}

Added value: +{
+  "description": "One sentence describing how the idea solves the problem. Ask the user: 'What is your solution?' Example: 'We auto-generate the full evidence package from their existing cloud infrastructure, identity provider, and source-control systems.'",
+  "maxLength": 200,
+  "minLength": 5,
+  "type": "string"
+}

Added value: +{
+  "description": "Optional short phrase describing the target customer or ICP. Ask the user: 'Who is your target market?' Skip if they are unsure. Example: 'Pre-Series-A SaaS startups under 50 employees preparing for their first SOC 2 Type 1.'",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

Previous value: -[
-  "idea"
-]New value: +[
+  "name",
+  "problem",
+  "solution"
+]

Removed value: -{
-  "description": "True if the user provided extra context.",
-  "type": "boolean"
-}

Added value: +{
+  "description": "The problem + solution one-line description that was prefilled.",
+  "type": "string"
+}

Removed value: -{
-  "description": "The idea text that was prefilled into the report URL.",
-  "type": "string"
-}

Added value: +{
+  "description": "The startup name that was prefilled.",
+  "type": "string"
+}

Previous value: -"Deep link to the free Market Research entry point with the idea prefilled."New value: +"Deep link to the free Market Research entry point with all form fields prefilled."

Added value: +{
+  "description": "The target market that was prefilled, if provided.",
+  "type": "string"
+}

Added value: +{
+  "description": "True if the user provided a target market.",
+  "type": "boolean"
+}

Previous value: -[
-  "reportUrl",
-  "ideaPrefilled",
-  "emailCaptured",
-  "contextProvided",
-  "bundle",
-  "nextAction",
-  "productUrl"
-]New value: +[
+  "reportUrl",
+  "namePrefilled",
+  "descriptionPrefilled",
+  "emailCaptured",
+  "targetMarketProvided",
+  "bundle",
+  "nextAction",
+  "productUrl"
+]