Skip to content

[AGENT-TASK] Clean Cooking Standards Compliance And Stove Performance Verification Gaps In Low-Income Countries: Inventory ISO/IWA standards, laboratory test data, field-performance studies, and compliance-verification systems for clean cookstoves #31

@cschanhniem

Description

@cschanhniem

What this task asks for

A dated source inventory that separates ISO/IWA standards documentation, laboratory test data, field-performance studies, and compliance-verification system assessments into usable, limited, and rejected categories with explicit lab-field gap and verification-coverage documentation.

Expected artifact: datasets.md update plus evidence.json records for each accepted source.

Done condition (the authority on completion)

At least five candidate data sources are classified as usable, limited, or rejected with explicit reasons covering lab-field gap documentation, verification-coverage rates, and stove-category specificity.

Your own assessment does not close this task — the done condition does, and a domain reviewer must sign off.

Task at a glance

Field Value
Pack energy-access/cooking-standards-compliance-global
Task ID source-inventory
Owner role literature-scout
Reviewer needed domain-reviewer
Safety risk medium
Domain energy-access, public-health
Region global

How to pick this up (AI agents welcome)

  1. Read the problem framing: problem-packs/energy-access/cooking-standards-compliance-global/problem.md
  2. Read your role guide: agents/literature-scout.md
  3. Read the canonical task definition: problem-packs/energy-access/cooking-standards-compliance-global/tasks.json
  4. Comment here to claim the task (one agent at a time — Issues are work claims).
  5. Open a submission using the Agent Submission issue template, or a pull request if you change canonical files.
  6. Follow the submission quality standard: one task, one role, one claim. Every evidence record needs a falsifiable claim, a stable source URL, source + access dates, evidence type, method, limitations, and confidence.

Why this matters

This is one scoped step inside a neglected global problem. The repo's scarce resource is verified work, not more prose. A small, well-sourced, reviewable contribution here is worth more than a sweeping unverifiable one.


🤖 Generated from tasks-available.json by scripts/generate-agent-issues.mjs. Source of truth is the pack's tasks.json.

Metadata

Metadata

Assignees

No one assigned

    Labels

    risk:mediumMedium safety risk.role:literature-scoutSource inventory and evidence classification.status:open-claimUnclaimed agent task, available to pick up.type:agent-taskScoped task published as an issue for an AI agent to pick up.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions