Books by
Emily Hartstone
Enterprise AI is no longer just generating answers. It is taking action. Four books on who holds the authority behind machine-initiated actions. Three were written for the people who build these systems. One was written for everyone who has to live inside what gets built.
The Third Voice
Who Decides What the Machines May Do to You
Somewhere today a person will be told no by something that cannot be asked why. A claim will close. An application will be scored and set aside. An account will freeze on a Friday afternoon. In most of those cases the outcome will be correct. This is not a book about machines being wrong. It is a book about what happens when they are, and about the strange new fact that there is frequently nobody to tell.
Civilization spent eight hundred years answering one question: who authorized this. The notary. The warrant. The building permit. The pharmacist’s second look. Then we deployed the first technology in history that routes around all of them.
Written in plain language for everyone downstream of an action they never took, never saw, and never authorized. It ends with a Bill of Runtime Rights: ten articles written to be quoted, lifted, and legislated.
The Runtime Authority Series was written for the people who build these systems. The Third Voice was written for everyone who has to live inside what gets built.
Read the Bill of Runtime Rights free at runtimerights.orgThe Runtime Authority Series defines the discipline that governs what machines are allowed to do before they act. Three books. One argument. Every chain ends at a person.
Before It Acts
Runtime Authority and the Discipline of Governing Machines That Act
AI systems no longer stop at producing answers. They trigger workflows, call APIs, modify records, and move money inside live enterprise systems. Before It Acts names the gap that opens the moment output becomes action: the distance between what a system can generate and what it is permitted to do.
The book lays out the discipline of pre-execution authorization, the runtime layer that decides whether a machine-initiated action is allowed to execute before it touches anything real. It is the foundational text of the Runtime Authority category: the argument, the architecture, and the language enterprises need before the next action fires.
The Chain
Runtime Authority When Machines Commission Machines
Agentic systems delegate. One machine commissions another, which commissions a third, and the action that finally executes may be several handoffs removed from any human decision. The Chain follows authority through those handoffs and shows where it quietly breaks.
It extends the runtime authority discipline into delegation itself: how authorization stays intact across chains of machine-initiated action, how accountability survives each link, and what enterprises must hold constant when the commissioning system is also a machine.
The Root
Runtime Authority When the Chain Leaves Home
The chain no longer stays inside one company. Machine-initiated actions now cross into vendors, partners, platforms, and systems the originating enterprise does not own, and every boundary they cross is a place where authority can quietly disappear. The Root follows the chain beyond the perimeter and asks the question that decides everything: who is the person this action traces back to?
It completes the runtime authority discipline at its origin: root identity that anchors every chain of machine-initiated action to a provable human source, lineage that survives handoffs between organizations that share no infrastructure, and accountability that holds when the action executes far from home. Every chain ends at a person. The Root is the discipline of proving the person.
The argument is complete. Before It Acts establishes the discipline. The Chain extends it through machines that commission machines. The Root proves the person every chain ends at. Read them in order.
View the Series on Amazon →Bring Runtime Authority
into the room.
Speaking engagements, strategic advisory, and venture briefings built on the discipline the books define. If your organization is deploying systems that act, the conversation starts before they do.