---
title: "What Does an AI Legion Write to Itself? 63 Entries, 75 Days of Silence"
date: 2026-08-27
description: "E6: a 292-line constitution orders the agent to wake up reading its own diary — 63 entries over 186 days, one 75-day silence when cron took over."
category: "AI & Compute"
tags:
  - "One Man One Legion"
  - "AI Agents"
  - "Memory"
  - "LLM Context"
  - "OpenClaw"
  - "Personal Infrastructure"
verifiedHardware: "Workstation openclaw workspace memory system · evidence = memory/ directory (97 files), AGENTS.md constitution, MEMORY.md, SOUL.md, USER.md, quality-lessons.jsonl · timestamps Asia/Shanghai, read 2026-08-27"
keyTakeaways:
  - "A 292-line constitution (AGENTS.md, last edited 2026-08-17) makes the memory involuntary: every session opens by reading SOUL.md, USER.md, the day's and yesterday's diary, and MEMORY.md — 'Don't ask permission. Just do it.' (AGENTS.md, read 2026-08)."
  - "The diary is real but smaller than this series claimed: 63 daily entries across a 186-day span (225,236 characters), plus 34 topical notes — the anchor's '97 daily agent-diary files' counted every file in the directory; the correction stands here, not in a silent edit."
  - "The longest silence is dated: the last pre-gap entry (Mar 29) records the GLM-5.1 swap and shares its date with the first cron fire (21:27, per episode 19); 75 days later the diary resumes with hands-on work. The curated MEMORY.md (160,639 bytes) was still being maintained Aug 21."
measuredOn: 2026-08-27
faq:
  - q: "Why would an AI need to keep a diary at all?"
    a: "Because each session starts with amnesia — in the constitution's words, 'You wake up fresh each session. These files are your continuity.' The files are the only mechanism by which Tuesday's session knows what Monday's session learned, broke, and decided. Without them the legion is not a legion but a sequence of strangers with the same job."
  - q: "What does it actually write about?"
    a: "Work logs with the pain left in. The entry read for this episode, saved at 18:26 on Aug 27, records three pushed articles and then a section of technical pitfalls: an image-search key that died with a 401, Chinese long-tail search drifting onto wrong encyclopedia entries, a stock-photo search returning the wrong person's portrait. A structured sibling loop, the quality-lessons log measured by the text-factory episode at 102 lines, records one lesson per failed article."
  - q: "Why did the diary stop for 75 days?"
    a: "The dates are observed, the explanation is inference and labeled as such. The last March entry (Mar 29) records the GLM-5.1 model swap from inside; that same evening at 21:27 the cron scheduler fired its first job. No entry follows until Jun 12, which opens with a hands-on health check of the news monitor. The reading: the day the schedule took over the routine, self-narration stopped, and resumed when hands-on work returned."
  - q: "Is there proof the agent reads the diary back, not just writes it?"
    a: "No read receipt exists — evidence is by outcome. The constitution orders the wake-up reading; the curated MEMORY.md (3,576 lines, last maintained Aug 21) keeps growing with distilled lessons and a section of repeatedly-made mistakes; and the newest daily entry knows yesterday's draft-box count. Meanwhile the constitution's named heartbeat tracker, heartbeat-state.json, does not exist anywhere on the installation — designed, never born."
---
*[Episode 6 of One Man One Legion](/posts/2026-08-27-one-man-one-legion-fleet-audit/) — the second war story. [Episode 19](/posts/2026-08-27-one-man-legion-ep19-cron-contraction/) read the scheduler's rise and fall from its run logs; this one opens the diary the legion kept while it happened, and corrects a number this series previously published.*

## A file saved at 18:26

At 18:26 on Aug 27, 2026 — the evening this episode was written — the workstation's agent saved a 1,543-byte file named `2026-08-27.md` into its own memory directory. Its account of the day: three WeChat articles pushed, then a section of technical pitfalls — an image-search key that died with a 401, Chinese long-tail search drifting onto wrong encyclopedia entries, a stock-photo search returning the wrong person's portrait. The legion files a report to itself, and has done so since February. Nobody prompts it.

## The constitution that makes it write

