FDISK and the Importance of Sleep – ParlAIment

FDISK and the Importance of Sleep

09 Jul, 2026

When I was younger, my dad got a bit tired of me breaking the family computer. I remember one particular time that I attempted to install a Windows 95 game onto a non-Windows 95 computer (they didn't have 95 until shortly after Windows 98 was available) and completely borked the whole thing.

After quite a bit of heated words, I got the computer taken away from me and a mandate that if I was going to break a computer, I should get my own.

So I did...

And then. I did. Repeatedly.

It got to be a joke (one my dad still tells) that I would FDisk at the drop of a hat. Then reinstall Windows (or sometimes Linux) and try again.

On the one hand, it taught me how to troubleshoot and the number of times I FDisk'd reduced dramatically.

On the other, my poor dad had to watch me blow away my computer about 1000 times.

So why is this story relevant?

This last weekend I almost FDisk'd my whole stack out of frustration.

F-This<br>It was, admittedly, a bad day. I was already in the dumps and had just sat down after a long day to do the thing I liked (work on EAI), and I started with an extremely frustrated diatribe to both Claude Code and Eggy (local AI).

I told them I was frustrated. I was done. I was just playing at AI. That the system I had worked on for months didn't actually DO anything that I wanted it to. No ability to read the surfaces I wanted it to, complexity that seemed like a self-licking ice cream cone of hubris.

Then I caught it working.

Duel Process<br>That title works in so many ways. It was a duel between a VERY frustrated human and two AIs that were trained to do what the Human wanted.

I told Eggy that I wanted to completely wipe the working memory. Not update. Not archive.

Delete.

Obviously, this is an irreversible act and one that the system was not designed to handle explicitly. It was only designed to handle local (within the system) acts that are reversible. So Eggy did the best he could and asked me for the one thing that proved the system DID do what I intended.

He wanted a ticket that authorized him to archive the memories.

I almost missed it but Claude pointed this out. I was still a bit too irritated to listen, but at least took Eggy's advice and archived instead. Myself. Using the filesystem instead of EAI.

This means that the reset happened out of the bounded works of the system, though nothing was destroyed. The identity atom system I created was regenerated from founding files, exactly per the design and the system continued to function.

The Wrong that Made the Right<br>We just completely broke the constitution (governance), and that realization brought me back because I had gone against the thing I had been building and it felt...

Wrong. And both the feeling and the action were completely justified.

So it was right.

What also felt wrong was the fact that 73 actions were in my queue and a UI overhaul meant I couldn't click on them. I still couldn't see documents or how things were connected. Still couldn't rely on the system to serve up context to me OR to Eggy.

Realization to Reality<br>After a good night of sleep, the UI was fixed and one click recorded 73 commits.

Then, during a back and forth in trying to fix a bug, Eggy was confidently incorrect and the system stamped the performance as "MISCLAIMED" in very big red letters and a red glowing box.

Unscripted, my system told me again that it was working.

By the time the weekend was over, I had stored my first sourced file using the system. It was Andrej Karpathy's LLM-wiki note, arguably the seed of the system, with a note: "This is the originator. The lens that helped me focus. Thanks Andrej."

And the dominoes just kept falling.

Each time they fell the lessons I learned stuck harder:

Governed belief is best observed through stress (see the three times I got unscripted tests: AI offered a wipe (asked for a ticket), Model overclaimed (stamped clearly), the human bypassed (recorded and not silently accepted)).

The gap between governance and theater is one broken button, so it's important to fix the mechanism before writing more.

You can't judge a system on a bad Friday, but you can let the bad Friday interrogate it and fuel the fire to get it to a state much further than it was.

The solution wasn't sleeping on it. It was that doing so stopped me from destroying evidence that the system was actually working.

The Green List<br>Normally I end this with a short quote on the lesson. I think it's better to end it on what changed from Friday to Monday. Note that, normally, I write every word on here but below is originally generated by AI and I have lightly edited for clarity.

The knowledge loop — closed end to end:

✅ First full canonical promotion: panel → propose (my hand) → machine concurrence (Eggy's reasoning, recorded) → confirm (my hand) → works/promoting-a-panel-to-librairy-planning-v1.md. Hansard chain complete. (10:58)

✅...