Here's the problem it's solving. AI-assisted work kept hitting the same four walls: A session boots with no memory of what stalled last time. The first ten minutes go to reconstructing context instead of moving. An agent fires on a live system before I've approved the action — sometimes subtly, sometimes not. A decision gets made, executed, and evaporates. Three weeks later nobody can find the reasoning. Context bloats until the model is hallucinating on its own earlier outputs, because everything loaded at once. These aren't AI problems. They're operating discipline problems. The capability outran the governance layer. ATX fixes it with a tiered runtime kernel. When a session opens, it doesn't load everything. It classifies the work first — reads its own saved state, identifies the project scope, finds the smallest matching route card — then loads only the agent doctrine that path needs. Nothing broad loads by default. The kernel is four files. The whole system is maybe thirty. Classification before action. That single discipline is what separates a command center from a chatbot with a context window. The governance layer is a named hierarchy, and each name is a gate: Optimus Prime (oath): Truth, proof, refusal, correction. Governs before movement. No claim passes without it. Ultra Magnus (routing): Sequence, operating discipline, handoff. Work doesn't reach a specialist without routing. Kup / Rewind / Teletraan-1 (memory): Relevance, exact record, findability. Three agents answering three different questions about the same past. Prowl (risk gate): Mandatory. Scores every non-trivial action. Can stop movement entirely. Gate-pass is never approval — that's Prowl's only rule. Ironhide (boundary): Live-system and credential hard stops. No bypass path. Specialists: Each acts only inside routed scope. No specialist outranks a gate above it. The naming language is deliberate — more on why in a second. Before ATX speaks, it reads its own state. It recovers context from saved files — boot state, load index, decision log — instead of asking me to reconstruct what happened. It leads with what's urgent or stalled. It surfaces the open items I'd otherwise forget. And at any live-system boundary, any credential touch, any risk score of 3 or above, it stops cold and waits for explicit approval.

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇬🇧 We're back. Good morning from London. 👋 Thanks for the patience last week. Jake and I needed a few days to breathe before London Tech Week kicked off, and you all responded with nothing but support. We don't take that for granted. Now let's get back to building. ---- 📋 THE CHALLENGE Build a folder-based AI operator that handles ONE operational workflow end-to-end. You pick the workflow. This week's deliverable is one operator folder that someone could drop into a Claude project and use to handle a real business workflow without babysitting. ---- 🎯 PICK YOUR WORKFLOW The workflow is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎫 Customer support triage (which tier handles this ticket?) - ✅ Content review and approval - 📨 Lead intake and qualification - 💸 Refund request handler - 🤝 Partnership pitch evaluator - 🎙️ Podcast guest pitch sorter - 💼 Freelance project intake - 📄 Resume screen for one specific role - 📅 Meeting request triage (book, decline, delegate) The more specific, the better. "Customer support" is too broad. "Refund request triage for an ecommerce store doing under 200 orders per month" is right. 📎 If you want a fully written client brief as a reference, the attached PDF walks through one example. Don't build the example. Use it as a template for how to think about scoping your own operator. ---- 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your operator is a folder with five things: - 📄 identity.md (who the operator is and what workflow they own) - 📐 rules.md (the decision logic: criteria, edge cases, escalation rules) - 💬 examples.md (decisions in action, including at least one edge case) - 📚 reference/ (checklists, templates, rubrics) - 📖 README.md (how to use it)