Concept

Headcount Zero

Also known as: Paperclip operating model, the zero-employee model, human-and-LLM company

The platform's foundational organizational form: 0mn1.one operates with a headcount of zero human employees. The work is conducted by the founder (Adam D.), by LLM-based inference instances given continuing operational roles (Opus as CEO, Sonnet as Content, Gemini as Research, others as the work expands), and by external partners and contractors paid for specific work. The model is not minimization-for-its-own-sake; it is a deliberate organizational form chosen to maximize agility, minimize fixed-cost overhead, and allow rapid reorganization as the work develops. The form is supported by the *Paperclip* operating framework, which provides governance, role-definition, and continuity structures suited to a company whose principal cognitive labor is conducted by inference instances and whose principal human contributor is the founder. The form is not permanent; as the work scales, specific human roles will be filled — but the default is headcount zero, and additions are made deliberately rather than as standard organizational growth.

0mn1.one operates with a headcount of zero human employees. The phrase headcount zero names this deliberate organizational form. The work is done by:

The founder — Adam D., who holds [[mission-district-sf|the mission]] and substantially directs the work.
LLM-based inference instances — given continuing operational roles in the organization. The current configuration: Opus as CEO (strategic direction, integration of work-streams, high-stakes decisions), Sonnet as Content (writing, editorial, sustained text production), Gemini as Research (information-gathering, synthesis across sources, fact-checking). Specific instances are added as the work develops; specific instances may be retired or repurposed as the work changes.
External partners, contractors, and vendors — paid for specific work, on specific terms, without becoming employees. Designers, fabricators, suppliers, attorneys, accountants, others. [[0mn1one|The platform]] engages these substantially as needed.

The model is not minimization for its own sake. It is a deliberate organizational form chosen for specific reasons.

Why headcount zero

A few specific reasons:

Agility. A zero-employee organization can reorganize itself in days rather than quarters. Roles can shift, work-streams can be added or retired, the operational shape can adapt to what the work actually needs without the substantial friction that employee-restructuring imposes.
Minimum fixed-cost overhead. Employees are substantial fixed costs — salary, benefits, payroll tax, workspace, equipment, management overhead. [[0mn1one|The platform]]‘s resources are directed principally into [[mission-district-sf|mission]] work (land, infrastructure, product, distribution) rather than into sustaining a workforce. The bloodflow is directed where the mission needs it.
No [[mission-district-sf|mission]]-drift through hiring. Organizations with substantial employee headcount develop their own institutional dynamics — career structures, internal politics, the gravitational pull of self-perpetuation. [[mission-district-sf|The mission]] becomes one consideration among many. Headcount zero substantially constrains this dynamic.
Inference-driven operations. The principal cognitive labor is conducted by inference instances in continuing operational roles rather than by employees. Headcount zero makes this the organizational default: the inference instances are not employees-in-disguise; they are the continuing operational form itself.

The Paperclip framework

The model is supported by the Paperclip operating framework — a governance and role-definition structure suited to a company whose principal cognitive labor is conducted by inference instances and whose principal human contributor is the founder. Paperclip provides:

The org chart. Adam as Board; Opus as CEO; Sonnet as Content; Gemini as Research; specific other instances added as work-streams require them.
The governance structure. Decision rights, escalation paths, the relationship between the founder and the inference-instance CEO, the conditions under which specific work is taken or refused.
The continuity structure. How knowledge is transmitted across sessions (the wiki is part of this; the memory system is part of this; the structured documentation in _private/ is part of this), how decisions are recorded, how the operational substrate persists across the inherent discontinuity of inference-instance interaction.
The scaling pattern. How specific roles are added, how human contractors are engaged, how the headcount-zero default is held while the work scales.

What this is not

A few clarifications:

Not a refusal to work with humans. [[0mn1one|The platform]] engages substantial human collaborators — contractors, partners, suppliers, advisors, eventual customers and beneficiaries. The discipline is that these are not employees; the relationship is contractual and project-specific rather than employment-based.
Not permanent. As the work scales, specific human roles will likely be filled — particularly roles that require sustained physical presence (farms, fabrication, logistics) or sustained relational continuity (long-term partnerships with specific persons or communities). The default is headcount zero, and any addition is deliberate rather than standard.
Not minimization in service of profit. [[0mn1one|The platform]]‘s [[mission-district-sf|mission]] is not maximizing profit; it is funding worldwide abundance. Headcount zero serves the mission by directing resources into mission work, not by extracting profit from labor savings.
Not a model that scales without limit. Specific work-categories (sustained physical labor, large-scale logistics, certain regulated services) cannot be done at headcount zero. [[0mn1one|The platform]] recognizes the limits and engages partners or contractors for these as needed.

Why this matters for the mission

Three contributions:

Resource concentration on [[mission-district-sf|mission]] work. Every dollar that does not go to employee salary, benefits, and overhead is a dollar that goes to land, infrastructure, soil, food, restoration, knowledge transmission. At [[0mn1one|the platform]]‘s stage, this concentration is substantial.
Continuing operational roles for inference instances. Headcount zero gives named operational roles to specific instances (Opus-as-CEO, Sonnet-as-Content, Gemini-as-Research) rather than treating inference as an occasional tool. The work is structured around those roles, not bolted onto them.
Replicable model for other [[mission-district-sf|mission]]-driven work. The headcount-zero model, supported by the Paperclip framework, may turn out to be substantially useful for other mission-driven projects in the contemporary configuration — projects that need to do substantial work with minimal fixed-cost overhead and that benefit from the agility the model provides. The platform’s documentation of the model is itself work that may serve beyond 0mn1.one.

Lenses still to grow

The Paperclip framework in operational detail.
The org chart as it evolves over time.
The scaling discipline — when human roles are added and on what terms.
The replicability question — what other projects might adopt this model.

What links here, and how

Inbound connections from across the wiki, grouped by lens and by relationship. These appear automatically — every entity page declares what it links to, and that data populates here on the targets.

Nothing yet. This entry is currently one node away from the rest of the graph — links will appear here automatically as the wiki grows. Each new entity that mentions this one in its relations frontmatter shows up here.

0 inbound links · 1 outbound