The Capability Boundary of a Single OPC#
An OPC can be powerful, yet it remains constrained by the following:
- distribution;
- credibility;
- legal capacity;
- local relationships;
- capital;
- specialized human expertise;
- customer access.
These seven items share a common feature: none of them can be closed by an individual simply trying harder. Each requires either scale, or licensing, or a long accumulation of standing in a particular geographic and social position. This is precisely the long-standing rationale for the traditional company β the company is a container for acquiring these resources.
The problem is that stuffing every individual back into a traditional company just to obtain these resources comes at the cost of abandoning the OPC's core advantages: concentrated judgment, short decision chains, and the unity of execution and responsibility.
An OPC Alliance can provide shared infrastructure without forcing every member into a traditional company structure.
This is the starting point of the OPC Infrastructure concept: detaching "scale" from "organizational form" and turning it into a pluggable layer.
The Trust and Economic Infrastructure Layer#
In the OPC's six-layer stack, the sixth layer is Trust and Economic Infrastructure. It carries what a single OPC cannot invent on its own and must instead be supplied by an external system:
- identity;
- contracts;
- contribution records;
- payments;
- revenue sharing;
- reputation;
- compliance;
- audit;
- ownership.
The first five layers β Person, Context, Goal System, Agent Team, Human Network β can all be configured and run by one person. The sixth cannot. Identity only counts as identity once others recognize it; a contract needs a counterparty and an enforcement mechanism; reputation only means something once it accumulates across parties. The sixth layer is inherently shared, and therefore inherently infrastructure.
The Ten Layers of the Alliance#
A possible layered structure for the OPC Alliance is as follows. Each layer is a component that can stand on its own or be layered on progressively.
Identity Layer#
Verified people and entities. This is the precondition for every layer that follows β if "who is who" cannot be confirmed, capability, reputation, and contribution all become impossible to attribute.
Capability Graph#
Who can do what, in which market, and under what conditions. Note the latter two items in particular: capability is not an abstract label β a description of capability detached from market and conditions is not actionable in collaboration.
Trust Graph#
Track record, referrals, commitments, and outcomes. The difference between the trust graph and the capability graph is that the former records "a history of following through," while the latter records "a declaration of what can be done."
Opportunity Network#
Shared deal flow, projects, and market access. This layer directly addresses a single OPC's shortfalls in distribution and customer access.
Collaboration Protocol#
Clear roles, approval points, and deliverables. Collaboration without a protocol degrades into personal favor-trading, which cannot scale and cannot be held accountable when something goes wrong.
Contribution Ledger#
Records who contributed the Goal, relationships, capital, expertise, execution, and risk. In a traditional company, these six types of contribution are crudely converted into salary, rank, and equity; in an alliance structure they must be recorded separately, because distribution is based on them.
Economic Settlement#
Payments, revenue splits, commissions, and ownership agreements. This layer converts the records in the contribution ledger into cash and equity.
Shared Agent Infrastructure#
Reusable workflows, tools, models, and knowledge. It is pure waste for a single OPC to repeatedly rebuild the same Agent capability; once shared, marginal cost approaches zero.
Shared Services#
Legal, finance, compliance, design, operations, and localization. This layer addresses the shortfalls in legal capacity and specialized human expertise.
Capital Layer#
Financing structures for qualified OPCs and Goal-driven projects β a direction for future experimentation.
To be clear: the capital layer and incubation are directions for future experimentation. They do not constitute a current offer of investment, nor any commitment to provide services.
The OPC Network as a New Organizational Layer#
One possible evolutionary path:
Person
β OPC
β OPC Network
β Goal-driven Institution
The key to this path is that the network does not need to become a traditional large company.
It can remain modular, expressed through six characteristics:
- small stable cores;
- dynamic project teams;
- shared protocols;
- portable reputation;
- reusable Agent infrastructure;
- outcome-based economics.
Together, these six describe a way of scaling that differs from the traditional company: a traditional company scales by adding headcount and layers, at the cost of longer decision chains and diluted responsibility; a modular network scales through shared protocols and reusable infrastructure β headcount need not grow, the core stays stable, and scale shows up instead in the dynamic recombination of project teams.
Portable reputation is the most easily underestimated of the six. In a traditional company, most of a person's reputation is absorbed by the organization and must be rebuilt after leaving; in a network structure, reputation is recorded on the trust graph, belongs to the individual, and accumulates continuously across projects and across alliance members. This is the precondition for an OPC to keep winning opportunities without the shell of a company around it.