The Markdown Department

Build a working AI department out of plain-text files. One AI employee is a trick. A department is a business. Craig Nkonge's first boo Then the new problem multiplication creates: the files have to talk to each othe Plain, blunt, funny where the truth is funny — every story in it happened. Same four files as book one, multiplied by the jobs that need doing, governed, reviewed, and corrected scar by scar. One employee was the demo. The department is the business.r. Charters, handoffs, a ten-line constitution. What breaks at scale — the rogue that drifts, the silent one, the double doing the same job twice, the sprawl — and the human-approval rails that keep every risky move waiting on a tap. The Tuesday review: thirty minutes that steer the whole department.k taught you to build one AI employee out of four markdown files. This one multiplies it: the money watcher that enforces the no-assumptions law every morning, the content runner that batches a week of posts without burning the voice, the lead scout that triages the inbox into three piles and drafts the reply, the scheduler that holds the calendar and files on Friday.