product-framing git:20261014.924cdc9A

Immutable. This exact content never changes and is served at /api/v1/blob/ef68d39ca3b622f2.

---
name: product-framing
description: Structure a bounded product opportunity inquiry and preserve evidence limits.
---

# Product Framing

Treat product framing as a research question, not a demand verdict. Record user, buyer, and payer separately; state the context and current workaround; include status quo or no-build as an alternative; and distinguish observed, derived, assumed, and unknown claims. An observed claim requires a raw evidence reference and a matching source record that identifies who observed it and when. A user report remains user-reported unless independently observed. Keep synthetic examples explicitly synthetic.

Apply the source-family, duplicate, counterevidence, conflict-group, availability, and publication-date rules in [Claim Quality](claim-quality.md). Preserve distinct source records when sources conflict; never combine them into one neutral or majority claim. A source family records common origin, while a duplicate group explicitly groups records that repeat that origin. `unavailable` means the source could not be accessed or checked; it does not mean a completed search found nothing. Use `published_at: null` when publication time is unknown, and do not infer it from retrieval or observation time.

Create an opportunity brief before a research protocol. Capture uncertainty and the next discriminating action. A complete structure does not establish truth, demand, semantic source quality, or permission to act. Use existing task acceptance and evidence gates for completion; artifact labels never authorize spending, contact, publication, deployment, or delivery.