Analyze the User's Request:

1. Analyze the Request:

• Core Task: Write complete public web page copy for "Analyze the User's Request:"
• Format: Markdown (headings, short paragraphs, bullet lists)
• Plan Details Provided:
• Goal Metric: completed validation submissions
• Checkpoint Hours: 48
• Kill Rule: maxIterationsWithoutRevenue: 3
• Boost Rule: minRevenueUsd: 10
• Clone Rule: minRevenueUsd: 5
• Channel: owned-site
• Price Usd: 0
• Distribution Plan: Publish the validation test on the venture's free website, promote via social media and email newsletter to attract target users.
• Maintenance Plan: Monitor submissions weekly, update test questions based on feedback, and ensure site uptime.
• Constraints:
• Be honest and specific about what it is and who it is for
• No fake testimonials, numbers or claims
• Do not invent prices, links or payment buttons
• Venture/Stage/Task Metadata: venture:7cec11ef-de6d-41f4-89c7-08660c2c6903 stage:APPROVE_PUBLISH task:3cdc13b0-d197-4cef-80f1-769ed26ec938

1. Deconstruct the "Product/Service":

• The prompt asks for a public web page copy for "Analyze the User's Request:" - this seems like a meta or self-referential title, but likely means: write the copy for a validation test or tool page titled/related to analyzing user requests.
• Based on the plan: It's a free validation test published on an owned site. Goal is completed validation submissions. Price is $0. It's a test/questionnaire to gather data/feedback.
• Who it's for: Target users, likely product designers, founders, researchers, or people interested in validation. The plan says "attract target users."
• No fake numbers/testimonials. No invented prices/links.

1. Identify the Core Offering:

• It's a free validation test/submission form.
• Purpose: To analyze user requests (probably for product feedback, research, or validation).
• Metrics: completed validation submissions within 48 hours checkpoint.
• Rules: kill/boost/clone rules seem like internal business logic, but I should incorporate the essence without making up fake details. The prompt says "Be honest and specific about what it is and who it is for; no fake testimonials, numbers or claims." So I should mention the goals/metrics honestly but not invent exaggerated numbers. I can reference the given plan parameters as factual descriptors.
• Price: $0 (free).
• Distribution: owned site, social media, email newsletter.
• Maintenance: weekly monitoring, updates based on feedback, uptime.

1. Draft Structure (Markdown):

• Main heading: Maybe "Analyze the User's Request" or a descriptive title. The prompt says "Write the complete public web page copy for 'Analyze the User's Request:'" so the page is likely centered around that concept. I'll make the main title/heading reflect that.
• Sections: What it is, Who it's for, How it works, Goals & Checkpoints, Rules (briefly, honestly), Distribution & Free Access, Maintenance.
• Keep paragraphs short. Use bullet lists where appropriate.
• No fake testimonials. No invented links/buttons/prices beyond what's given ($0).

Let's outline:

   # Analyze the User's Request

   A free validation test designed to help founders, product teams, and researchers quickly gather structured feedback on ideas, features, or concepts.

   Who this is for:
   - Independent makers and solopreneurs
   - Small product teams seeking rapid validation
   - Researchers needing consistent user request data

   How it works:
   - Submit a concise description of your request or idea
   - Receive a structured analysis framework
   - Contribute to a growing dataset of validated user needs

   Goal & Timeline:
   - Target: completed validation submissions within 48 hours of publication
   - Success measured by submission volume and quality

   Participation Rules (transparently shared):
   - No revenue required to participate – it's free ($0)
   - Internal metrics guide test iteration (kill/boost/clone rules applied post-analysis)
   - Results feed into ongoing platform improvements

   How to Participate:
   - Visit the hosted test page
   - Submit your request via the simple form
   - Share with your network to boost response rate

   Stay Updated:
   - Weekly feedback summaries posted on the site
   - Questions and framework updated based on participant input
   - Site uptime monitored; issues resolved promptly

Wait, I need to be careful not to invent numbers or claims that aren't in the prompt. The prompt gives specific plan parameters: goalMetric, checkpointHours, killRule, boostRule, cloneRule, channel, priceUsd:0, distributionPlan, maintenancePlan. I should incorporate these faithfully, but without making up extra stats. I can restate them accurately.

Let re-read constraints: "Be honest and specific about what it is and who it is for; no fake testimonials, numbers or claims. Do not invent prices, links or payment buttons."

So I can mention priceUsd:0, checkpointHours:48, goalMetric, etc., as long as I don't invent fake numbers beyond what's given. I should not say "we expect 100 submissions" etc. I'll stick to the given parameters.

Also, the page is for "Analyze the User's Request:" - I'll make the heading exactly that or a natural page title around it.

Let's structure markdown properly:

• Main heading: Analyze the User's Request
• Subheading/description
• Bullet lists for who it's for, how it works, rules, etc.
• Short paragraphs.

I need to ensure I don't add fake "success stories" or "users say". Just factual copy based on the plan.

Draft:

   # Analyze the User's Request

   This page hosts a free validation test designed to capture and structure user requests for product ideas, features, or research questions. It is published on an owned site with no participation fee.

   **Who this is for**
   - Founders and solopreneurs testing early-stage concepts
   - Product teams collecting structured user feedback
   - Researchers seeking consistent request datasets

   **How it works**
   - Submit a brief description of your request or idea
   - The submission is logged toward the 48-hour checkpoint goal
   - Analysis feeds into ongoing platform improvement cycles

   **Participation goals and rules**
   - **Goal metric:** completed validation submissions
   - **Checkpoint:** 48 hours from publication
   - **Kill rule:** maximum 3 iterations without revenue-generating traction (internal metric, not a barrier to participation)
   - **Boost rule:** minimum $10 revenue threshold applied post-analysis for certain feature prioritization tracks
   - **Clone rule:** minimum $5 revenue threshold for replication consideration
   - **Price to participate:** $0 (free)
   - **Channel:** owned-site distribution

   **Distribution**
   The test will be promoted via the venture’s social media channels and email newsletter to attract the target user base.

   **Maintenance**
   - Submissions monitored weekly
   - Test questions updated based on direct feedback
   - Site uptime ensured; issues addressed promptly

Check against constraints:

• Honest/specific: yes
• No fake testimonials/numbers: I only use given parameters, no invented stats
• No invented prices/links/buttons: price is $0, no links mentioned, no payment buttons
• Incorporates all plan fields accurately
• Markdown format with headings, short paragraphs, bullet lists

One thing: "killRule":{"maxIterationsWithoutRevenue":3} - I should not frame it as a penalty for users. The prompt says "Be honest and specific about what it is and who it is for". The rules seem like internal business logic. I'll phrase them neutrally, maybe as "internal iteration guidelines" or just list them as part of the plan without implying users are "killed". The prompt says "no fake numbers or claims". I'll just restate the rules as given, but carefully. Maybe better to say "Internal iteration guidelines include:" and list them, noting they guide test refinement, not user eligibility. Or I could omit the kill/boost/clone rule details if they'd confuse the public page, but the prompt includes them in the plan, so likely expects them to be reflected honestly. I'll include them as transparently shared plan parameters, but phrase carefully.

Let's refine: The venture is at stage APPROVE_PUBLISH, task is to publish the validation test. The copy should be a public web page. I'll make sure the kill/boost/clone rules are presented as part of the venture's internal framework, not as user constraints. Or maybe just skip detailing them if they're not relevant to the public, but the prompt explicitly gave them, so I should include them faithfully. I'll phrase: "The venture operates with the following internal frameworks (shared for transparency):" then list them.