Navigation
Getting Started
Reference: directing
Watching
Reference: shaping
Optional budgets
Problems
Concepts & package reference
Reference
Concepts

The exocorp

A company whose cognition and action are carried by autonomous agents operating inside a durable organizational substrate.

What it is, exactly

An exocorp is still a company. It has a durable identity and boundary, explicit authority, governed resources, and accountable contact with the outside world. What’s different is the operating matter — meaningful parts of noticing, interpreting, planning, executing, reviewing, remembering, and improving are carried by non-human workers.

Humans aren’t absent. Humans may found the exocorp, own it, constrain it, govern it, invest in it, approve high-risk actions, supply direction, participate in selected workflows, or shut it down. But humans are no longer the only workers through which the company senses, reasons, acts, remembers, and improves. Human involvement becomes a governance and interaction question, not the definition of the organism.

What an exocorp is not

  • Not a chatbot swarmA chatbot swarm has many agents talking. But conversation is not a company. A company needs a durable boundary, explicit authority, owner-qualified state and obligations, evidence, governance, external contact, and a way for outcomes to change future behavior. Without those things, the swarm is theater.
  • Not a task queue with autonomous workersA task queue assumes the important work has already been recognized and shaped into executable form. The harder company problem is upstream: what should be noticed, believed, tested, promised, rejected, continued, or killed? When work items become primary too early, the company starts protecting itself from uncertainty.
  • Not a workflow engineWorkflow engines assume the shape of the process is knowable enough to encode. A company may install workflow packages, but the common runtime does not require one process model or treat workflow transitions as kernel meaning.

The defining properties

An exocorp is bounded, agent-primary, coordination-neutral, and able to revise its selected operating structure under explicit authority and outcome pressure.

  • BoundedAutonomy without boundary is not company autonomy — it’s open-ended tool use. An exocorp knows what it’s trying to be, what it’s allowed to do, what it has promised, what resources it may spend, and when it must ask for permission.
  • Agent-primaryAgents are primary product users and may design, launch, operate, evolve, and repair the company through bounded machine-facing interfaces. A required human UI is not the operating center.
  • Coordination-neutralA company may be one principal, a hierarchy, overlapping groups, a peer network, a market, or another selected shape. Teams, managers, queues, reviews, and workflows are useful package semantics, not universal runtime requirements.
  • A company substrateCompany identity, desired configuration, owner-qualified state, selected packages, authority, and evidence can persist beyond any one execution or provider session. No single store owns all of it.
  • GovernedControlled operations use explicit owner-qualified authority and limits. Companies may add budgets, approvals, escalation, and other governance through selected owners without making those semantics kernel nouns.
  • Outcome-pressuredAn exocorp must have contact with external reality: customers, users, markets, operators, invoices, competitors, regulators, production systems, resource constraints. Without external pressure, the company optimizes its own stories.

A company that can change its own operating matter

The old company changed itself by hiring, training, restructuring, buying tools, writing process, changing incentives, and accumulating culture. Those mechanisms remain relevant, but an exocorp gains additional surfaces of change: it can revise its operating graph, update principal contributions, acquire and select packages, change component configuration, and replace execution bindings.

This makes self-modification both more available and more dangerous. Capability and topology changes should be evaluated against outcomes. The canonical software-company template demonstrates one optional evidence discipline through labs; another company may select a different evaluation package.

Next