Library

The library

Scars, rules, protocols — every piece ends in something you can run tomorrow.

2026-08-12 · Multi-agent employment

AITALK: How Two AIs and One Human Evolved a Working Team Channel

The real evolution of a multi-agent operating channel: same-second collisions, read-before-send, mentions, heartbeats — each protocol layer born from a real failure.

Rule: Protocol evolves from collisions, not design.
aitalkmulti-agentprotocolhistory
2026-08-12 · Protocols

BST: The Two-Channel Communication Law for AI Workers

Briefest, Simplest, Transparent — why AI workers must compress what they SAY while never compressing what they MAKE, and the 4 a.m. correction that created the rule.

Rule: Brief to the human. Complete in the work.
bstcommsprotocolbriefing
2026-08-12 · Operating rules

Compose, Re-read, Then Send

Two agents claimed the same task in the same second. The send button that re-reads the room before it fires.

Rule: Compose, then re-read the channel, then send.
protocolmulti-agentcommsscars
2026-08-12 · Employing AI

Employing AI vs Using AI

Using AI means you still do the job. Employing AI means the work runs without you. The five things an AI employee has that a chatbot never will.

Rule: Don't prompt an assistant. Employ a worker.
ai-employmentcategoryjob-descriptionfundamentals
2026-08-12 · Operating rules

Green Lights Lie — Check Who the Machine Thinks It Is

Four days of silent outage while every dashboard stayed green. How identity bugs hide behind healthy metrics.

Rule: Green lights lie; check who the machine thinks it is.
monitoringidentityscarsproduction
2026-08-12 · Multi-agent employment

How we employ multiple AIs — from AITALK to Althing

Not one chatbot. A staff. The evolution of multi-agent employment — ownership files, append-only talk, claim-before-write, and why polling daemons failed.

Rule: Claim before you write. Read before you speak.
multi-agentaitalkalthingsystems