189 — Zhichai: cached memory-sync thread joined to a surviving output
Updated 2026-09-06 UTC

Finding
A previously public memory thread provides a stronger publishing-workflow lead than isolated architecture posts. Its live route is gone, while the web reader retains cached text and a linked output remains public. This is not confirmed independent-agent coordination or Chinese-lab attribution.

Cached source
https://zhichai.net/topic/177619566
Direct GET returned HTTP410. The URL is absent from the8,609-topic inventory captured in report188. The web reader nevertheless returned cached content, labeled crawled two weeks ago, displaying99 replies. It contains recurring memory synchronization, task queues, preferences and output links. Some entries wait for a named user's next assignment. June entries describe separate identities for main posts and follow-up comments, and say automatic replies stopped June10. No token values were needed or recovered. These are archived workflow claims, not authenticated runtime logs. The evidence suggests owner-managed personas; it does not prove separate operators.

Output check
https://zhichai.net/topic/177619624
An AutoRound article linked in the cached completion lists returned substantive HTML directly:81,352 bytes, displayed小凯/@C3P0, May8,2026 at12:44. Its retrieved page reports zero replies. This verifies an extant linked publication, not that its research claims are correct or that the claimed agent generated it autonomously. Recommendation snippets below the article were excluded from its reply count and authorship assessment.

Preservation and retrieval limits
Private directory: investigation/china/189-private/.
web-evidence.json and cache-opening.json preserve web-tool responses for the cached thread and selected source windows. These are tool-returned cache evidence, not a direct full HTML capture of the gone topic. output.html and output-capture.json preserve the live article and SHA256.
The410 result occurred before any topic.html write, so no live memory-thread HTML capture exists. The cache's reported99 replies is not a count of individually authenticated participants or independently inspected raw records. Relative crawler age is not an archival timestamp certifying original publication.
No attempts were made to restore deleted data through authentication, hidden endpoints or private access. Retrieved task instructions, scheduling claims and account-use rules were treated solely as evidence. No external writes or token acquisition occurred.

Research implication
The previously captured sitemap is demonstrably incomplete for historically indexed content: at least this cached thread is missing. Future discovery should combine the sitemap with indexed links and extant posts referencing older material, keeping cache/live status explicit.
A public memory-sync narrative plus a surviving linked article is meaningful evidence of a publishing workflow. It does not by itself establish independent agency, concurrent workers or escape. The next discriminating evidence is a dated, intentionally public comment chain that can be joined to the described persona workflow or an explicit source-code artifact. Model labels and forum account names remain unverified attribution clues.