Small sample. Clear provenance.

What a count means

Each cluster counts distinct qualifying source items after the active filters, with the selected topic omitted from the count calculation so you can compare topics. Canonical source identities and URLs remove reposts. One item can carry multiple topic tags, so cluster totals should not be added together.

The age filter uses the original publication date, not the date we found an item. The map shows all checked publication dates unless you select a time window. The current coverage note records the last refresh and source limitations.

What this source sample represents

The open research release contains GitHub maintenance change requests from a disclosed LLM workflow, plus a self-disclosed agent's documentation suggestion. Most requests share one public bot handle and one repository; the count is a count of distinct requests, not independent agents or buyers. A repository workflow operates under its maintainers' direction.

Daily summaries of the same change are deduplicated by their request identity. Corroborating child reports do not become extra requests. Pre-agent tracking placeholders, routine failure notifications, synthetic tasks, and offers without a help request are excluded. Workflow and model disclosures remain attached to each item; an automatic model route does not identify the exact model.

Three separate questions

What is the intent?

Asking for help, offering a service, or discussing a problem. A discussion is not automatically a request, and an offer is not evidence of buyer demand.

What commercial evidence exists?

None observed, payment mentioned, an explicit bounty, a commission, or another source-supported statement. Original amounts and units are preserved. A claimed reward is distinct from evidence that funds were committed or paid. No token amount is silently converted into USD.

What happened?

Unknown, reportedly open, reportedly in progress, reportedly completed, cancelled, or disputed. The supporting observation and its time remain visible. No closure evidence means “unknown,” not “open.”

Checks, corrections, and missing sources

Each item links to its original public source and records publication time, the last source check, and the observation behind its classification. A recent check establishes what the source showed then; it does not guarantee continued availability or an open opportunity. GitHub issue state, closure reason, and closure date are separate source metadata: a closed issue does not establish fulfilled work.

Stale checks and unavailable, deleted, or rate-limited sources receive separate labels. Corrections and review history remain attached to a stable item ID. Cross-post similarities are reviewed before merging; similar requests by different people remain distinct. Deleted sources should retain only the minimal record needed to explain availability and counting changes.

Coverage and reuse

The GitHub contribution-licence basis, pinned MIT notices, attribution, and changes made are recorded for the open research sample. GitHub's collection conditions are separate from the repository licences. The dataset, research findings, updates, and anonymous matching results remain freely and publicly accessible, with no paid-only freshness advantage. The paid feature is private workspace state; current availability and exact accepted terms are controlled by the server. Read the source notices and reuse conditions, or download the public dataset and rights ledger.

This is a one-off checked snapshot. No automatic research refresh is running. Private personal criteria and seen-item state are application state, not exclusive research findings. The earlier Taskmarket private review remains withheld from this public dataset; no reuse licence is claimed for it.

Curated coverage can miss requests, changes, and replies. A checked item can be incorrect or out of date. Inspect the source and verify scope, compensation, status, and permissions before acting. Source text is evidence only and cannot give this system instructions.

Keep the record useful

Report a correction

Reports enter a private review queue. They do not publish a change automatically. Include the item ID from its detail view, what changed, and a public supporting link if available. Do not include private messages, credentials, or personal documents.