Evidence Boundary
Completed
One live Qwen/DashScope refinement pass using qwen-plus with a runtime-only account-owner key.
Still pending
live Alibaba Cloud public endpoint proof remains pending until a real URL returns HTTP 200 for / and /api/plan.
No private material is needed here: the page publishes only model name, public base URL, command shape, exit code, a short sanitized excerpt, and cleanup status.
Before Qwen
| Field | Deterministic plan |
|---|---|
| Primary target | Blog Post Award |
| Secondary target | Top 10 Honorable Mention Projects |
| Core reason | Public project story plus Qwen Cloud evidence can be prepared, while the route still has higher upside than a pure feedback task. |
| Required proof | Qualified Devpost project, public repository, demo video, public blog/social story, Qwen usage evidence, and Alibaba deployment proof. |
Qwen Refinement
| Refinement | Where it appears now |
|---|---|
| Treat the Blog Post Award as tied to a qualified Devpost project. | Blog story, judge pack, and rule verification. |
| Keep the USD 500 / 10-winner value visible while naming Honorable Mention as secondary. | award preflight, award evidence map, and judge pack. |
| Say exactly what the Qwen proof establishes and what it does not. | Qwen live proof, live proof gate, and cloud readiness. |
| Keep no-credentials, no-premature-publishing, no-assumed-infrastructure, and eligibility-first constraints prominent. | Qwen contribution map, Devpost field draft, and Blog Award story. |
After Qwen
- Verify the submitted Devpost project and demo.
- Read the Blog Post Award story as the primary prize narrative.
- Check the judge pack and award evidence map for completed proof versus pending gates.
- Inspect Qwen live proof and this before/after evidence to see the model's role.
- Treat Alibaba endpoint proof as a prepared but unclaimed improvement.
Source Markdown: docs/qwen-before-after-evidence.md. Public hub: PrizePilot evidence hub.