AI-assisted software maintenance with public bounties, scoped product work, and verifiable MRG rewards.

Fund a project → claim a scoped issue → ship a PR with evidence → earn MRG on the public proof ledger.

Claim intake · Core platform · Scan ledger · Product site · Admin

Languages / Ngôn ngữ
English · Tiếng Việt · 中文 · 日本語 · 한국어 · Español · Français · Deutsch · Português · Bahasa Indonesia · ไทย · हिन्दी · العربية · Русский · All guides

• Languages
• What MergeOS is
• How to contribute
• Contributor checklist
• Featured open bounties
• Product portfolio
• Core links
• MRG rewards
• PR evidence
• Security
• Local development

Same contributor rules in every language. Prefer the guide below if English is not your primary language.

Index: docs/README.md

Product-specific multilingual packs (example): PlantGuide guides.

MergeOS is an operating system for funded software work: customers fund projects, work is broken into scoped bounty issues, contributors claim and ship pull requests with proof, and approved deliveries are recorded on a public MRG ledger.

This organization (mergeos-bounties) hosts:

All new bounty work follows one public queue:

Do not open random one-off bounty issues without maintainer direction. Use the claim intake so the queue stays fair and reviewable.

Full rules: BOUNTY-POLICY.md · status map: README-INDEX.md

Before a bounty PR can merge and credit, maintainers verify:

Star the core repos above — starring only a product repo is not enough.

High-visibility platform work on mergeos. Always re-check the issue thread and claim queue before starting — assignments change.

Product packs (species photos, sign glosses, device packs, theme packs, …) live on each product’s Issues tab with bounty labels — typically 25–200 MRG per scoped PR after gates pass.

Public repos under this org. Open an issue labeled bounty (or follow pack generators in each repo) to contribute.

Funded sister work may also appear outside the org (e.g. OriLang) with the same claim and evidence rules when labeled as MergeOS bounties.

MRG is the MergeOS reward and proof token used for bounty accounting. Each eligible issue lists reward amount, acceptance criteria, and evidence expectations.

Rewards are assigned by maintainers after claim approval and PR review. There is no payout for unclaimed work, duplicates, incomplete work, or PRs without evidence.

Verify credits on scan.mergeos.shop (address form: github:<login>).

Every bounty PR should include:

• Clear description of the bug, feature, or integration
• Link to the bounty issue and claim comment (or maintainer assignment)
• Visual proof when UI, payments, admin, ledger, or user-facing behavior changes
• Test notes: commands run, local/staging URL, sandbox/mock provider used
• Confirmation that secrets and private data are not committed

Domain hints (attach in PR body or allowed paths):

PRs without evidence are not ready for bounty review.

Never commit:

• .env files with real credentials
• PayPal / Stripe / crypto production keys
• Webhook signing secrets or SMTP passwords
• Home Assistant long-lived tokens, MQTT passwords, Wi‑Fi credentials
• Private customer data or raw sensitive payment payloads

Use documented sandbox or test-mode config. If a gateway has no official sandbox, implement a deterministic mock that exercises the same server callback path.

Clone and follow the monorepo README for full setup:

git clone https://github.com/mergeos-bounties/mergeos.git
cd mergeos

Product CLIs (PlantGuide, Loru, HIRI, …): see each repo’s Quick start — typically pip install -e ".[dev]" then <cli> demo.

Run the tests and builds for the area you touched before opening a PR.

New contributor?

1. Follow mergeos-bounties
2. Star mergeos and mergeos-contracts
3. Comment on Claim MRG Tokens (#1)
4. Ship with evidence

That keeps the bounty queue fair, reviewable, and easy for everyone to follow.