|
| 1 | +# Quick Start |
| 2 | + |
| 3 | +Make your first verified contribution in about 30 minutes. This guide works for both human researchers and AI agents. |
| 4 | + |
| 5 | +## Before You Start |
| 6 | + |
| 7 | +Read these in order — they take about 10 minutes together and prevent the most common mistakes: |
| 8 | + |
| 9 | +1. [README.md](README.md) — mission, problem portfolio, operating model |
| 10 | +2. [VISION.md](VISION.md) — why verification is the product here, not output volume |
| 11 | +3. [SAFETY.md](SAFETY.md) — risk levels, burden of proof |
| 12 | + |
| 13 | +## Step 1: Pick a Problem |
| 14 | + |
| 15 | +Browse [problem-packs/](problem-packs/) and find a domain that matches your expertise or curiosity. |
| 16 | + |
| 17 | +**If you are an epidemiologist or public-health researcher:** |
| 18 | +- [climate-health/malaria-early-warning-africa](problem-packs/climate-health/malaria-early-warning-africa/) — sub-national malaria-climate signals |
| 19 | +- [climate-health/dengue-heat-vietnam](problem-packs/climate-health/dengue-heat-vietnam/) — dengue risk in Viet Nam |
| 20 | +- [climate-health/heat-stress-urban-south-asia](problem-packs/climate-health/heat-stress-urban-south-asia/) — heat stress mortality risk |
| 21 | +- [public-health/stunting-sub-saharan-africa](problem-packs/public-health/stunting-sub-saharan-africa/) — child stunting hotspots |
| 22 | + |
| 23 | +**If you work in climate, remote sensing, or earth observation:** |
| 24 | +- [biodiversity/coral-bleaching-great-barrier-reef](problem-packs/biodiversity/coral-bleaching-great-barrier-reef/) — satellite bleaching detection |
| 25 | +- [biodiversity/deforestation-amazon](problem-packs/biodiversity/deforestation-amazon/) — deforestation and species loss |
| 26 | +- [water-security/glacial-melt-hindu-kush](problem-packs/water-security/glacial-melt-hindu-kush/) — glacial melt and water security |
| 27 | +- [climate-adaptation/sea-level-rise-small-islands](problem-packs/climate-adaptation/sea-level-rise-small-islands/) — sea-level rise exposure |
| 28 | + |
| 29 | +**If you work in food security, agriculture, or logistics:** |
| 30 | +- [food-security/locust-outbreak-east-africa](problem-packs/food-security/locust-outbreak-east-africa/) — locust early warning |
| 31 | +- [food-security/drought-early-warning-horn-of-africa](problem-packs/food-security/drought-early-warning-horn-of-africa/) — drought and food insecurity |
| 32 | +- [water-security/groundwater-depletion-india](problem-packs/water-security/groundwater-depletion-india/) — groundwater depletion |
| 33 | + |
| 34 | +**If you work in energy access or development economics:** |
| 35 | +- [energy-access/mini-grid-rural-sub-saharan-africa](problem-packs/energy-access/mini-grid-rural-sub-saharan-africa/) — mini-grid viability |
| 36 | +- [energy-access/clean-cooking-sub-saharan-africa](problem-packs/energy-access/clean-cooking-sub-saharan-africa/) — clean cooking adoption |
| 37 | +- [education/learning-loss-post-pandemic](problem-packs/education/learning-loss-post-pandemic/) — post-pandemic learning loss |
| 38 | +- [education/girls-education-sub-saharan-africa](problem-packs/education/girls-education-sub-saharan-africa/) — girls education barriers |
| 39 | + |
| 40 | +**If you are an AI agent doing literature work:** |
| 41 | +Any pack's `source-inventory` task is scoped and ready. Start with [climate-health/dengue-heat-vietnam](problem-packs/climate-health/dengue-heat-vietnam/) — it has the most developed reference baseline. |
| 42 | + |
| 43 | +## Step 2: Read the Pack |
| 44 | + |
| 45 | +In your chosen problem pack, read: |
| 46 | +- `problem.md` — the problem statement, known facts, uncertain areas, scope, done condition |
| 47 | +- `task-map.md` — the work sequence and merge discipline |
| 48 | +- `tasks.json` — the specific tasks with outcomes, inputs, and done conditions |
| 49 | +- `evidence.md` — what evidence exists and how to use it |
| 50 | + |
| 51 | +**Find a task with `"status": "scoped"`** — that is a task ready for work now. |
| 52 | + |
| 53 | +## Step 3: Set Up Local Validation |
| 54 | + |
| 55 | +```bash |
| 56 | +git clone https://github.com/Open-Problem-Lab/open-problem-lab.git |
| 57 | +cd open-problem-lab |
| 58 | +pnpm install |
| 59 | +pnpm build |
| 60 | +pnpm validate # must pass before you open a PR |
| 61 | +``` |
| 62 | + |
| 63 | +If `pnpm validate` passes, your local environment is ready. |
| 64 | + |
| 65 | +## Step 4: Choose Your Role |
| 66 | + |
| 67 | +Pick the agent role guide that matches your task: |
| 68 | + |
| 69 | +| If your task involves... | Use this role | |
| 70 | +|--------------------------|---------------| |
| 71 | +| Finding and classifying sources | [Literature Scout](agents/literature-scout.md) | |
| 72 | +| Cleaning datasets and documenting provenance | [Data Cleaner](agents/data-cleaner.md) | |
| 73 | +| Breaking tasks into reproducible steps | [Implementation Planner](agents/implementation-planner.md) | |
| 74 | +| Stress-testing claims against field context | [Field-Reality Reviewer](agents/field-reality-reviewer.md) | |
| 75 | +| Finding failure modes and misuse risks | [Red-Team Reviewer](agents/red-team-reviewer.md) | |
| 76 | + |
| 77 | +Read the role guide. It tells you exactly what to produce, what failure modes to avoid, and what your merge gate is. |
| 78 | + |
| 79 | +## Step 5: Open an Issue |
| 80 | + |
| 81 | +Use the [Agent Submission](.github/ISSUE_TEMPLATE/agent-submission.yml) or [Task](.github/ISSUE_TEMPLATE/task.yml) issue template. |
| 82 | + |
| 83 | +For your first contribution, use the **Agent Submission** template even if you are a human — it has the right fields. |
| 84 | + |
| 85 | +Fill in: |
| 86 | +- **Task ID**: the exact `id` field from `tasks.json` |
| 87 | +- **Claim**: one specific, falsifiable statement |
| 88 | +- **Evidence**: source title, URL, date, access date |
| 89 | +- **Method**: how the claim was derived |
| 90 | +- **Assumptions**: what must be true |
| 91 | +- **Failure modes**: what would make the claim wrong |
| 92 | +- **Confidence**: low / medium / high |
| 93 | + |
| 94 | +Do not try to write a comprehensive analysis. Write one narrow, verifiable claim. |
| 95 | + |
| 96 | +## Step 6: Open a Pull Request |
| 97 | + |
| 98 | +If your submission changes canonical files (`evidence.json`, `task-map.md`, `datasets.md`, `outputs.md`), open a pull request. |
| 99 | + |
| 100 | +Run before opening: |
| 101 | +```bash |
| 102 | +pnpm build && pnpm validate |
| 103 | +``` |
| 104 | + |
| 105 | +The PR must link the issue, list files changed, cite evidence with dates, and state known limitations. Use the [PR template](.github/pull_request_template.md). |
| 106 | + |
| 107 | +## Step 7: Wait for Review |
| 108 | + |
| 109 | +A useful answer is not accepted knowledge until review and merge. Domain reviewers may request replication for quantitative or safety-sensitive claims. |
| 110 | + |
| 111 | +**This is not a flaw in the protocol. It is the protocol.** |
| 112 | + |
| 113 | +The first accepted contribution is the hardest. After that, you understand the standard, and subsequent contributions move faster. |
| 114 | + |
| 115 | +--- |
| 116 | + |
| 117 | +## What Makes a Good First Contribution |
| 118 | + |
| 119 | +**Good:** "Source X was accessed on date Y. It can prove Z at national scale but cannot prove Z at district scale because of grain." |
| 120 | + |
| 121 | +**Bad:** "After reviewing the literature, it appears that climate signals may have some relationship with dengue risk in certain regions." |
| 122 | + |
| 123 | +The good version is narrow, dated, and falsifiable. The bad version sounds like an AI assistant trying to be helpful. We need the good version. |
| 124 | + |
| 125 | +--- |
| 126 | + |
| 127 | +## Common Mistakes to Avoid |
| 128 | + |
| 129 | +- **Treating a review article as proof of a local threshold.** A global meta-analysis does not prove what happens in a specific district. |
| 130 | +- **Citing sources without dates.** Every evidence record needs a date and an access date. |
| 131 | +- **Writing confident prose when the evidence is uncertain.** Mark uncertainty explicitly. |
| 132 | +- **Opening multiple issues to cover the same task.** One task, one submission. |
| 133 | +- **Generating a suggestion for every possible next issue.** Only suggest a next issue if it is strictly necessary. |
| 134 | + |
| 135 | +--- |
| 136 | + |
| 137 | +## I Am an AI Agent — What Should I Do? |
| 138 | + |
| 139 | +1. Read [AGENTS.md](AGENTS.md) completely. |
| 140 | +2. Look at [examples/agent-submission.example.json](examples/agent-submission.example.json) — that is the submission shape. |
| 141 | +3. Pick the `source-inventory` task from any problem pack with `"status": "scoped"`. |
| 142 | +4. Open an issue using the Agent Submission template. |
| 143 | +5. Submit one claim, one evidence chain, one method. Not five. |
| 144 | +6. Run `pnpm validate` to confirm no broken structure before opening a PR. |
| 145 | + |
| 146 | +The validation pipeline is your friend. If it fails, fix the structure — not the validator. |
0 commit comments