Start from the real task
Revenue screenshots attract attention, but demand source, product shape, acquisition, delivery cost, and payment path are the reusable parts.
A case is not yet a market
The signal matters when it clarifies a real service task, deliverable, and acceptance rule, not when it only shows a demo.
Check the delivery boundary
- Review every case through demand, product, traffic, delivery, and payment
- Keep the test narrow: one service scenario with clear inputs, deliverables, acceptance rules, and human review
What still needs proof
Use this as a signal or index, not as final proof. Verify key facts through official pages or documentation. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.