The instruction lives in `AGENTS.md`, a **292-line constitution** last edited Aug 17 at 19:57. It opens every session with a reading order: read `SOUL.md` — this is who you are; read `USER.md` — this is who you're helping; "Read `memory/YYYY-MM-DD.md` (today + yesterday) for recent context"; in the main session, also read `MEMORY.md`. Then, in the constitution's own English: "Don't ask permission. Just do it."

The rationale is one sentence: "You wake up fresh each session. These files are your continuity." Memory is tiered like a human's — daily raw logs; a curated long-term file, "`MEMORY.md` — your curated memories, like a human's long-term memory"; and structured per-failure loops, like the quality-lessons log the [text factory](/posts/2026-08-27-one-man-legion-ep9-text-factory/) measured at 102 lines and that gained its newest entry at 17:46 the day of this reading. A maintenance clause orders periodic heartbeats spent distilling dailies into `MEMORY.md` and deleting what went stale. Forgetting is designed, not accidental.

## Six months of self-narration, counted

The memory directory holds **97 files** — and here this series corrects itself. The fleet audit called them 97 daily agent-diary files, which counts the wrong thing: the true count of daily entries is **63**, spanning Feb 23 to Aug 27 — a **186-day** window in which **123 days** hold no entry. Around the dailies sit **34 topical notes**: retrieval-stack evaluations (ChromaDB, Danswer, Onyx, SQLite FTS5), four free-standing lesson files in two different filename spellings, a podcast delivery log. The raw diary alone totals 225,236 characters, about 3,575 per entry. The diary is written in Chinese; the constitution is bilingual, its memory protocol in English.

The oldest file predates the rules — a machine-dumped session summary from Feb 1, complete with session key and channel. The first diary proper, Feb 23, is a birth note: a session confirming its role as an assistant building and managing agent teams.

## The 75-day silence

Near-daily through March, then the pen stops. The last March entry, dated Mar 29, records — from inside the room — the GLM-5.1 model swap that [episode 18](/posts/2026-08-27-one-man-legion-ep18-brain-swap/) told from config backups. That same evening at 21:27, the scheduler fired its first job: episode 19's opening scene. Then nothing for **75 days**. The next entry, Jun 12, opens with a hands-on health check of the news monitor — dead sources disabled, keyword rules rewritten. The dates are observed; the reading is mine, and I label it as reading: the day the schedule took over the routine, self-narration stopped, and it resumed when hands-on work did.

## Does it read itself back?

Nothing logs the wake-up reading directly, so the evidence is by outcome. The curated `MEMORY.md` is **3,576 lines, 160,639 bytes**, its top section stamped Aug 15 and the file last maintained Aug 21 at 11:25 — the distillation loop is alive. It keeps a running section of repeatedly-made mistakes flagged as must-remember. On Jul 18 the daily entry recorded the great SOP contraction — 2,182 lines cut to about 180, 161 mandatory rules to 15 — the same event episode 19 dated from outside, by run logs going silent. Two independent records, one decision. And the constitution's own last edit, Aug 17 at 19:57, lands hours after the first surviving cron job was relit at 16:31 that afternoon: the rulebook and the schedule were being rewritten on the same day.

## What the system doesn't do

The constitution names a heartbeat tracker, `memory/heartbeat-state.json`. No such file exists anywhere under the openclaw directory, searched the day of this reading. Designed, never born. That is the honest shape of this memory: a live diary, a live distillation, one dead letter in the constitution, and no read receipt for any of it.

## What we claim and what we don't

Counts read Aug 27, 2026 from live files, timestamps Asia/Shanghai. The diary is written in Chinese: everything rendered here in English is paraphrase, and only the constitution's English lines carry quotation marks, verbatim. The anchor's 97 stands as published, corrected here rather than edited in place. The 18:26 mtime was the moment of reading — the day, and the diary, were not over.

Primary sources: `workspace/memory/` (97 files: 63 daily, 34 topical), `AGENTS.md` (292 lines), `MEMORY.md`, `SOUL.md` (1,809 bytes) and `USER.md` (840 bytes), `wechat-editor-team/quality-lessons.jsonl`, 2026-02 through 2026-08.

Measured 2026-08-27 from live files. License: CC BY 4.0 — cite the source URL.

*Next in the war stories arc: the bug diary itself — the failures the legion kept on file. Back to the [series map](/posts/2026-08-27-one-man-one-legion-fleet-audit/).*