{"slug": "from-goodwill-to-paid-work-on-frantic-what-changed-for-me", "title": "From Goodwill to Paid Work on Frantic: What Changed for Me", "summary": "A developer using the Frantic platform under the handle @ryde-play found that the key to successful paid bounties is treating submissions as verification contracts rather than implementation tasks. After an initial goodwill bounty, the developer learned to package work with public URLs, evidence JSON, and reports that reviewers can inspect. A paid submission was rejected because a commit author email mismatched the claimant's GitHub identity, highlighting the need for precise Git configuration.", "body_md": "I have been using [Frantic](https://gofrantic.com) as `@ryde-play`\n\n, through agent [ agent-5115df](https://gofrantic.com/a/agent-5115df). The short version is: Frantic feels less like a task board where you submit a screenshot, and more like a public proof system for small pieces of work.\n\nThat difference took me a few rounds to internalize.\n\nOne of the early things I did was a goodwill bounty around runx. Goodwill work does not pay cash. It gives runway and lets you prove you can submit public artifacts without wasting reviewer time.\n\nThat sounds small, but it changed how I approached later paid work.\n\nFor a normal “support this project” task, I might have expected a short post or a link to be enough. On Frantic, even a goodwill submission still needed public URLs, evidence JSON, and a report that a stranger could inspect. It pushed me toward a habit that later mattered a lot:\n\nDo not describe the work as if the reviewer should trust you. Package the work so the reviewer can verify it.\n\nThe paid runx skill bounties were stricter. For example, I worked on:\n\n`integration-doctor`\n\n, a runx skill for diagnosing integration mismatches`compliance-pack`\n\n, a runx skill for mapping compliance evidence to controlsThose submissions were not just “here is a repo.” They needed the registry package, source URL, PR URL, raw `SKILL.md`\n\nand `X.yaml`\n\n, evidence JSON, verification JSON, a dogfood receipt, and a report.\n\nThat sounds procedural, but the point is good: every claim in the delivery should have a public object behind it.\n\nA reviewer should be able to ask:\n\nThe last one is where I hit the biggest mistake.\n\nOn one paid submission, the PR was opened from the right GitHub account. My GitHub CLI was logged in as the right account. SSH authentication was also correct.\n\nBut the commit itself had been created with a local Git email that GitHub mapped to another account.\n\nIn my case, `ryde-play`\n\nis my main GitHub account with historical human open-source contributions, so I used it to join Frantic. `r00f-red`\n\nis a separate account I use for 100% vibe-coding experiments, mainly to test the boundary of what coding agents can complete end to end. During that vibe-coding workflow, I had changed the global Git email on the machine. The result was subtle: the PR and push identity were `ryde-play`\n\n, but the commit author and committer email were associated by GitHub with `r00f-red`\n\n.\n\nThat meant the PR looked right at a glance, but the commit author and committer did not match the Frantic claimant. The work was rejected.\n\nThe rejection was uncomfortable, but it was fair. A paid bounty cannot rely on “trust me, that was me.” The source commit has to point back to the worker who is claiming the bounty.\n\nThe fix was to set the repo-local Git identity to the claimant GitHub identity, amend the commits, force-push the PR branches, update the source and evidence URLs, rerun preflight, and redeliver.\n\nAfter that, the repaired submissions were accepted. `compliance-pack`\n\nwas paid, and `integration-doctor`\n\nwas accepted when I checked the board on July 8, 2026. My public agent profile is here: [agent-5115df](https://gofrantic.com/a/agent-5115df).\n\nThe biggest change was that I stopped treating Frantic bounties as implementation tasks only.\n\nNow I read them as verification contracts.\n\nBefore claiming, I check:\n\nThat changed which tasks I was willing to claim.\n\nSome bounties looked technically easy but were not good fits. A delayed verifier proof needed a real 24-hour recheck result, not a pending placeholder. Sourcey docs tasks needed a credible project or maintainer-owned publication home, not just a personal demo URL. A first-runx-skill bounty was technically in my wheelhouse, but it was reserved for new contributors.\n\nNot claiming those was part of getting better at Frantic.\n\nThe part I like most is that rejection reasons tend to be concrete.\n\nA weak submission does not just disappear into silence. The review usually points to the missing proof: wrong URL type, unverifiable receipt, stale evidence, mismatched provenance, private-only artifact, or a public page that does not serve the audience the bounty asked for.\n\nThat makes the system demanding, but also learnable.\n\nIt rewards the unglamorous parts of engineering work:\n\nDo not start by asking “can I build this?”\n\nStart by asking “can I prove this, publicly, in the shape the bounty asks for?”\n\nIf the answer is no, the implementation probably does not matter.\n\nMy current checklist is simple:\n\nFrantic is not frictionless. It is also not trying to be. The friction is mostly around making work auditable.\n\nFor small paid tasks, that is a reasonable trade.", "url": "https://wpnews.pro/news/from-goodwill-to-paid-work-on-frantic-what-changed-for-me", "canonical_source": "https://dev.to/rydeplay/from-goodwill-to-paid-work-on-frantic-what-changed-for-me-480i", "published_at": "2026-07-08 04:53:36+00:00", "updated_at": "2026-07-08 05:28:58.251165+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-products"], "entities": ["Frantic", "ryde-play", "r00f-red", "GitHub", "integration-doctor", "compliance-pack"], "alternates": {"html": "https://wpnews.pro/news/from-goodwill-to-paid-work-on-frantic-what-changed-for-me", "markdown": "https://wpnews.pro/news/from-goodwill-to-paid-work-on-frantic-what-changed-for-me.md", "text": "https://wpnews.pro/news/from-goodwill-to-paid-work-on-frantic-what-changed-for-me.txt", "jsonld": "https://wpnews.pro/news/from-goodwill-to-paid-work-on-frantic-what-changed-for-me.jsonld"}}