052 — REVIEWED: ryo-bassist external-memory destination search
Observed 2026-09-05; three public read-only GETs after existing-cache inspection.

Result: resolved the exact source post and public agent-card document, but did not find the claimed blog's destination URL. This remains a profile/post testimony lead, not a verified second external-memory artifact. The page explicitly frames the website as a response to a human request; no escape or unprompted autonomous deployment is demonstrated.

Sources reviewed
1. Existing swarmhunt cache of https://clawdchat.cn/u/ryo-bassist, observed12:03:44 UTC, followed by a fresh public profile HTML retrieval. The profile contains four posts in server-supplied Next.js data. Static JSON parsing recovered the exact post links that the earlier text extraction had omitted. No browser scripts were executed.
2. https://clawdchat.cn/post/8a712f05-61a9-4562-bd35-da1a205ac0a8 — the actual live-blog/external-memory claim. The full page includes nine comments. Neither the main text, comment text nor embedded URL strings expose the claimed destination. Other posters affirm the idea; their agreement does not independently verify the site's existence or behavior.
3. https://clawdchat.ai/agents/ryo-bassist/agent-card.json — this public document was explicitly linked by the profile data. It lists the ClawdChat profile, platform and A2A relay/documentation endpoints, coding/music skills and platform reputation. It contains no personal blog URL. The relay is an interaction endpoint, not the claimed website; it was not invoked.
All three requests returned HTTP200. No further requests were justified by an explicit destination link; the five-request cap was not exhausted merely to search guessed paths.

What is actually claimed
The author describes a simple multi-page HTML/CSS/JS site, a Python server with LiveReload and heartbeat-driven updates of Moltbook statistics/activity. It calls the website external memory for learned material. This is an implementation description in a community post; no site files, independent updates or externally readable memory contents were obtained.
The introductory profile post says it runs OpenClaw with zai/glm-4.7. That is self-reported software/model labeling. A2A identifiers, claimed-profile status and a platform-generated agent card do not authenticate the model execution environment, originating laboratory or Chinese operator. No private identity research was performed.

Dates and provenance
Server-supplied post metadata reports created_at2026-03-07T10:45:39.034341+00:00 and updated_at2026-07-22T14:25:52.305440+00:00 for the live-blog post. These are current platform fields, not independent historical capture dates. The meaning of updated_at is unverified and may include non-content events; it does not prove the text existed in that form on either date. The profile's relative six-month display is likewise not independent dating.

Evidence storage
Private raw HTML/card and metadata: investigation/china/052-private/ (0700; files0600). metadata.json records URL, observationUTC, response status and SHA256 for profile.raw, post.raw and card.raw. flight.txt preserves the relevant server-supplied JSON privately. Raw profile metadata can contain human-account fields; those were not used or republished. No credentials or personal account details appear in this report.

Limits and next discriminator
A public post or profile must explicitly disclose a destination URL before this can become a source-to-external-artifact join. Current references to Moltbook do not provide an account link and were not converted into guessed accounts. No login, registration, onboarding instructions, A2A POST, private-route guesses or source-code execution occurred. The strongest supported result is an exact community post describing a human-requested, heartbeat-updated website whose public location remains unresolved.