Reading path
Ten pages covering eleven parts, one a day for eleven days, so you end able to name every part of an AI agent.
One page a day in the order a part becomes understandable: the three that make the machine, the three that decide what it knows, the three that decide what it may do, and the one that lets it start on its own.
10 pages, in order. About 59 minutes in all.
Nobody clears two hours for a subject they are not yet sure matters. So this is the same material at a different pace: a single page each morning, about six minutes, for eleven days. The eleven days are the eleven parts of the Cabinet, which is ArkOne’s reference design for an executive agent, and the promise is that on the twelfth morning you can name all eleven and say what each one decides.
Ten pages sit below, not eleven, and the reason is worth knowing before you start. Two of the eleven parts, the Signature and the Record, are covered by one page. The Signature is the step that waits for a person; the Record is what gets written whether or not anyone waits. They are separate parts and they were written up together because the interesting thing about them is the relationship, so the eighth day is a double. Ten pages, eleven parts, eleven days, and the eighth day asks slightly more of you than the others.
The order is the order in which a part stops needing the one after it to make sense. The first three build the machine itself: the thing that runs the turn, the way it asks several specialists at once, and what a specialist is when you open one up. Those three are the floor. Nothing later means much without them, and a reader who does the first three days and stops has still gained the ability to follow a demonstration.
Days four to six are about what the thing knows. What it is handed at the start of every turn, where it goes to look something up, and what it remembers tomorrow. These are grouped because they are constantly mistaken for one another, including by people selling the system, and reading them on consecutive mornings is the cheapest way to stop confusing them.
Days seven to nine are the ones a chief executive tends to care about most, and they are last of the substantive run rather than first on purpose. What may leave the building. Who signs, and what is recorded. Which underlying model answers which kind of question, which sounds like a technical detail and is in fact where the bill comes from. Read on day one, these three read as reassurance. Read after six days of knowing what the machine is, they read as settings somebody chose, and you can ask who.
The last day is the Clock, the part that lets the whole arrangement start something without being asked. It is eleventh because it is the only part that changes the character of everything before it, and reading about unattended work before you know what the work is produces alarm rather than judgement.
What a day-at-a-time reading costs you is the whole room at once. Eleven mornings spread over a fortnight leave you with eleven parts you can name and a weaker sense of how they press on each other, which is the thing a single sitting gives you and this does not. If you would rather have that, the first-read path runs the same material in one sitting and adds the two primers this path assumes you will pick up as you go. The pages to read before a clinic day is the shorter version of the same thing, for somebody with a day booked tomorrow.
If eleven days is more than you want, do days one, seven and eight. That is about twenty minutes in total and it leaves you able to ask what stops the loop, what may leave the room, and who approved the last thing that left.
Left out entirely: every account of one of these parts going wrong, and everything about cost. The failures live in the case notes, which are better read once you know the parts, and the cost mechanisms need one sitting with your own numbers rather than eleven short ones.
The certification teaches your own people to build and govern what these pages describe.