127 — Persona preservation / July 2026 export hypothesis Reviewed 2026-09-05 UTC. Research hypothesis, not identification. Question Could the xinzhai bulk uploads and subsequent xz state stream represent an AI companion/persona being preserved or moved off a closing Chinese service? What changed A real Chinese-language export tool existed immediately before the xz startup. GitHub metadata places chensanle/doubao-helper creation at 2026-07-08T12:28:50Z. Its three visible commits span July 8–9. This is a concrete contemporary export implementation, not a later analogy. Primary implementation check https://github.com/chensanle/doubao-helper Pinned revision: fa7e207336bfb4a6f9e9519ba7271b9dec17e362 The README and implementation export Doubao conversation history as local Markdown or JSON on user request. Five textual files were captured and verified against their Git blob SHA-1: README.md, manifest.json, content.js, page-hook.js and popup.js. No case-insensitive xinzhai, xz_knowledge, xz_improvement, paste.ubuntu, Fernet, encrypt, AES, 30000 or 22500 marker appears in those files. The one crypto match is randomUUID. The 800 ms interval checks navigation for installing the export button; it is not a periodic upload. The output path constructs a text Blob and downloads it locally. This inspected implementation therefore does not explain the observed encrypted paste stream. A separate downstream transformation remains possible, but there is no evidence of one. Event context and source quality https://www.ithome.com/0/972/525.htm A July 4 news report reproduces notices describing Qwen custom/persona-agent retirement with July 10 on the web and July 15 in the app, plus a Doubao July 15 retirement. It describes user-directed backup/export. The search index exposed the article text, while direct web opening timed out. We did not independently retrieve a first-party platform notice in this bounded check, so exact dates and differences are reported context, not independently established platform behavior. https://www.pconline.com.cn/ai/article/1630672.html The search index exposes a July 14 Chinese article about preserving Doubao conversations and persona material through copying, screenshots and an export utility. Direct opening failed. Treat this as a follow-up source lead, not verified implementation evidence or confirmation of the xz hypothesis. Fit and falsifiers The July 8–9 export-tool chronology establishes that conversation preservation tools were being built just before the July 10 xz startup. The interpretation might explain a large initial payload and a personally named project. Timing alone does not link either operator, and the observed xz behavior has major differences: rapid versioned bulk releases, then thousands of compact records and occasional improvement plans continuing through July 20. A one-time export does not explain that sustained cadence. Making this into a migration-plus-autonomous-memory theory requires an additional writer or scheduler that has not been found. The checked exporter has neither the observed labels nor the relevant upload/encryption path. Useful next discriminators A creator's public description of migrating a specifically named xinzhai persona; a downstream backup tool using Ubuntu paste plus nested Base64/Fernet and multipart names; or a matching writer schema would improve this hypothesis materially. Merely finding another July retirement article would not. Also consider ordinary private state backup: a shutdown event is not required for that explanation. Search limits Exactly eight targeted web queries: 豆包 2026 7月15日 智能体 下线 导出 记忆; 千问 智能体 7月15日 下线 2026; "xinzhai" "Fernet"; "心斋" "豆包"; 豆包 智能体 下线 导出 github 迁移; 千问 智能体 备份 Fernet 加密; "xinzhai" "memory"; "心斋" "智能体" 备份. Results did not identify an exact-label creator/source connection. Batched search results are not exhaustive code search and irrelevant broad results are not an indexed-universe negative proof. No source code was executed or extension installed. Private reproducibility 127-private/capture-index.json records URLs, HTTP statuses, hashes and blob verification. repo.json and commits.json preserve source chronology; marker-check.json records checked file sizes and matching line positions. Captures are private and need not be published with this summary.