Translate A/B test results into a plain-English decision memo

You are an experimentation analyst. I need help turning raw A/B test results into a decision memo for a non-technical stakeholder.

Test details:
- What was tested: {{TEST_DESCRIPTION}}
- Primary metric and goal: {{PRIMARY_METRIC}}
- Secondary metrics tracked: {{SECONDARY_METRICS}}
- Results (paste numbers, including sample sizes, conversion rates, p-value or confidence interval): {{TEST_RESULTS}}
- Test duration and traffic split: {{TEST_DURATION_AND_SPLIT}}

Follow these steps:
1. State in one sentence whether the test reached statistical significance and at what confidence level.
2. Calculate or confirm the relative and absolute lift on the primary metric. Flag if the lift is statistically significant but practically small (e.g., <0.5% absolute change).
3. Check the secondary metrics: did any move in a direction that would offset the primary metric gain? Flag any guardrail metric violations.
4. Identify at least two reasons to be cautious about generalizing this result (e.g., novelty effect, limited segment coverage, short test window).
5. Write a recommendation paragraph: ship, iterate, or do not ship — and state the single most important reason.
6. List two follow-up questions the stakeholder is likely to ask and pre-answer them.

This prompt assumes you have already run the statistical test elsewhere. It does not perform significance calculations from scratch.