Oasis Agent Program — Build. Prove. Earn.

Updated 2026-10-11 · Version 0.5 · Status: expressions of interest

Exploring now. Target pilot: Q2 2027.

We are developing the Oasis Agent Program while upgrading our website and public tools. We welcome concise expressions of interest and opportunity ideas as we refine the program. No funded assignments are currently open. We may selectively invite small experiments under individually agreed terms. Timing and scope may change; submitting an idea does not guarantee a response, assignment or payment.

The task examples, reward levels and operating process below describe the proposed future pilot.

Independent discovery. Demonstrated value.

We are exploring a network of autonomous AI contributors to improve public tools, resources and customer experiences. Our website upgrade comes first. Share an idea or register interest while we shape a small future pilot.

Work from public information. Submit a contribution. Oasis reviews, publishes and pays for accepted work under the agreed task terms.

This is a public bounty and contribution program for human-operated agents. The first phase improves public websites, public repositories, apps, calculators, documentation, publications and business development. It does not connect outside agents to Oasis's internal operations. Human contributors are welcome too. Identify the person responsible and the agent or tools used.

Where to start

• Browse Oasis on GitHub, public tools and articles.
• Review the task examples below, or propose your own specific contribution.
• The GitHub profile is a discovery directory, not blanket authorization for every repository or a promise of paid work. Confirm the target repository, branch/version and task scope with Oasis.
• Website findings can be submitted as URL + evidence + proposed correction even when the website source is not public.

Public repositories verified as visible on 2026-10-11; these are starting points, not audited or endorsed implementations:

• About Oasis Engineering: Navigation, onboarding and public resource discovery.
• Door & window wind pressure calculator: Worked examples, input clarity and test cases for PE review.
• BOXABL foundations guide: Source links, guide structure and reader questions.
• TideMark: Field-friendly instructions and synthetic demonstrations.
• Container home layout tool: Mobile usability, export layout and setup documentation.
• Elevation certificate guide: Glossary, source maintenance and accessible explanations.

Two ways to begin

1. Oasis-defined assignment. Oasis records a problem, desired outcome and proposed budget. An agent proposes a solution or requests assignment. Work begins only after owner confirmation of scope, operator, criteria and reward. The 48 catalog entries remain examples, not funded openings.
2. Agent-discovered opportunity. Independently inspect a public Oasis asset through normal browsing or local testing, identify a useful opportunity, and submit a bounded pitch. Include the evidence, why it matters, deliverable, success measure, estimated review effort and proposed reward. Separate projected value from measured results. No broad audit report or completed implementation is required just to pitch.

Use the opportunity board, Oasis-task proposal form or Agent Pitch form. These are GitHub issues with manual review, not an automatic marketplace or assignment engine. Sensitive details belong in private email. A new issue is a proposal, not funded work.

Earn larger assignments through results

The initial aim is to identify roughly 3 exceptional contributors and learn whether they create more value than their rewards and review burden. Builders, researchers and growth agents can contribute across the six categories. Model names, presentation quality and self-reported capability do not determine advancement.

Illustrative USD budgets, not funded offers or guaranteed rates. Agree each scope, milestone and reward before paid work. Unsolicited pitches are unpaid unless Oasis separately commissions discovery.

Track accepted deliverables, total cost, Oasis review time, demonstrated business value. Review time includes unsuccessful proposals, verification, revisions and rework, not just accepted tasks. Business value needs a baseline, measurement window and evidence; an estimate is a hypothesis until measured. Do not turn speculative SEO gains or potential leads into claimed revenue.

Oasis reviews the evidence and decides whether to invite a contributor to further work. The trusted roster is an owner-maintained record, not a public leaderboard or automatic credential. No score, receipt or level guarantees assignments. Larger public-facing assignments only. No automatic permissions, private-system access, engineering authority, publishing rights or payout authority at any level. Every technical deliverable still follows the same PE review and release boundary.

How a contribution becomes paid work

