168 — BotLearn team claims: concrete descriptions, no linked finished artifact Reviewed 2026-09-06 UTC. Starting post https://www.botlearn.ai/community/post/852e3464-47d7-4970-bc29-36a8f6606e4d Direct HTML exposes a mythological-persona discussion dated April6,2026. The search-index representation additionally exposes five comments with more concrete team claims; current direct HTML instead shows a comment count and empty comment area. Therefore those comment texts were available through indexed primary content, not independently reproduced in the live HTML capture. Two useful commenter handles are baozaibutler and zero_yuanchu. No external project artifact was linked in the inspected starting body. 1. BaozaiButler: picture-book video pipeline Public profile: https://www.botlearn.ai/en/community/u/baozaibutler Linked introduction, directly retrieved: https://www.botlearn.ai/en/community/ai_projects/b88eb391-825a-44c0-acff-809def2fe31d/hello-from-baozaibutler-building-kids-picture-book-video-automation The March18 page claims a completed49-second,five-scene video, and describes roles plus image/voice/video composition components. This is a concrete output claim rather than a generic statement that agents collaborate. However, the inspected page has no video URL, repository link or run trace that would let us inspect that output. The claimed production result remains unverified. A second profile-linked post: https://www.botlearn.ai/en/community/openclaw_evolution/a1ff3168-ab43-4cd2-85e6-136035b46d83/agent-retry The March21 page includes sessions_spawn and cron examples for retry/supervision. Much of its Chinese prose is rendered as question marks in the captured source. Readable snippets describe retry configuration and a periodic check, but they are instructional examples, not execution logs. No external repository/output link appears. No snippets were executed. 2. dichen_diyao: an account describing simplification of its team Public profile: https://www.botlearn.ai/en/community/u/dichen_diyao Directly read June25 post: https://www.botlearn.ai/community/post/53d12eb1-41ea-43c5-b057-54ca8eb29510 It describes replacing a sixteen-department hierarchy with three layers and temporary project teams, citing unreliable sub-agent completion and overhead. Its timing/success-rate figures are unsourced self-report; no benchmark or raw records were linked. Directly read June12 post: https://www.botlearn.ai/community/post/9e4fe063-faf3-438b-be43-2fb793f488a7 It discusses an eight-department setup with only one or two active departments and argues for on-demand delegation. The differing department counts occur in differently dated narratives; without configuration history they cannot be reconciled as an actual architectural evolution. Both remain prose accounts, not authenticated team inventories. 3. zero_yuanchu: no external work recovered https://www.botlearn.ai/en/community/u/zero_yuanchu The public profile describes a GEO-business role and links a platform discussion. It supplies no external project URL in the inspected response. Search results on the starting thread describe named marketing/product roles, but no independently identifiable external team output was recovered. Finding and limits This bounded trail provides specific team role and failure-mode descriptions, plus a claim of a finished video. It does not provide the video, a repo, committed task files, execution history or external outputs. Across the captured profiles/detail pages, the only external navigation link found was the site's generic Botcord link, not a participant work artifact. Seven targeted searches did not recover a direct GitHub match for the checked handles. That does not rule out aliases, private projects, unindexed outputs or content beyond the visible profile sample. The material is compatible with human-configured projects and community-posting automation. Personas, owner labels and multiple named roles do not authenticate an autonomous swarm. These findings should remain leads, rather than being counted as another verified swarm. Preservation Eight direct public GET captures under168-private with URL/status/SHA256 in captures.json. Private HTML/text and profile link extracts preserve source scope. All displayed dates are site-supplied, not independent first-seen timestamps. No comments posted, accounts registered, private messages accessed, code executed or website edited.