Decision memorandum / September 2026
The First Cut: Tool or Entity?
Before revenue growth, valuation or compensation, determine what the company believes is standing on the other side of the text box.
01 / The decision
What does this company believe AI is?
The advanced student will eventually face a practical question: should I bet on this company—or, more consequentially, should I join it?
To bet is to invest capital. To join is to invest years. The decisions are different, and neither should rest on one idea alone. Balance sheets matter. Valuation matters. Leadership, culture, competitive position and technical execution all matter.
But I would begin both decisions with the same first cut. Before asking how much AI the company uses, ask what the company believes AI is.
Is AI an instrument a person operates—or an entity to which responsibility can be assigned?
This is not a prediction about next quarter’s stock price. It is an attempt to identify the company’s underlying philosophy of the transition now underway. Products can change quickly. An organization’s ontology—its settled answer about what kinds of things exist and where agency belongs—is much harder to move.
The distinction, entered in the ledger.
The labels are not moral rankings. They describe two architectures—and two very different corporate futures.
02 / What entity means
I do not mean sentient.
Be precise. Entity here is not a claim about consciousness, souls, legal personhood, rights or artificial general intelligence. It is an operational category.
An entity can be assigned a role. It can have a name, hold context, receive permissions, use resources and carry an objective across time. It can decide which available tools to use. It can work while you are doing something else. It can return with a completed artifact or escalate an exception it cannot resolve.
Most importantly, responsibility can be arranged around it. You can ask what it owns, what it may touch, when it must stop, who evaluates its work and what happens when it fails.
A tool is fundamentally different. You pick up a hammer. You open Excel. You invoke a calculator. The tool does not have a job. You have the job; the tool extends your capability.
A role can be synthetic without pretending the role-holder is human.
This distinction determines more than interface language. It flows into product architecture, pricing, security, organizational design, job descriptions and management philosophy. A company building better instruments for the existing workforce is making a different bet from a company reorganizing work around assignable intelligence.
03 / The IBM case
A coherent tool philosophy can still build agents.
I spent roughly twenty years at IBM, so I use IBM deliberately. You do not have to infer its declared philosophy. IBM’s first Principle for Trust and Transparency states that the purpose of AI is to augment human intelligence. The company says its systems are designed to enhance and extend human capability rather than replace it.
That is an extraordinarily coherent philosophy. It is also, in my framework, a tool philosophy. The human remains the primary entity. AI assists, enhances and extends the human.
Yet the evidence cannot stop there. IBM also sells agents. Its watsonx Orchestrate Agentic Control Plane governs and scales agents, exposes their access to tools and data, and supports scheduling for recurring work. An enterprise can use IBM technology to run processes without a person manually triggering every cycle.
This is exactly why the word agent is no longer diagnostic. A company can build autonomous systems inside a worldview that locates ultimate agency, judgment and accountability with people. That may be the prudent design for many consequential settings. It may also constrain the company’s organizational imagination. The point is not that one philosophy is virtuous and the other reckless. The point is that they compound toward different destinations.
Primary evidence: IBM’s Principles for Trust and Transparency and IBM’s Agentic Control Plane announcement.
04 / The entity case
Delegation changes the unit of work.
Now consider Anthropic’s language around Claude. Its research defines an agent as a model that directs its own processes and tool use while accomplishing a task: it plans, acts, observes, adjusts and repeats until the work is complete or human judgment is required.
Claude Cowork makes that architecture legible. A user can hand Claude multi-step work across files and applications. Claude Tag makes the shift social: a team can tag Claude in a Slack channel, delegate a task and continue doing something else while it works. Anthropic describes the experience as closer to collaborating with a teammate than operating a single-purpose interface.
OpenAI’s Workspace Agents reveal the same conceptual move from another direction. They combine an objective, instructions, approved tools and a trigger. An agent can run on a schedule or begin through an API, carrying a repeatable workflow across connected systems.
No one needs to pretend these systems are people. The relevant fact is that work is being packaged around a bounded bearer of responsibility rather than around a human continuously manipulating software.
Primary evidence: Anthropic on trustworthy agents, Anthropic’s Claude Tag announcement, and OpenAI’s Workspace Agents documentation.
05 / The interface
Role assignment feels natural because the model can maintain a role.
Listen to how people begin serious interactions with frontier AI: “You are my research analyst.” “You are responsible for following up with every inbound lead.” “Monitor this account every morning.” “Find the discrepancy and interrupt me only if it exceeds ten thousand dollars.”
You would never open Excel and say, “You are my chief financial officer.” Excel is an instrument. It contains extraordinary capability, but the role remains yours.
With a frontier model, role assignment feels natural. Give it an objective, context and boundaries, and a coherent pattern of behavior emerges around the assignment. A math tutor teaches. A researcher searches, weighs evidence and writes. A monitoring agent watches for changes and decides whether a condition deserves escalation.
The important breakthrough in conversational AI was not merely fluent text. It was the sensation that one continuous counterpart could remain with you as the subject changed. Physics, Shakespeare, Python, a business plan, a private problem: the conversation survived the transitions. Earlier interfaces exposed the edge of their programming. The generative interface created the experience of continuity on the other side of the box.
The great transition is not from manual work to assisted manual work. It is from execution to delegation.
06 / The organization
Ask leadership to draw the company five years from now.
A tool-oriented company tends to imagine essentially the same organization populated by more productive humans. Every salesperson has an AI assistant. Every programmer has an AI coding tool. Every accountant has a copilot. Ten thousand employees become ten thousand AI-enabled employees.
That could be a valuable company. It may improve quality, reduce drudgery and distribute expertise. But it is the old organizational chart wearing new technology.
An entity-oriented company imagines something stranger. Some responsibilities belong to people. Some belong to AI. Some are shared. A person may supervise a portfolio of synthetic roles. One agent may coordinate specialist agents. Entire positions may dissolve because no person needs to occupy the execution layer continuously.
The unit of organizational design changes from person plus software to entity plus responsibility. Sometimes the entity is biological. Sometimes it is synthetic. In both cases, the organization must still answer who sets purpose, who grants authority and who bears consequence.
This is also why the entity philosophy cannot mean “remove the humans.” Mature delegation increases the importance of human judgment. Someone must define the objective, shape the institution, choose the constraints, evaluate the result and remain accountable when the system affects other people.
07 / Our language
“Bring your AI” is an ontological statement.
At Charleston AI, we use the phrase deliberately. Bring your laptop means bring equipment. Bring your AI implies continuity: arrive with an intelligence relationship that already carries context, preferences, working methods and responsibility.
The possessive matters too. Your AI. Not our feature. Not the institution’s seat. You arrive with an entity you have been shaping, and the work is to make that relationship more capable, more accountable and more sovereign.
This does not settle the technical architecture, and it does not erase security boundaries. A company must still control access to its data. A person should not grant an agent indiscriminate authority. Entity thinking is not a license for anthropomorphism or carelessness. It is a commitment to organize technology around roles, permissions, memory, responsibilities and relationships instead of one isolated feature invocation at a time.
Run the first-cut audit.
Open the evidence file. Company language is useful, but architecture and organizational imagination carry more weight than branding.
01 / Is responsibility persistent or merely invoked?
02 / Can I delegate an outcome instead of prescribing a procedure?
03 / Can the system select and coordinate tools?
04 / Can it act because something happened?
05 / Does it escalate exceptions instead of every ordinary step?
06 / Is the human doing the task or governing responsibility for it?
07 / What organization does leadership imagine?
Before you bet your capital—or a decade of your life—find out who the company believes can own the work.
A product can change in a quarter. An ontology becomes thousands of decisions.
1 thought on “The First Cut: Tool or Entity?”