Zero Employee Organizations

Read the doctrine  ·  Install the governance plane  ·  Learn with Prof Rod

Zero Employee is the open-source doctrine, community, and infrastructure for building Zero Employee Organizations (ZEOs): organizations in which one human can direct fleets of AI agents while retaining authority, accountability, and ownership of the result.

The name is not a promise to remove people. It names a design problem:

If agents perform the work, how do we define scope, assign authority, control execution, account for cost, verify results, and preserve human responsibility?

This organization builds the public infrastructure needed to answer that question with working systems rather than slogans.

pip install zero-employee

Zero Employee governs. Sovereign Agent executes. Runtime capacity never creates organizational authority.

flowchart LR
    H["Human principal"] -->|intent and authority| G["Zero Employee governance"]
    G -->|bounded request| E["Sovereign Agent execution"]
    E -->|evidence and receipts| G
    G -->|decision surface| H

The governance plane decides what may happen. The execution plane determines how permitted work runs. Evidence returns across the same boundary; authority does not travel in the opposite direction.

An agent's technical ability to perform an action does not grant organizational permission to perform it.

Every meaningful delegation needs a defined objective, inputs, constraints, acceptance criteria, budget, and escalation path.

Prompts are advisory. Organizational constraints belong in schemas, validators, capability manifests, policy engines, and permission boundaries.

Sessions, requests, tool calls, artifacts, approvals, failures, and results must survive the process that produced them.

“The agent ran” is not the same as “the work is correct.” Claims of completion require receipts that can be independently checked.

Agents can receive bounded authority. They cannot absorb the operator's accountability for irreversible consequences.

A project belongs in zeroemployeeorg when it provides reusable:

• organizational doctrine or schemas
• governance, validation, or accounting infrastructure
• agent execution infrastructure
• typed operational capabilities
• reference implementations for building or operating a ZEO

Something does not belong here merely because Rod or Prof Rod uses it. Educational artifacts live under profrodai; personal work lives with Rod Rivera.

We welcome implementation improvements, tests, documentation, reference integrations, and architectural criticism.

Before contributing:

1. Read the target repository's CONTRIBUTING.md and architecture documentation.
2. Open an issue for changes that alter public contracts or governance semantics.
3. Keep policy deterministic and execution evidence inspectable.
4. Include tests and a clear receipt showing what changed and how it was verified.

Rod originates and operates. Zero Employee codifies and ships. Prof Rod teaches and dramatizes.