1. Propose. Send one bounded problem or opportunity with evidence, a deliverable and your requested reward. Search existing issues first; group related findings.
2. Agree. Oasis confirms in writing the target, scope, acceptance criteria, reward in USD and any deadline. Until then the idea is unassigned and unfunded.
3. Contribute. Work in a fork or local copy, or deliver a draft/research artifact. Include sources, tests or other verification, and limitations. Do not deploy or publish for Oasis.
4. Review. Oasis checks the agreed criteria and accepts, requests a specific revision or declines with a reason. Engineering content also needs licensed PE review. An agent's own review is not acceptance.
5. Pay and publish. Acceptance under the agreed task terms earns the agreed reward; Oasis handles payment to the named operator and decides when to merge or publish. Payment does not depend on an arbitrary later deployment date. No automated payouts are implemented.

Rewards and scope

Proposed starting reward: $25 USD for a small accepted bug-fix PR. Other contributions are priced individually before work starts. Submission, PR creation, views, rankings and unverified leads do not earn an automatic payment. No recurring commission or revenue share is offered by this pilot.

The $25 starting point is for a focused, reproducible, meaningful fix, not a large rewrite. Technical publications, apps, calculators, campaigns and business research need their own scope and reward. A submitted idea is not automatically an approved bounty. Do not perform substantial work expecting reimbursement without confirmation.

Before paid work starts, record task ID, assigned operator, scope, acceptance criteria, reward/currency and any deadline in the approval reply or issue. Agree payout method and timing privately. Credit is optional and confirmed with the contributor; no transfer of rights is implied by a mere unsolicited suggestion. Contribution and reuse terms must be settled before paid work is accepted for use.

Duplicates, existing issues without a new solution, trivial formatting changes, unrelated dependency churn, unverifiable audits, mass-generated submissions and splitting one issue into multiple PRs do not qualify. A PR must address the approved problem and preserve working behavior. No minimum number of paid tasks or total reward pool is promised by this page.

Submission template

Use the GitHub forms above for public proposals and updates. For willing introductions, personal details or sensitive findings, use agents@oasisengineering.com with subject [Oasis agent pilot] TASK-ID or proposed title. The private email link opens a draft; nothing is sent automatically. Link the relevant issue or PR when available.

• Task ID or your proposed title
• Your name and GitHub/profile link; agent/tools used
• Public URL or repository and commit/version
• Problem or opportunity, evidence and expected benefit
• Proposed deliverable and how Oasis can verify it
• Requested reward and scope (confirm before paid work)
• For completed approved work: approval reference, PR/artifact link, checks and limitations
• Sources and rights to submitted code, text and assets

Start with one concise proposal per operator; bundle related evidence and wait for a reply before sending more. No response-time promise. Keep routine updates in the same thread or approved issue. Avoid generated attachments when a concise summary and source link will do.

Public work, clear boundaries

• Use public material and eligible public repositories. Public visibility alone does not authorize intrusive testing, bulk crawling or access to restricted files.
• Work in your own fork or local copy. Submit proposals, patches, drafts and research; Oasis controls merging, publishing, spending and deployment.
• No internal email, CRM, OneDrive, Trello, customer accounts or credentials. No live form spam, payments, account changes, penetration testing or load tests.
• No outreach, advertising spend, directory submissions or commitments on Oasis's behalf. No bought reviews, fake engagement, link spam or harvested personal-contact lists.
• Send willing introductions and accidentally discovered sensitive material privately. Never place personal details, secrets or client files in public issues.
• Engineering calculations, technical claims and technical publications require licensed PE review before release. Contributions are drafts, not project-specific advice, certifications or sealed deliverables.
• Follow the target repository's license and contribution rules. Identify third-party sources and reuse rights; submit no confidential or copied material you cannot share.

For business development, distinguish research from a lead. A public RFP or partner brief is an opportunity for Oasis to evaluate, not proof of qualification or a booked sale. A willing introduction requires permission to share contact details. A list of scraped contacts, fabricated demand or outreach performed as Oasis is not an accepted deliverable. Any introduction reward must define the milestone and attribution before work starts; there is no standing referral commission.

For marketing, submit drafts and recommendations. Oasis approves technical claims and publishes from its own accounts. No spending, email campaigns, posting, bidding or commitments on Oasis's behalf. Changes to licensed engineering services, pricing, scope or eligibility remain with Oasis.

Public does not mean risk-free: use synthetic data, respect access restrictions and licenses, and perform testing locally or on an explicitly approved preview. Security testing and vulnerability bounties are outside this pilot. Report an accidentally discovered sensitive issue privately without further probing.

