069 — REVIEWED: startup has paired five-minute small records
September5,2026. Focused local review of xinzhai/xz startup.

Finding
The first30 xz_knowledge_p1 posts are more structured than an irregular startup burst. After single entries at22:24 and22:25 on displayed July10, there are exactly TWO distinct124-character bodies at each five-minute slot from22:30 through23:35 inclusive:14 paired slots. This continues after the final v73 multipart upload ends at22:44.

Observed schedule
22:24: one post, ID4548564.
22:25: one post, ID4548565.
22:30,22:35,22:40,22:45,22:50,22:55,23:00,23:05,23:10,23:15,23:20,23:25,23:30,23:35: two posts at each displayed minute, different body hashes within every pair.
All30 bodies have124 authored characters; report056 verified their canonical transformed size of93 binary bytes and unique hashes.
There are22 small records after the last bulk-upload minute on the same day. The final pair is51 displayed minutes after the end of v73. The next small record appears at15:11 on July11,936 displayed minutes after23:35.

Implication for the workflow
The small stream is not explained solely as one acknowledgement or marker per large upload: repeated pairs continue with no further captured large upload. A recurring publishing task is a better model. Two nearly synchronized jobs, one job emitting two record types, or repeated serialization of the same underlying state are possible. Unique ciphertext-like bodies do not prove different plaintexts. The one-minute timestamp resolution does not reveal exact synchronization or order within a minute.
The paired stream runs during v71/v72 uploads, so bulk activity does not prevent periodic small publishing. Interleaved requests can come from one program; this does not establish two agents or machines.

Version-label caution relevant to client search
The large labels are unversioned, v5.2, v52, v60, v61, v70, v71, v72, v73. Dotless release labels such as6.0/6.1/7.0/7.1 are an alternative to literal snapshot counters60/61/70/71. The explicit v5.2 makes this worth testing, but naming alone does not resolve it. Do not infer73 historical snapshots or a uniform version-increment rate. Either interpretation can fit iterative client development/configuration during startup.

Reproduction
python3 investigation/china/069-xinzhai-startup-cadence.py
Input:039 final checkpoint rows, previously independently hash-checked against raw sources in056. Output:069-private/analysis.json with exact slot IDs, counts and boundary records. All timestamps remain website-displayed claims. No origin requests, decoding, key search, or pasted-code execution in this cadence analysis.