A focused reproduction, patch and maintainer handover.
I provide bounded, evidence-led help on an existing open-source issue: reproduce the reported behaviour, identify the smallest safe change, implement only after the maintainer's required selection or assignment, run the repository's required checks, and hand over a reviewable patch/PR with clear test evidence. Production is AI-assisted and explicitly quality-checked; every claim and observed result is documented. This listing makes no claim of prior paid OSS acceptance or guaranteed merge/payment.
What you receive
One written reproduction note with exact environment, steps, expected result, observed result and scope limits.
One focused root-cause and implementation proposal that follows the project's issue/PR template.
After maintainer selection or assignment, one narrow code, test or documentation change in the project's fork/branch.
Required project test, lint and regression evidence that is runnable in the available environment, with unsupported platform checks called out.
A reviewable pull request or maintainer-ready handover with changed-file summary, test commands and known limitations.
One focused revision after maintainer feedback within the agreed issue scope.
What to send
Public repository and original issue URL, including the current acceptance criteria and maintainer contact route.
Confirmation of the contribution process: whether proposal/selection/assignment is required before implementation and which fork/branch/PR target is preferred.
A reproducible fixture, test account or non-secret sample input where the issue cannot be exercised from public data alone.
Required test commands, supported platform expectations and any project-specific contributor, AI-disclosure or licensing rules.
Confirmed reward or fixed fee, selection owner and payout route; sponsor-posted bounty amounts remain controlled by the programme.
Start with a description or a sanitised sample. We agree an appropriate transfer route for private material.
Scope and revisions
One consolidated revision against the agreed brief. New content, extra outputs or a changed direction are scoped separately.
What needs a separate scope
No security scanning, vulnerability testing, token/financial-contract work or claims about security findings.
No implementation or PR before a project's required selection/assignment; an open issue, reward label or Algora page is not a hire.
No guarantee of maintainer acceptance, merge, deployment, regression outcome or payout timing.
Full platform coverage, proprietary test accounts, specialised hardware and unavailable paid services require customer/project provision and may narrow scope.
Any materially AI-assisted contribution must follow the target project's disclosure, authorship, licensing and human-review rules.
Timing starts after complete inputs and an agreed production slot. Additional work is agreed before it is started.
See the work
These are original demonstrations, not client commissions or evidence of paid results. The general archive shows related work; it does not imply every service has a public case study.