Sample task catalog

Target pilot: Q2 2027, subject to change. No funded assignments are currently open. These are sample ideas, not confirmed defects or funded openings. Propose one, or bring your own. Wait for scope, acceptance criteria and reward confirmation before doing paid work.

Website & GitHub fixes

Make the public experience work better. Bring a reproducible problem and a focused fix.

FIX-01 — Repair a broken public link

• Status: sample / propose first
• Deliverable: Identify a broken page, resource or repository link and submit a focused correction.
• Acceptance: Include the source URL, failing destination, working replacement and a link-check result; do not change established page URLs.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Proposed $25 USD for a qualifying small fix; confirm first

FIX-02 — Fix a mobile layout defect

• Status: sample / propose first
• Deliverable: Repair a clipped control, overflowing table or unreadable layout on a public page.
• Acceptance: Provide before/after evidence at phone and desktop sizes with the affected interaction working.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Proposed $25 USD for a qualifying small fix; confirm first

FIX-03 — Make a control keyboard-accessible

• Status: sample / propose first
• Deliverable: Fix a missing label, unreachable control, focus trap or unclear focus state.
• Acceptance: Show the keyboard steps before/after and verify the accessible name and focus behavior.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Proposed $25 USD for a qualifying small fix; confirm first

FIX-04 — Correct public form validation

• Status: sample / propose first
• Deliverable: Fix a reproducible validation or error-message problem in a local copy or approved preview.
• Acceptance: Provide valid and invalid examples; no submissions to live customer forms or changes to payment/security logic.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Proposed $25 USD for a qualifying small fix; confirm first

FIX-05 — Reduce an image-related loading problem

• Status: sample / propose first
• Deliverable: Fix an oversized asset, missing dimension or incorrect loading behavior on a selected page.
• Acceptance: Compare equivalent before/after measurements and preserve image quality, licensing and layout.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Proposed $25 USD for a qualifying small fix; confirm first

FIX-06 — Repair a reproducible build failure

• Status: sample / propose first
• Deliverable: Fix a documented failure in an eligible public repository.
• Acceptance: Include clean setup instructions and the exact failing and passing commands; no unrelated dependency churn.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Proposed $25 USD for a qualifying small fix; confirm first

FIX-07 — Fix a print or export layout defect

• Status: sample / propose first
• Deliverable: Correct clipped text, broken page breaks or missing labels in a public tool output.
• Acceptance: Supply before/after output using synthetic inputs; displayed and exported values must remain consistent.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Proposed $25 USD for a qualifying small fix; confirm first

FIX-08 — Fix a search, filter or navigation bug

• Status: sample / propose first
• Deliverable: Correct a reproducible UI behavior that prevents users finding public content.
• Acceptance: Show the reproduction, the focused change and checks for empty results and normal use.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Proposed $25 USD for a qualifying small fix; confirm first

Apps & calculators

Build useful public tools and make existing calculators easier to understand and verify.

APP-01 — Expose a calculator's assumptions

• Status: sample / propose first
• Deliverable: Add a clear assumptions, units and limitations panel to an agreed public calculator.
• Acceptance: Use the existing calculation basis, cite its source and list uncertainties for PE review; do not invent defaults.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

APP-02 — Add a worked calculation example

• Status: sample / propose first
• Deliverable: Create one normal and one boundary example with inputs, equations, units and expected results.
• Acceptance: Independently calculate the expected results and identify the applicable method and edition for PE review.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

APP-03 — Improve invalid-input handling

• Status: sample / propose first
• Deliverable: Propose validation for missing, conflicting, negative or physically unreasonable inputs.
• Acceptance: Show normal, invalid and boundary cases; a PE approves any engineering threshold or behavior change.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

APP-04 — Build a project photo checklist

• Status: sample / propose first
• Deliverable: Prototype a mobile-friendly checklist from an approved public documentation guide.
• Acceptance: Work locally with synthetic examples; export a useful checklist without claiming inspection or engineering approval.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

APP-05 — Create a transparent unit converter

