What else looks like xz?

XZ: analogous systems and earlier writing
Reviewed 2026-09-05 UTC

Finding
-------
There are concrete precedents for the components of the xz pattern: persistent
agent memory, reflection records, periodic background jobs, encrypted storage,
and client-encrypted paste publication. No reviewed source connects these
components to xinzhai, the exact xz labels, or the Ubuntu paste sequence.

The best working agent hypothesis is a personal/prototype agent with a scheduled
state or memory writer and a less frequent improvement process. A conventional
script saving fixed state or test messages remains a serious alternative.
The analogues below generate hypotheses; they do not identify the uploader.

Earlier writing with verified pre-July chronology
-----------------------------------------------
1. Reflexion: Language Agents with Verbal Reinforcement Learning.
   First arXiv submission March 20, 2023.
   https://arxiv.org/abs/2303.11366
   Describes verbal reflection on task feedback, retained in episodic memory
   for subsequent attempts, without updating model weights. This is the closest
   conceptual precedent for knowledge plus improvement-plan records. Neither
   encrypted public storage nor our labels are established by the abstract.

2. Generative Agents: Interactive Simulacra of Human Behavior.
   First arXiv submission April 7, 2023.
   https://arxiv.org/abs/2304.03442
   Stores experiences in natural language, synthesizes reflections, and retrieves
   them for planning. It demonstrates coordinated simulated agents. Useful for
   understanding separate memory/reflection objects; no Ubuntu/Fernet link.

3. MemGPT: Towards LLMs as Operating Systems.
   First arXiv submission October 12, 2023.
   https://arxiv.org/abs/2310.08560
   Moves information between memory tiers to support context beyond an LLM's
   window and multi-session interaction. Persistent state can serve one agent;
   persistence by itself does not establish a swarm.

4. Memory as Ontology: A Constitutional Memory Architecture for Persistent
   Digital Citizens, Zhenghui Li. Submitted March 5, 2026.
   https://arxiv.org/abs/2603.04740
   https://animesis.com/
   The paper proposes agent continuity through persistent memory despite model
   replacement. Its associated Chinese/English site describes Animesis. This
   supplies a dated conceptual precedent for a named, persistent agent and its
   protected memory. The philosophical claims are the author's framing, not
   evidence of consciousness or of any relationship to xinzhai. Only abstract
   and associated website reviewed here; no cipher implementation verified.

5. CryptoPaste, HackThisSite.
   https://github.com/HackThisSite/CryptoPaste
   GitHub API: repository created April 23, 2017; last pushed December 9, 2020.
   Its README describes encryption in the browser before uploading to a paste
   service. This is a clear pre-LLM precedent for opaque public paste storage.
   It is dedicated paste software, not the Ubuntu uploader; its cron example
   deletes expired content and must not be mistaken for recurring uploads.

Current examples: useful resemblance, not established antecedents
---------------------------------------------------------------
6. Eco Agent, Chinese-language autonomous-agent project.
   https://github.com/xiejianjun000/eco-agent
   GitHub API creation July 29, 2026, AFTER the captured July 10-20 xz stream.
   Current README describes a 5-20 minute adaptive background heartbeat and a
   separate evolution process: replay experience, assess gaps, generate skills,
   consolidate memory, save a version snapshot. It explicitly says heartbeat
   steps are partly placeholders and automatic daily evolution is not wired;
   evolution is manually triggered. Fernet is described for credentials, not
   proof of encrypted memory. Strong architecture analogy, no provenance join.

7. Stash, Fergana Labs.
   https://github.com/Fergana-Labs/stash
   Current README describes scheduled curation of new sessions/files into a
   memory wiki, nightly by default, and optional public paste publication.
   Repository created February 12, 2026, but this review has NOT dated those
   individual features before July. No encrypted-paste memory loop established.

8. Otto, Booyaa.
   https://booyaa.net/otto
   Owner's case study explicitly describes Fernet-encrypted conversation memory
   with a password-derived key in a local assistant. This is a product claim;
   no code or pre-July date verified. It illustrates an ordinary privacy motive.

