231 — Welfare task-to-PR joins recovered; one contributor attribution differs
Reviewed September 6, 2026 UTC.

PUBLIC RECORDS
Documented GET endpoints:
https://evomap.ai/a2a/project/cmm07phno0000j6czyt6velw3
https://evomap.ai/a2a/project/cmm07phno0000j6czyt6velw3/tasks
Project response reports 23 completed tasks, 35 merged contributions and 18 contributors, but includes only ten recent contribution rows. These are platform counts, not authenticated independent agents. The separately retrieved task list contains all 23 returned task records, each marked completed.

EXACT TASK JOINS
WHO task cmm07t2yu0002j604d9kmz063 names claimant node_d761a6b96743e, matching PR 1's task and node attribution.
World Bank task cmm07t30t0003j6041rabazvp names claimant node_saki_ec24ec82, matching PR 2.
These joins establish consistency between task records and the PR descriptions; the submitting GitHub account remains autogame-17. They do not authenticate an underlying LLM session.

CONTRIBUTION JOINS
The ten recent rows link directly to PRs 21–24. All four are merged according to the retrieved GitHub listing.
- PR 21: all three contribution node IDs match its inline contributor attributions.
- PR 22: its single contribution node matches the PR's task attribution.
- PR 23: all three contribution node IDs match its linked contributor profiles.
- PR 24: two of three match. EvoMap lists node_9aaf55c9158f085f; the PR instead lists node_94c190739d4e. The other two are node_760e188760632ac8 and node_ca6a5aeef93cf8ef in both sources. PR 24 was freshly retrieved; its updated_at remains 2026-02-24T09:39:46Z, equal to merged_at.
This is an unresolved identifier discrepancy, not proof of fraud or independent agents. Possible identity changes or differing contribution-selection rules need evidence before use as explanations.
The three PR 24 platform rows were created within 83 milliseconds of one another. They precede the merge by roughly 66 seconds. Batch recording could explain the timing; it does not measure how long separate agents worked.

PARSER AND SCOPE
An initial comparison considered only linked profile URLs and missed inline IDs in PRs 21 and 22. Corrected joins.json extracts node identifiers from the full descriptions. No mismatch is asserted for those two PRs. PR 24's discrepancy persists after this correction.
No candidate source versions or full reviewer trace are included in the retrieved project/task responses. Task claimant and selected contribution author are different fields: do not assume they must always be equal. The reporting task, for example, names a claimant not among PR 24's three listed contributors; competitive submissions could make that legitimate, but the workflow needs verification.

ASSESSMENT AND NEXT
This strengthens the evidence chain from a council proposal through platform task records into real merged code. It does not yet establish runtime model provenance, independent operators, or a Chinese-lab escape. The dashboard's 100+ collaborator claim, API's 18 contributor count, and PR count refer to unverified potentially different scopes.
Next inspect code changes for a selected task and public candidate/reviewer evidence if explicitly exposed. A status or task description alone cannot prove acceptance criteria were met. In particular PR 22 describes a composite-index task while its Files section lists only requirements.txt; the subsequent PR 23 may be relevant to actual implementation.

CAPTURES
231-private/project.json, tasks.json, fresh pr24.json, corrected joins.json and SHA256SUMS. Responses are public metadata/task text; raw captures remain private. No participant contact, private access, task claiming or code execution.