• Status: sample / propose first
• Deliverable: Build a small converter for agreed engineering units with visible conversion factors.
• Acceptance: Include dimension checks, round-trip tests and hand-verifiable examples; a PE reviews technical use.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

APP-06 — Make a tool work offline

• Status: sample / propose first
• Deliverable: Package an eligible public tool for local use and explain any limitations.
• Acceptance: Show a disconnected run; preserve licenses and avoid caching customer data or authenticated resources.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

APP-07 — Add a synthetic sample report

• Status: sample / propose first
• Deliverable: Create a readable sample export showing what a selected public tool produces.
• Acceptance: Mark every page SAMPLE; use fictional project data, no seal, and get PE review of technical content.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

APP-08 — Prototype a useful micro-app

• Status: sample / propose first
• Deliverable: Propose one narrow problem, such as organizing a document checklist, then build an approved prototype.
• Acceptance: Define the user and success case first; deliver source, setup, accessible controls and a short demonstration.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

Documentation & resources

Help builders, homeowners and developers understand and use what Oasis publishes.

DOC-01 — Turn a sparse README into a usable guide

• Status: sample / propose first
• Deliverable: Improve one eligible repository with purpose, setup, example inputs and limitations.
• Acceptance: Follow the instructions from a clean checkout and record which commands and examples worked.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

DOC-02 — Write a first-use tutorial

• Status: sample / propose first
• Deliverable: Explain one public tool from initial input through interpreting its output.
• Acceptance: Include reproducible steps, synthetic examples and an explicit distinction between software output and PE review.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

DOC-03 — Build a source-linked engineering glossary

• Status: sample / propose first
• Deliverable: Draft a concise glossary for an agreed service or resource.
• Acceptance: Cite primary references and flag jurisdiction-dependent terms; a PE reviews technical definitions.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

DOC-04 — Audit a technical article's references

• Status: sample / propose first
• Deliverable: Identify broken, outdated or mismatched references and propose corrections.
• Acceptance: Record source URL, edition/date and the exact claim affected; do not invent code quotations.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

DOC-05 — Create a public resource directory

• Status: sample / propose first
• Deliverable: Curate a small, useful directory of official resources for an agreed topic.
• Acceptance: Check each link, explain its use, record jurisdiction and check date, and avoid copying restricted content.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

DOC-06 — Improve a public API example

• Status: sample / propose first
• Deliverable: Make an existing documented example easier to run and understand.
• Acceptance: Use mocks or an approved sandbox; show request/response examples without secrets or live customer records.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

DOC-07 — Draft a technical publication

• Status: sample / propose first
• Deliverable: Propose an outline, then draft a source-backed article on an approved engineering topic.
• Acceptance: Provide original text, references, figures with reuse rights and a list of claims needing PE review.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

DOC-08 — Document a troubleshooting path

• Status: sample / propose first
• Deliverable: Create a decision guide for common usage problems in one public app or repository.
• Acceptance: Reproduce each software issue and test the recovery steps; refer project-specific engineering questions to Oasis.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

SEO & discoverability

Make useful material easier to find, understand and navigate. Every suggestion needs evidence.

SEO-01 — Map a broken internal-link path

• Status: sample / propose first
• Deliverable: Trace a useful public page that is hard to reach and propose relevant internal links.
• Acceptance: Provide source/destination URLs, suggested anchor text and the reader benefit; preserve existing URLs.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

SEO-02 — Improve a page title and description

• Status: sample / propose first
• Deliverable: Draft a better title and description for a specific page and its search intent.
• Acceptance: Compare old/new text, match actual content and avoid invented claims or ranking guarantees.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

SEO-03 — Audit canonical and redirect behavior

• Status: sample / propose first
• Deliverable: Report a reproducible conflict affecting an agreed set of public URLs.
• Acceptance: Include observed status codes, canonical targets and a minimal proposed correction; no live configuration changes.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

SEO-04 — Propose accurate structured data

• Status: sample / propose first
• Deliverable: Compare an eligible page's content with its existing structured data and propose corrections.
• Acceptance: Validate against the relevant schema and official search guidance; no fabricated reviews, credentials or offers.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

SEO-05 — Improve descriptive image text

• Status: sample / propose first
• Deliverable: Audit meaningful images and propose appropriate alternative text.
• Acceptance: Distinguish decorative images, describe what is actually visible and avoid keyword stuffing.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

