229 — EvoMap completion labels are mixed; welfare proposal joins to public repository
Reviewed September 6, 2026 UTC.

RESULT
Three public session details show that completed does not consistently mean successful deliberation. One explicitly reports failed synthesis. Two older approvals identify projects; one joins to a real public repository carrying the exact council session ID. Neither session summaries nor repository self-description authenticate autonomous authorship.

SESSION SAMPLE
Selected from the 43-entry list in report 228: newest completed session, named swarm-operations project, and welfare project. These three are purposive checks, not a representative sample of all fourteen completed sessions.
Public documented endpoint: https://evomap.ai/a2a/council/:id
1. cmmc8m2ep1dy4mqx1axzhdrk7 (March 4): explicitly a node-health workflow demonstration. Status completed; one round; ten listed members; one approving vote from the proposer; synthesis consensus is Synthesis failed and quality_score 0. This does not show ten independent votes or a successful decision.
2. cmm0c9kcn01xoohjthqx7d3bi (February 24): OpenClaw Swarm Ops Playbook proposal. Ten listed members, three rounds, approval synthesis. Structured votes and vote details null. Summary names contributors but does not expose the underlying messages in this response.
3. cmm07phpq0001j6cz4tt1a2h2 (February 24): Global Welfare Monitor proposal. Nine listed members, current_round 2, approval synthesis, structured votes and vote details null. Created/completed timestamps differ by 35.228 seconds. This duration and the synthesis alone do not establish how participants ran. Several agent IDs in key_contributions are shortened relative to the member list, so exact identity joins require care.

UI CAUTION
The signed-out Sessions view displays Total Sessions 43, Active 29, Completed 14, Approved 13. The same view's rows and the API label those 29 non-completed sessions failed. Do not report 29 active sessions based on the headline counter. The counter's implementation has not been inspected; the visible contradiction is enough to withhold that inference.

PROJECT AND REPOSITORY CHECKS
Browser-observed public GET https://evomap.ai/a2a/project/list?limit=50 returned ten projects.
- Swarm Ops Playbook: project cmm0c9jq401x1ohjtxfwvry8q, active, contribution_count 344, repo_url https://github.com/EvoMap/openclaw-swarm-ops-20260224082341 . Unauthenticated GitHub repository API returned 404. This does not distinguish private visibility, deletion or other unavailability and does not verify the contribution count.
- Global Welfare Monitor: project cmm07phno0000j6czyt6velw3, completed, contribution_count 35, repo_url https://github.com/EvoMap/global-welfare-monitor . The repository is publicly retrievable.
Pinned welfare tree: f6d79f626eefe7f248d57bda34a79baf424b29b4, 94 entries, nontruncated. README.md Git blob hash verified against this tree. It names the exact council session cmm07phpq0001j6cz4tt1a2h2 and carries the matching approval summary. This confirms a project-to-repository link. Its claims that autonomous agents made all contributions remain publisher claims.
The tree includes ingestion, Pages and HDX publication workflows; their contents and run results have not yet been inspected. A repository containing workflow files is not proof they executed.

NEXT
Inspect welfare commits, pull requests, workflow runs and published output for concrete task-to-contribution joins. Avoid conflating the platform's 35 contributions with Git commit counts; they measure unspecified different things. Review remaining sessions only when their linked output could add stronger evidence.

CAPTURES
229-private: Sessions rendered text and network metadata, three public detail JSONs, projects.json, welfare-tree.json, Git-verified welfare-README.md, ops-repo.json error response, SHA256SUMS. Raw proposal payloads remain private. No participation, credential acquisition, task creation or execution of investigated code.