That distinction is not cosmetic. It is central to what OLTIP Protocol is.
Much of modern financial distribution is built around products. Products have issuers, wrappers, terms, distribution channels, and local regulatory classifications. They are manufactured, sold, and administered within the perimeter of a given institution. OLTIP Protocol is intended to operate at a different level. It does not prescribe a single wrapper, jurisdiction, or provider structure. It defines a common framework that multiple institutions may implement, provided that the implementation preserves the framework's structural logic.
In that sense, OLTIP Protocol is closer to a protocol than to a product.
A product answers questions such as which vehicle is used, which institution distributes it, and what local disclosures apply. OLTIP Protocol is concerned with the deeper structural layer beneath those choices: the rule-based architecture that governs payout logic, capital-preservation discipline, cost limits, implementation boundaries, and governance requirements.
This is why OLTIP Protocol should not be understood as a branded investment wrapper waiting to be launched by one provider. Its intended form is institutional implementation. Under an OLTIP Protocol-compatible structure, the implementing institution remains responsible for the local execution — the legal wrapper, custody, reporting, compliance, participant communication, and operational administration. The framework does not displace those responsibilities. It defines the structural standard within which they are carried out.
Without that boundary, a framework can easily be mistaken for a product concept. The result is predictable confusion: people ask whether OLTIP Protocol is a fund, an annuity, an insurance contract, a platform, or a retirement account. The answer is that OLTIP Protocol is not identical with any one of those forms.
- It is not an annuity
- It does not guarantee income
- It does not pool mortality risk
- It does not transfer investment risk from participant to provider
- It does not depend on discretionary manager judgment in core payout logic
- It does not require one institution to hold all implementations on its own balance sheet
OLTIP Protocol may be implemented through regulated wrappers that take those forms locally, but it is not itself identical with any one of them. Treating it as a structural framework rather than a product concept also preserves scalability: different institutions in different markets can implement compatible versions under different local conditions while still preserving a shared identity.
That is one of the main reasons governance matters so much. A protocol without governance is just a vocabulary. A protocol with stewardship, certification discipline, version control, and implementation boundaries can become something more durable: an institutional standard. OLTIP Protocol is intended to develop in that direction.
Once a framework becomes loose enough to absorb discretionary modifications, marketing reinterpretation, or economically extractive redesign, it stops being the same framework in any meaningful sense. This is why OLTIP Protocol places so much emphasis on protocol integrity. Institutions may implement the framework locally, but not rewrite its structural logic at will.
The phrase "protocol, not product" is not branding language. It is a statement about institutional level.
OLTIP Protocol is intended to sit above the level of any one wrapper and below the level of abstract philosophy — concrete enough to govern implementation, general enough to be carried across jurisdictions and institutions. That is what gives it the possibility of becoming federated rather than founder-bound, and institutional rather than merely conceptual.
When evaluating OLTIP Protocol, the first question should not be, "What product is this?" The better question is: "What kind of institutional framework is this, and what would compliant implementation require?"
That is the level at which OLTIP Protocol is meant to be understood.