Two valid starting conditions feed one demand-to-outcome engine: an existing offer can be tested against real demand, or a market can be explored before any product exists. Both branches must produce the same validated opportunity-and-offer contract before entering the shared EP050 execution pipeline.
Evidence boundary. Branch B may generate hypotheses, never facts. A discovered app or service concept cannot enter the shared engine until real problem evidence, a defined audience, a testable proposition and explicit success/rejection criteria exist. Neither branch authorizes scraping, publishing, outreach, spend, lead routing or any other external action.
A
Existing product or service
The operator already has an offer and wants to determine whether real commercial demand supports it.
→→
B
No product or service yet
The operator defines a market, audience or problem territory and searches for a product opportunity worth testing.
→→→→
↓
Y-branch merge point
Both branches must emit this exact canonical contract. Downstream nodes do not need to know which branch created it.
↓
Shared demand-to-outcome engine
From this point both branches use one implementation, one state model and one evidence lineage.