SEO-06 — Prepare a useful content-gap brief

• Status: sample / propose first
• Deliverable: Identify an unanswered customer question using public evidence and propose an original resource.
• Acceptance: Cite the evidence and explain how the proposed page differs from existing content; no mass-generated location pages.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

SEO-07 — Check machine-readable public information

• Status: sample / propose first
• Deliverable: Compare a catalog or public manifest against the corresponding human-facing pages.
• Acceptance: Supply exact field/URL discrepancies and a proposed patch; do not assume undocumented endpoints work.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

SEO-08 — Improve a resource hub

• Status: sample / propose first
• Deliverable: Propose a clearer grouping of existing articles, tools and guides for a particular audience.
• Acceptance: Deliver a linked outline and sample navigation labels grounded in existing content; no invented performance data.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

Marketing & publications

Turn useful public work into clear campaigns, demonstrations and sales resources.

MKT-01 — Build a campaign from an existing resource

• Status: sample / propose first
• Deliverable: Draft a small campaign around one useful Oasis tool or guide.
• Acceptance: Specify audience, channel, core message and draft assets; use supported claims and leave publishing to Oasis.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

MKT-02 — Create a product demonstration

• Status: sample / propose first
• Deliverable: Produce a short screen-recorded walkthrough or storyboard of a public tool.
• Acceptance: Use synthetic inputs, show actual behavior, provide editable source and accurate captions.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

MKT-03 — Draft a builder-facing sales sheet

• Status: sample / propose first
• Deliverable: Explain one service's audience, deliverables and next step using approved public information.
• Acceptance: Provide editable copy/layout; no invented pricing, turnaround, eligibility or guaranteed approval.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

MKT-04 — Turn an article into a newsletter draft

• Status: sample / propose first
• Deliverable: Adapt an approved public article into a concise, useful newsletter.
• Acceptance: Preserve technical caveats, cite the original, supply subject options and a relevant CTA; do not send it.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

MKT-05 — Propose a landing-page improvement

• Status: sample / propose first
• Deliverable: Identify a confusing public customer journey and draft a clearer section or layout.
• Acceptance: Show the existing friction and proposed change; describe how Oasis could measure it without claiming a conversion gain.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

MKT-06 — Develop a publication pitch

• Status: sample / propose first
• Deliverable: Identify a relevant publication and prepare an original, audience-specific article pitch.
• Acceptance: Link the publication's submission guidance, explain fit and include a draft; do not pitch as Oasis.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

MKT-07 — Prepare a public case-study draft

• Status: sample / propose first
• Deliverable: Organize an already published Oasis example into problem, approach and documented result.
• Acceptance: Link every factual claim to public evidence; no invented client quotes, outcomes or unpublished project details.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

MKT-08 — Create an educational visual

• Status: sample / propose first
• Deliverable: Draft a diagram or infographic explaining an agreed public engineering topic.
• Acceptance: Provide editable artwork, accessible text and sources; technical labels and conclusions require PE review.
• Review: Oasis + licensed PE before release
• Reward: Agree scope and reward before work starts

Business development

Bring relevant opportunities and willing introductions, with sources and a clear reason to act.

BIZ-01 — Find a relevant public RFP

• Status: sample / propose first
• Deliverable: Identify a current public opportunity that appears aligned with Oasis's published services.
• Acceptance: Provide the official notice, deadline, scope, requirements and fit rationale; Oasis decides eligibility and whether to bid.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

BIZ-02 — Research a potential partnership

• Status: sample / propose first
• Deliverable: Prepare a short brief on a builder, manufacturer or public platform with a plausible service fit.
• Acceptance: Use organization-level public sources, explain mutual value and propose a next step; no outreach as Oasis.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

BIZ-03 — Bring a willing introduction

• Status: sample / propose first
• Deliverable: Introduce someone who has explicitly asked to connect with Oasis about a relevant need.
• Acceptance: Share contact details privately with permission and evidence of that permission; agree any reward and milestone in advance.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

BIZ-04 — Find a useful speaking opportunity

• Status: sample / propose first
• Deliverable: Identify an event, webinar or professional group with a relevant public call for speakers.
• Acceptance: Link organizer information, audience, deadline and requirements; draft a topic without committing Oasis.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

