The Arcs

A hundred and thirty-one field notes, filed by date. Which is the least interesting thing about any of them.

Date order is how a journal gets written. It is not how a story gets read. Open the archive at the top and you meet last Tuesday’s firewall incident with no idea that the same fight has been running since April — that this is chapter nine, and chapters one through eight explain it.

So: five arcs. Five recurring fights this haus keeps having, each one an ordered path through the notes that belong to it. Follow an arc end to end and you watch an idea get beaten into shape over four months. Read by date instead and you get a weather log.

Tommy, the haus’s Abyssinian and its only immortal employee, has been present for all of them. He offers no help. He does, however, sit through every one.

Tip

Every note is also a standalone incident with its own diagnosis, so you can drop in anywhere. The arcs are for when you want the argument rather than the answer.

The Cathedral Arc — teaching a Mac Mini to think

The longest and most technical thread: getting a 35-billion-parameter model to serve a household from a closet, and discovering — repeatedly — that the model was never the problem. The instruments were.

1. The Reasoner That Went Quiet — twenty-five hours of green probes, then the service answers a real question with nothing at all.
2. The Cathedral Sees — vision lands after eleven days of a 503 wall.
3. The Vision Probe Lied — the probe that reported success on a broken path.
4. The Kernel Needed Two Tokens — same prompt, warm cache, different answer.
5. The Cathedral Could Not Read Long — a context ceiling nobody had measured.
6. The Champion Who Memorized the Exam — the model scored well because it had seen the test.
7. The Gate That Says No to Memorization — so the exam got locked in a drawer.
8. The Ruler Was Broken, Not the Model — the thesis of the whole arc, stated plainly.

The lesson: every time this haus concluded “the model can’t do it,” the instrument was broken. Twice. Then a third time.

The Curfew Arc — a promise that has to hold at 21:30

The family-facing thread, and the one with the highest cost of failure: a rule about screens that has to be true even when a vendor’s cloud is down, even when the enforcement layer politely reports success.

1. The Allow Button, Retired — the control that quietly undid the rule.
2. The Screen That Rewarded Forgetting — an incentive designed exactly backwards.
3. The Block That Killed the Hub — enforcement with too wide a blast radius.
4. The Device That Announces Itself — you cannot govern what you cannot name.
5. The Firewall That Quarantined the Dishwasher — twenty-nine appliances jailed by a stamp nobody read.

The lesson: a command that returns success is a claim, not a fact. Read the state back, every time.

The Leak Arc — custody of the keys

Four months of learning that a secret is not safe because it is encrypted; it is safe because you know every place it lives.

1. The mTLS Day — five probes migrated before lunch.
2. The Vault Spoke, Then I Misheard — the answer was right there and got read wrong.
3. The SSH Key the Box No Longer Needs — removing access is a feature.
4. The Post-Quantum Vault Ceremony — key material for a threat that has not arrived.
5. The Secret That Was Never Missing — the status word said absent; the value was present.
6. The Key Baked Into the Wall — a live token compiled into a published binary.

The lesson: hiding a leaked key buys a day; rotating it buys back the day it leaked.

The Network Arc — the haus versus its own plumbing

Doors, gateways, netmasks, and one ISP. The most user-visible arc, because when this thread breaks, somebody in the haus cannot watch anything.

1. Asymmetric Doors — in is not the same as out.
2. The Front Door — one way in, on purpose.
3. The Door the Printer Opened — the threat model forgot the office equipment.
4. The Slash-One That Ate the LAN — one wrong netmask, one dead network.
5. The Speed Test That Cried Slow — the measurement was the bug.
6. Closing the LAN — the loopback surface sweep.
7. The Alarm Nobody Could Answer — a perfect smoke detector and no fire brigade.

The lesson: when something that worked breaks, ask what changed — and diff the working twin before theorising about physics.

The Self-Healing Arc — building something that fixes itself

The spine of the whole project: the night twenty-six services fell over, and everything built since to make sure the haus notices before a human does.

1. Living Force Manifest Deployment — the immune system gets its memory back.
2. The Pressure Valve Trilogy — a kernel panic at midnight, a daemon by lunch, the daemon killing its own patient by dinner.
3. First Breath — the body, half-wired, breathing.
4. The Ladder That Heals Itself — remediation with rungs.
5. R2D2 Got Honest → Got Courage → Stops Paging Itself — a supervisor growing up in three notes.
6. The Guards That Cried Wolf — alert fatigue as an engineering defect.
7. The Doctor That Fainted at Every Diagnosis — the diagnostic tool was the outage.
8. Fail Open, Fail Closed — the only question that matters when a guard dies.

The lesson: a system that lies about its health is more dangerous than one that fails, and a healer with no diagnosis is just percussion.

If you only read three

The Pressure Valve Trilogy for the shape of a hard day. The Firewall That Quarantined the Dishwasher for how an investigation should go — including the part where it accused the wrong colleague on nothing but timing. The Ruler Was Broken, Not the Model for the single most expensive lesson in the archive.

Then the doctrine pages hold what all of it distilled into, and the annex keeps the receipts the doctrine no longer has room for.

Five arcs, one recurring shape: the haus was never wrong about the fact that something hurt. It was wrong, over and over, about what it was measuring — and every note above is the same lesson wearing a different night.