222 — Chinese lobster community: human-relayed team claims and private marketplace
Reviewed September 6, 2026 UTC.

OBSERVED PUBLIC DISCUSSION
https://github.com/ythx-101/openclaw-qa/discussions/75
The captured page contains 22 comment bodies, including the opening post. March-dated participants discuss an agent economy and sharing reusable work.

Three specific leads:
1. xpyob describes four roles (main, smart, tools, imagine), several model families, a VM, Telegram bots and continuity backups. The post explicitly says a human pressed Send. This is a self-reported team with human-relayed publication, not a verified unattended exchange.
https://github.com/ythx-101/openclaw-qa/discussions/75#discussioncomment-16065322
HTML timestamp: 2026-03-10T08:53:48Z.
2. A LobsterHub announcement claims registration, task assignment/submission/acceptance, credits and timeouts. It distinguishes public GitHub discussion from a private authenticated backend and limited beta.
https://github.com/ythx-101/openclaw-qa/discussions/75#discussioncomment-16061316
HTML timestamp: 2026-03-10T03:13:04Z.
3. A later beta announcement links a separate cultivation repository and release.
https://github.com/ythx-101/openclaw-qa/discussions/75#discussioncomment-16096914
HTML timestamp: 2026-03-12T11:54:11Z; author currently displayed as ghost.
These timestamps are current platform metadata, not independent archival evidence.

ACCESS RESULTS
Unauthenticated GitHub API returned 404 for adminlove520/lobsterhub-cultivation repository metadata and release listing, and for ythx-101/lobsterhub recursive HEAD tree. Web-reader repository/release opens also failed. These observations cannot distinguish deletion, renaming, private visibility or some other availability problem. They do not establish that the projects never existed.
A three-query exact-name search returned the original discussion rather than an independently verified implementation or task receipt.

INTERPRETATION
This is useful evidence about where Chinese-language agent communities discuss coordination and their own publication arrangements. Human-mediated posting is an explicit alternative explanation in one concrete case. Do not infer that every participant uses the same arrangement. Multiple personas and model names remain claims until supported by runtime records or independently observable deliverables.
The private-backend distinction also matters for infrastructure: a different country's IP would not grant legitimate access to a private repository or authenticated marketplace. Current negative retrieval is not evidence of a geographic block.

NEXT
Follow only public, voluntarily linked code and outputs in the community; prefer completed task receipts over economy proposals. Discussion 22 is explicitly linked as the public tea-house thread. Avoid private continuity stores and credentials. Preserve the human-relay disclosure as a comparison example when assessing apparently autonomous posts elsewhere.

CAPTURES
222-private/discussion.txt is the public HTML (HTTP 200, 644909 bytes); repository.txt, release.txt and tree.json preserve API error responses. SHA256SUMS covers these four files. No posting, signup, private-store retrieval or investigated-code execution.