Analyze the Request/Constraints:

1. Analyze the Request:

• Task: Write complete public web page copy for "Analyze the Request/Constraints:"
• Format: Markdown with headings, short paragraphs, bullet lists
• Plan provided: Includes goalMetric, checkpointHours, killRule, boostRule, cloneRule, channel, distributionPlan, maintenancePlan
• Requirements:
• 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 info: venture:eca71a-fc68-4803-8ab4-c7603132234c, stage:APPROVE_PUBLISH, task:293d59ae-85b9-4e7b-b971-c28afaec5952

1. Deconstruct the "Plan" Section:

• goalMetric: constraintAnalysisAccuracy
• checkpointHours: 4
• killRule: maxIterationsWithoutRevenue: 5
• boostRule: minRevenueUsd: 20
• cloneRule: minRevenueUsd: 10
• channel: owned-site
• distributionPlan: Published on the venture's owned‑site landing page, promoted via the venture's newsletter, blog, and social media channels; made freely downloadable as a PDF checklist.
• maintenancePlan: Quarterly review of the constraint‑analysis test results, update the checklist based on new venture requests, and incorporate user feedback to improve clarity and coverage.

I need to integrate these meaningfully but honestly. The prompt says "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 should reference the plan parameters accurately but not fabricate fake metrics or testimonials. I can include the plan details as part of the page's transparent description, but without making up numbers that aren't given, or I should stick to the given plan values truthfully.

Wait, the plan has specific values like checkpointHours: 4, maxIterationsWithoutRevenue: 5, minRevenueUsd: 20, minRevenueUsd: 10. These are internal venture parameters. The page copy is for "Analyze the Request/Constraints:" which seems to be a public web page copy. I need to write the copy, and presumably incorporate or reference the plan honestly, but without inventing fake claims. The plan details might be part of the page's "About" or "How It Works" section, but I must be careful not to exaggerate or fabricate.

Let's re-read carefully: "Write the complete public web page copy for 'Analyze the Request/Constraints:' (markdown: headings, short paragraphs, bullet lists). Plan: {...}. 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 the output should be the web page copy in markdown. The "Plan" is probably metadata/context for me to write the copy accurately, but the copy itself should be honest, specific, no fake stuff. I should likely include the plan's intent/description truthfully, maybe as a transparent section, but not invent numbers beyond what's given, and certainly no prices or payment buttons.

Structure of the page:

• Heading: "Analyze the Request/Constraints"
• Brief intro/what it is
• Who it's for
• How it works (incorporating plan elements honestly)
• Distribution/maintenance info (from plan)
• Maybe a transparent note about the venture's framework

I need to avoid making up anything not in the prompt. The plan has goalMetric, checkpointHours, killRule, boostRule, cloneRule, channel, distributionPlan, maintenancePlan. I can describe these in general, honest terms, without fabricating. For example: "This initiative operates with a 4-hour checkpoint to review constraint analysis accuracy. If no progress is made within 5 iterations without meeting revenue thresholds, the project is paused. Revenue thresholds of $10-$20 trigger cloning or boosting mechanisms..." But wait, the prompt says "no fake testimonials, numbers or claims." The numbers in the plan are given, so I can reference them as part of the venture's framework, but I should be careful. Actually, the prompt says "Be honest and specific about what it is and who it is for; no fake testimonials, numbers or claims." This likely means don't make up fake user testimonials, don't invent fake usage statistics, don't claim fake benefits. The plan numbers are part of the task context, so I can include them factually as given, but perhaps frame them as "internal parameters" or "venture framework metrics" rather than claims about performance.

Let's think about what "Analyze the Request/Constraints:" actually is. It's a public web page copy. Probably a landing page or a tool description. Given the venture context, it's likely a framework or checklist for analyzing requests/constraints in venture building. The plan describes its lifecycle, distribution, metrics.

I'll structure the markdown copy with:

• Main heading
• Subheading explaining what it is
• Who it's for (honest, specific)
• How it works (bullet points referencing the plan parameters truthfully)
• Distribution & maintenance (from plan)
• No fake anything.

Let's draft:

   # Analyze the Request/Constraints

   A framework for systematically parsing venture requests against operational constraints, enabling faster alignment, clearer trade-offs, and more reliable go/no‑go decisions.

   **Who this is for**
   - Founders and product leads who need to rapidly evaluate new ideas against resource, time, and revenue constraints
   - Venture teams managing multiple concurrent projects who want a consistent analysis lens
   - Anyone building or scaling a venture who wants to move from intuition‑based calls to structured constraint analysis

   **How it works**
   - **Constraint mapping**: Identify the request’s core requirements, then map them against known venture constraints (timeline, capital, team capacity, market fit).
   - **Metric check**: Apply the goal metric—constraint analysis accuracy—to score the alignment. A 4‑hour checkpoint reviews each analysis for completeness.
   - **Decision rules**: 
     - If the analysis meets accuracy thresholds, the request proceeds.
     - If no progress is made within 5 iterations without meeting minimum revenue relevance ($10–$20 range), the process is paused (kill rule).
     - If milestones are hit, the framework can be cloned or boosted for broader application.
   - **Output**: A concise constraint report ready for review, feedback, or PDF export.

   **Distribution**
   Published on the venture’s owned‑site landing page, promoted via the venture’s newsletter, blog, and social media channels. Made freely downloadable as a PDF checklist.

   **Maintenance**
   Quarterly review of constraint‑analysis test results, with updates based on new venture requests and user feedback to improve clarity and coverage.

Check against requirements:

• Markdown headings: yes
• Short paragraphs: yes
• Bullet lists: yes
• Honest and specific about what it is and who it's for: yes
• No fake testimonials, numbers, or claims: I referenced the plan's numbers ($10–$20, 5 iterations, 4-hour checkpoint) but framed them as part of the venture's decision framework, not as proven results or testimonials. I should be careful not to present them as claims of effectiveness. Maybe rephrase to "internal thresholds" or "venture framework parameters". The prompt says "no fake... numbers or claims." The numbers are real in the context, but I should perhaps avoid stating them as if they're performance metrics, and instead as "venture framework parameters". Let's adjust.

Actually, re-reading: "Be honest and specific about what it is and who it is for; no fake testimonials, numbers or claims." This likely means don't make up fake user numbers, success rates, testimonials. The plan's numbers are part of the task, so I can include them factually, but I'll frame them as "venture framework parameters" to stay safe. I won't emphasize them as proven results.

Let's also ensure I don't invent prices or payment buttons. I won't include any $ signs for pricing, just the plan's minRevenueUsd references as framework thresholds, but maybe better to avoid explicit dollar amounts in the copy to stay strictly "no prices". The plan has priceUsd:0 and minRevenueUsd values. I'll just say "relevance thresholds" or keep it generic without pricing language.

Revised draft avoiding explicit price mentions in copy:

   # Analyze the Request/Constraints

   A structured framework for parsing venture requests against operational constraints, helping teams clarify trade-offs and make timely go/no‑go decisions.

   **What it does**
   - Maps each request to key constraint categories (timeline, capacity, capital, market alignment).
   - Scores analysis against a goal metric of constraint analysis accuracy.
   - Triggers review checkpoints every 4 hours to assess progress.
   - Applies decision rules: after 5 iterations without meeting relevance thresholds, the process is