The Agentic Enterprise
How Delegated Software Changes Coordination, Management, and Firm Boundaries
What happens when organizational coordination itself becomes partly computational?
The executive summary will be derived from the fourteen chapters as the manuscript is completed.
The Shift
- Chapter 01
Organizations Already Compute
The enterprise did not wait for generative AI to begin computing its work. Chapter 01 establishes what organizations already compute, where that computation reaches its boundary, and what may change as software becomes capable of interpreting context and acting within it.
Read Chapter → - Chapter 02
From Tools to Delegated Participants
In Development
The Coordination System
- Chapter 03
The Coordination Bill
Coordination has a bill — paid in discovery, interpretation, commitment, monitoring, resolution, and repair. Chapter 03 makes that cost visible and keeps the question empirical: whether agents reduce the bill is a testable proposition, not an assumption.
Read Chapter → - Chapter 04
The Heterogeneous Organization
An enterprise is a collection of domains with different responsibilities, records, vocabularies, incentives, and rights to decide. Chapter 04 argues that visibility does not settle meaning and presents federation as a design direction: coordination across distinct sources of knowledge and authority.
Read Chapter → - Chapter 05
Work as an Explicit Commitment
Task records capture activity, but the central obligation often stays implicit. Chapter 05 presents the commitment as an explicit coordination object — outcome, accountable parties, authority, evidence, and exception paths — and keeps the discipline conditional: formalize where it improves shared understanding enough to justify the effort.
Read Chapter → - Chapter 06
An Institutional Memory That Can Be Wrong
Delegated software acts through context, which makes organizational memory part of the control path. Chapter 06 sets out what memory must preserve — provenance, validity, correction paths, and surviving disagreement — for an emerging coordination architecture.
Read Chapter →
The Institutional Consequence
- Chapter 07
Beyond the Enterprise Brain
The enterprise brain is an attractive image for agentic coordination, and a poor institutional model. Chapter 07 distinguishes information access from decision authority, examines what centralization does well, and presents a federated intelligence architecture in which authority remains attached to roles, policies, and accountable processes.
Read Chapter → - Chapter 08
Management After Machine Coordination
Management is partly a response to coordination costs. Chapter 08 examines what may change when software maintains routine coordination: a plausible reallocation of managerial attention, accountability structures under delegation, and the risks of surveillance, workload, and metric pressure.
Read Chapter → - Chapter 09
Who Is Allowed to Decide
When software can interpret context and act, authority becomes visible in a new way. Chapter 09 sets out delegation as a governed act — principal, jurisdiction, action, conditions, escalation, review — and frames the distribution of decision rights as a constitutional choice.
Read Chapter →
The Enterprise Boundary
- Chapter 10
Faster Coordination, Faster Failure
Coordination speed has a double edge. Chapter 10 examines how delegated software can extend the reach of an error across workflows, and sets out the containment safeguards — scoped permissions, evidence gates, circuit breakers, reversibility — that keep speed from becoming systemic failure.
Read Chapter → - Chapter 11
Agents Across the Company Boundary
Chapter 11 examines what happens when delegated software meets a counterparty. Cross company agent interaction depends on institutions as much as interfaces — identity, scoped delegation, semantics, commitment, provenance, and recourse — and technical interoperability should never be mistaken for trust.
Read Chapter → - Chapter 12
Does the Firm Become Smaller
Chapter 12 asks whether agents that lower coordination costs will make firms smaller, larger, or simply different. The answer depends on which costs fall faster — internal administration or market coordination — and the direction remains an empirical, conditional question.
Read Chapter →
The Conditional Future
- Chapter 13
The Autonomous Enterprise on Trial
Chapter 13 treats the autonomous enterprise as a claim to be tested, not a forecast. It defines the unit of autonomy, sets out how a bounded trial should be run and evaluated, and places the burden of proof on the claim.
Read Chapter → - Chapter 14
A Constitutional Choice, Not a Technological Destiny
Chapter 14 closes the publication by framing the computational enterprise as a set of institutional choices. It sets out four open trajectories, the constitutional questions each answers, and a discipline for choosing that keeps the future conditional.
Read Chapter →
This Publication represents an independent editorial publication developed from publicly available information, original analysis, and professional experience.
It is published as part of Sentient Review, Volume 01, Publication 03.
The organizations discussed provide context for the publication's independent exploration of enterprise transformation, operating models, engineering leadership, enterprise architecture, governance, and AI.
Each Publication contributes to an evolving body of executive work dedicated to increasing clarity, coherence, and practical insight for enterprise leaders.