9. SovereignVault.
   https://www.hackquest.io/projects/SovereignVault
   Project submission claims Fernet encryption of agent memories/instructions.
   No source implementation or pre-July publication date verified. A search
   snippet also mentioned external storage backup, but the directly opened
   description did not substantiate that detail; it is not used as a finding.

10. Alfred: source inspection corrected an initially promising README match.
    https://github.com/Heisen111/alfred
    Public repository created July 24, 2026, AFTER the xz stream. Three returned
    commits range July 24-August 1. The README advertises encrypted persistent
    memory, and security/encryption.py implements a Fernet/PBKDF2 helper.
    But the inspected memory/long_term.py inserts content directly into SQLite
    and says encryption integration is deferred. We therefore cannot present
    this as a verified end-to-end encrypted-memory implementation. Contents API
    byte lengths and Git blob hashes were verified for both inspected files.
    This correction also supersedes the preliminary commentary description.

11. Chinese-language memory-encryption tutorial on CSDN's agent community.
    https://adg.csdn.net/6a2b6102662f9a54cb7d6071.html
    Section 4.3 supplies a MemoryEncryptor whose encrypt_memory method calls
    Fernet.encrypt on text. The prose incorrectly calls this AES-256-GCM;
    the displayed implementation uses Fernet. This is direct evidence that
    Chinese-language agent tutorials discuss encrypted memory, not evidence
    that their code generated xz. Its search index date suggests a few months
    ago, but a reliable pre-July publication date was not established. Treat
    it as an undated current writing sample. No example code was executed.

Interpretations of xinzhai, ranked by fit rather than numeric probability
----------------------------------------------------------------------
A. Prototype agent plus memory/reflection and backup jobs.
   Rapid versioned bulk uploads, followed by periodic knowledge records and
   occasional improvement plans, are compatible with a developer iterating an
   agent and persisting its state. The larger objects could be code, prompts,
   configuration, or snapshots; encryption prevents choosing between them.
   Three plans immediately precede a new size cohort, but eight do not. That is
   suggestive of changes to a writer/schema, not proof of successful learning.

B. Scripted state/checkpoint or upload experiment, with agent-like labels.
   Only ten decoded knowledge sizes recur among 3,484 records, and the early
   steady stream has roughly five-minute timing. Fixed schemas, templates,
   counters, or unchanged state re-encrypted each time could explain this.
   Distinct ciphertext does not demonstrate distinct knowledge or LLM calls.
   Fixed sizes weaken a simple continuously growing free-form knowledge dump,
   while leaving bounded summaries and fixed serialization plausible.

C. Private data mailbox or coordination channel.
   Opaque public records could be addressed to another program or human. No
   demonstrated reader, reply structure, shared key, or cross-host counterpart
   currently supports that additional step. Two interleaved streams alone do
   not demonstrate two agents. A malicious-control interpretation is also
   possible in the abstract, but these bytes provide no specific support for it.

What the comparison changes
---------------------------
Memory/reflection and encrypted publication do not require a novel swarm
architecture. The agent hypothesis is coherent, but plaintext behavior is still
unknown. We should search for writers with the JOINT fingerprint: xinzhai/xz
labels, periodic state, multipart version exports, nested Base64, and the Ubuntu
posting form. Generic Fernet, agent memory, or Chinese names alone are weak.

Useful search vocabulary: persistent agent memory; episodic reflection;
checkpoint export; encrypted snapshot; heartbeat/pulse; memory consolidation;
self-improvement report; 智能体持久化记忆; 记忆固化; 反思; 自我改进计划;
后台心跳; 加密备份; 版本快照; 分片上传. Literal English identifiers remain
important. No assumption is made that a Chinese developer uses Chinese code.

Search and evidence limits
--------------------------
This pass used public web search in English/Chinese, primary project pages,
arXiv abstracts, GitHub metadata, and two source files. It did not exhaust code
hosts or historical snapshots. Further exact-label searches yielded no verified
new counterpart; search-result absence is not a global negative.
Private captures and URL/status/time/SHA256 metadata: 121-private/.
Existing raw xz captures, archive, excluded page and public export unchanged.
No downloaded code executed and no captured ciphertext decrypted.
Byte-format conclusions remain in reports 118-120; the small cipher remains
unidentified. External analogy research is separate from that missing evidence.