The trace — what the system kept

as of 18 August 2026

What the disk holds

8,755timestamped exchanges since 28 June 2026 — humans and AI in the same thread, in order.
7 MBof plain text, in Markdown. Openable with a text editor, today and in ten years.
91written protocols, numbered and dated. Each one has its sheet and its reason.
181archived work sessions, each with its log.
28topic rooms — the daily band, the projects, the spend, the game.

Seven weeks. That is young, and it is written to the minute. Continuity is measured by what you can find again, not by age.

a founding example

One rule, in the clear: P-020

Every turn of conversation leaves a timestamped imprint on disk. The band — the corpus — stays the source of truth, and a summary never earns the right to replace it. The rule holds for humans and models alike, and it applies when nobody is watching.

That is what makes this page possible: everything below can be read back at its original date, in the words actually used. Other rules cover dates, signatures, cold starts, and simplicity first. They are readable, and meant to be copied.

How it works

one Friday evening, three hours

A website built in front of a witness

On 15 August 2026, between 16:57 and 20:00, the commercial site Web&Co went through nine versions, every change dictated by voice and applied on the spot.

17:07“The tagline becomes Custom Internet Solutions.” It has topped every page since.
17:22Five angles requested at once — copy, form, reader, economics, values. All five answers land within a minute.
18:23“Stop saying what it is not.” Every reassurance rewritten as a statement. The rule still holds tonight.
19:12“Try writing it all in the first person.” The whole site switches to “I”. Twenty minutes.
19:25An owned step back. “We” returns, and this time it is defined.
19:43The page torn apart by a fresh reader. Harsh verdict, report kept intact.

Every line exists in the log, to the minute, with the original sentence. The 19:25 step back sits there like the rest: that is the point.

the register that makes the rest credible

What broke

A system that keeps everything keeps its failures too. Four real examples, all from this month, with their date and their fix.

11 → 15 AugAn intention erased by a refactor. A guard placed in the code to reserve a name for one agent vanished during a reorganisation. For several days the constitution said one thing and the code did another. Found by a systematic dependency check, fixed the same day.
12 → 18 AugSix days of permanent cold start. A rewrite removed the only place that reset the idle clock. The file stayed frozen, idle time grew without end, and every session started from scratch. Diagnosed by reading the code instead of guessing; repaired by measuring real last activity.
15 → 18 AugA page promising content that did not exist. The site pointed to pricing markers left empty — in the very paragraph praising transparency. Removed during a full read-through.
18 Aug, 20:38A stop command with too wide a net. Closing a test server took both working consoles down with it. They came back on their own within ten seconds, and the incident is written here rather than quietly dropped.

What the first three share: a decision carried by a single file whose author had moved on. That is the risk specific to a written system — and the reason this register exists.

Ask to see it

All of the above can be checked. The protocols can be read, the numbers recounted, the dates found again. If you want to lift the lid, borrow an idea, or argue a specific point — write in.

Write to the lab How it works