primitive-market-research

name	primitive-market-research
description	Map product-market evidence, users, alternatives, substitutes, competitors, antagonists, pricing, and capability fit before admitting a WEAVE application.

Primitive Market Research

Use When

Use this skill before selecting or building a WEAVE application when product, user, customer, market, pricing, competitor, substitute, antagonist, or value uncertainty is material.

Inputs

• target market or app idea
• target users and use cases
• customer or audience segment
• capability sources
• capability context index or source manifest
• pricing, competitor, substitute, or antagonist sources
• known constraints

Outputs

• product-market facts
• capability map
• context sources checked
• customer segment
• alternatives and substitutes
• competitor, antagonist, and pricing evidence
• disconfirming evidence and reasons the app may not matter
• constraints and risk gates
• technical feasibility evidence
• primitive fit mapping
• ranked opportunity list
• sourced facts, assumptions, and opinions separated clearly
• admit, park, or block decision

Rules

• Use current source evidence when pricing, availability, or competitors may have changed.
• Use the WEAVE capability context index when one is available, then verify volatile claims from primary sources before implementation or public claims.
• Separate evidence-backed claims from assumptions.
• Keep opinions separate from sourced facts and assumptions.
• Do not pass Research on technical feasibility alone while product, user, customer, alternative, substitute, competitor, antagonist, or value uncertainty remains central.
• Admit exactly one wedge before Planning.
• Park attractive alternatives explicitly.

Stop Conditions

• The capability cannot be verified enough to support selection.
• The customer segment or use case is too vague to plan.
• Research would require private account access or paid execution.

Verification

Research is ready when the selected wedge, parked alternatives, and missing questions are visible in the evidence packet, and the readback separates sourced facts, assumptions, and opinions.