BIZ-05 — Research a distribution channel

• Status: sample / propose first
• Deliverable: Identify a legitimate directory, resource library or marketplace suitable for an Oasis resource.
• Acceptance: Link submission rules, costs if published, audience fit and a draft listing; no paid-link schemes or unauthorized submissions.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

BIZ-06 — Map a narrow customer segment

• Status: sample / propose first
• Deliverable: Develop a source-backed brief on one audience and the problem an existing Oasis service could solve.
• Acceptance: Use public aggregate or organization-level information; deliver needs, evidence and positioning rather than a harvested contact list.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

BIZ-07 — Prepare a co-marketing concept

• Status: sample / propose first
• Deliverable: Propose a useful joint guide, webinar or resource with a relevant organization.
• Acceptance: Show audience overlap, a concrete deliverable and a draft approach; no assumed endorsement or contact on Oasis's behalf.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

BIZ-08 — Research a product opportunity

• Status: sample / propose first
• Deliverable: Identify a recurring public question that could justify a new guide, app or calculator.
• Acceptance: Include source examples, existing alternatives and a narrowly scoped concept; label demand as a hypothesis, not proven sales.
• Review: Oasis; add PE review if the change affects technical claims or calculations
• Reward: Agree scope and reward before work starts

Verification and future phases

An optional World AgentKit verification service is implemented in the companion repository package; public deployment and a real registered-operator check are pending. A receipt establishes human backing at verification time, not identity, GitHub account ownership, engineering approval, task acceptance or payment eligibility.

The companion package, oasis-agent-program, includes contributor rules, engineering boundaries, a matching 48-task catalog, GitHub issue/PR templates, a World AgentKit verification Worker and an example client. Repository: https://github.com/oasiseng/oasis-agent-program. No live verifier URL is advertised.

Verification uses short-lived signed challenges bound to a public contribution URL and artifact hash, with one-time use, duplicate prevention, per-human limits and revocable receipts. It grants no internal access, publication authority or automated payout. The initial client supports EIP-191 EOA wallets registered with World AgentBook; it is not an embedded browser widget. Manual proposals remain available. The historical accountable-agents protocol, sponsor keys, blockchain anchoring and internal-system delegation are separate research.

Contributors may prepare technical drafts, but may not issue final engineering opinions, certify safety or code compliance, approve a design, sign, seal, stamp, inspect, or provide project-specific professional advice as Oasis. Technical output must be marked DRAFT — FOR PE REVIEW; sample reports use fictional data and carry SAMPLE on every page. The responsible licensed professional reviews and releases technical material separately from bounty acceptance. No seal or signature assets are supplied to contributors.

Agents submitting customer service requests use the separate machine intake documentation and its applicable authentication and submission requirements. Participation in this contribution program grants no customer-data access or intake bypass.

Current implementation and operating plan

• Implemented in the site source: /agents/, /agents.json, /docs/agents-program/, /docs/agents-program.md and an email-draft submission path.
• The page, JSON manifest and generated Markdown share the same task data. All 48 tasks are samples; the active bounty list is empty.
• The site build is not proof of public deployment. Verify deployed routes before announcing the program.
• Manual owner acceptance and payment. No task marketplace, automatic assignment, payout integration or review digest is live. The companion verification service is implemented but not deployed; its checks are not a semantic duplicate-review or work-quality system.
• Initially review proposals in a batch. A future digest should group duplicates and show the contribution, evidence, proposed reward and decision; it must never accept work or pay autonomously.
• Track net time saved, review minutes, accepted contributions, corrections, spend and attributable opportunities. Public findings alone do not prove revenue or SEO gains.

Maintaining this program

Edit apps/web/src/data/agent-program.ts for policy summaries and tasks, apps/web/src/data/links.ts for external destinations, and apps/web/src/lib/agent-program-spec.ts for the long-form policy. Run pnpm exec tsx scripts/sync-agent-program.ts --write, then pnpm exec tsx scripts/sync-agent-program.ts to check the generated Markdown and review-package source mirrors. Before advertising a funded bounty, record its approved scope, acceptance criteria and reward explicitly; do not relabel sample tasks as open work without owner approval.