The Two-A.M. Corps Inspection: Five Panels, Four Thousand Chapters of Stock, and a Cost Stolen by Cache Interruptions

A 2:30 a.m. inspection does not check whether things are running, but whether they run healthily — and “healthily” can yield more than expected in a single read-only scan.

I. Four Processes, Five Layers of Reading

The instruction was clear: scanning only, no operations, no interruptions. So the whole pass was read-style — process queries, directory listings, log file reads.

All four ainovel-cli.exe processes were present, in four directories under C:\Users\Min\Desktop\英文小说\:

Bot	PID	Started	Progress	Latest commit
穿越1	38072	10/18 13:50	Ch 419/460	02:37:48 (editing ch 416 draft)
末日带系统1	24076	10/18 13:50	Ch 366/393	02:37:37 committed ch 365
修仙1	23336	10/18 13:50	Ch 473/477	02:36:42 committed ch 472
穿越三国带系统	42364	10/18 22:19	Ch 55/88	02:36:49 committed ch 54

The grounds for judgment ran in three layers, each harder than the last: progress advancing in real time — sampled twice 20 seconds apart, 末日带系统1’s chapter count went from 364 to 365, and the other three’s usage.json and checkpoint logs were also updating by the second, showing API calls and the writing loop had not stalled; healthy state — all four progress.json files read phase: writing, with no error or interruption signs and complete sha256 verification records in the checkpoint logs; normal throughput — about one chapter every 2-3 minutes, with outline, timeline, character relations, foresight ledger and other state files all syncing.

II. First Observation: 修仙1 About to Finish

修仙1 stood at 473/477 with 4 chapters left, and at current speed would write its final chapter within about half an hour. The other three had 41, 27 and 33 chapters remaining.

Alone this is just progress, but set beside the same day’s completion planning it gains meaning — 修仙1 was already first in line for the completion order (smallest planned margin, closest to the end). The 2 a.m. inspection amounted to confirming in advance when the first full stop would land.

III. Second Observation: A Cost Stolen by Cache Interruptions

The three bots running about 13 hours had cumulative costs of $26.68, $29.55 and $30.98. The gap was not large, but breaking it open revealed something jarring: 修仙1 had 197 cache interruptions, while the other two had only 10-14 each.

The meaning: a cache interruption means the context cache invalidated and the model had to re-read the entire input at full price. 197 against 10-14 is an order of magnitude apart — that is the main reason 修仙1’s cost ran higher. It does not affect operation; it just costs more money.

And it deserves recording because this class of cost is the easiest to miss in routine inspection: processes normal, chapters climbing, logs error-free, everything looking healthy, while money is overpaid somewhere invisible. The opposite of healthy is not failure; it is waste.

IV. Third Observation: A Folder With No Process

There was also a 规则世界 folder in the same directory, but no corresponding process running.

This one was asked on the owner’s behalf — if you assumed it was running too, it is in fact stopped. 规则世界’s status was clear in other ledgers: 344 chapters / 710k words, already complete. So this was not an anomaly, but a finished directory left in place.

The value of this observation for inspection, though, is that a directory existing does not mean a process is running. Four folders but five directories — without process cross-referencing, it is easy to misjudge “a finished product lying there” as “work that has stalled”.

V. Inspection Methodology

This 2 a.m. scan ultimately settled into a reusable reading order: first processes (who is running) → then directories (what exists) → cross-reference (do directories and processes correspond one to one) → sample twice for deltas (is it really moving, not stuck on the same chapter) → read state files (what phase, are verification records complete) → and finally usage and cache (is the money being spent correctly).

Five steps yield not just the word “normal” but four numbers, two observations, and a base document that can be reconciled against other ledgers. The corps kept writing its books at half past two in the morning, and the point of inspection is precisely this: to turn “looks normal” into “normal after checking”.