MODELED · COUNSEL-GATED · NOT AN OFFER. sOpusAI is not available. This page describes proposed mechanics for internal review only. Nothing here is an offer to sell or solicitation to buy a security, or investment advice. Any future offering would occur only under Reg D with a PPM and Florida counsel sign-off.

OpusAI

The Yield Unit

sOpusAI

Modeled · Counsel-gated · Not an offer

A structural explanation of the proposed mechanics behind sOpusAI — the yield-bearing claim on the protocol's credit book. This is not an offering. It describes how the instrument would work once counsel approves and the machinery exists.

01

Two units, not one

The protocol separates stability from yield through two distinct units:

  • Stable entry layer — USDC / PYUSD. The liquid dollar rail into and out of the protocol. OpusAI does not mint its own stablecoin. Holding it earns no yield; it is the unit of account and the exit path.
  • sOpusAI — the yield-bearing claim. You obtain it by depositing the stable unit. Its value is not fixed 1:1 — it appreciates as the credit book earns.

The nervous holder stays in the stable unit; the yield-seeker moves into sOpusAI. The holder chooses.

02

Yield accrues as a rising value, not a payout

sOpusAI captures income through a rising exchange rate against the stable unit — there is no dividend, no claim button, no manual step. Holding it is the entire action. When redeemed, the holder receives more of the stable unit than they put in, reflecting accrued yield.

Value is always read through the vault's convert-to-assets logic — never by assuming one share equals one dollar.

03

Two sources of yield — one of them a floor

sOpusAI earns from two places:

  • Wrapping interest — interest on credit the protocol wraps against verifiable, income-producing machine-economy cashflows (Genesis II). This is the variable, thesis-driven layer.
  • T-bill / reserve floor — capital not currently deployed into credit sits in short-term Treasury-bill-yielding reserves. This creates a yield floor and minimizes cash drag between deposits and wraps.

Even when capital is not lent out, it earns the reserve rate. No specific APR is displayed — mechanics only, until counsel and a real book exist.

04

Collateral — real cashflow, not emissions

The yield is backed by credit against verifiable machine-economy cashflows — broader than GPUs alone: compute, storage, bandwidth; DePIN operators; eventually agent working capital.

Credit rule: only wrap against verifiable, income-producing collateral; non-recourse to the collateral, springing recourse to the operator only for fraud.

This is interest from real borrowers — not token-emission yield, not inflation.

05

Redemptions — orderly by design

Redemption discipline is a feature, not a limitation:

  • Redemptions process on a fixed periodic epoch — [EPOCH: e.g. 30 days] — to be set by counsel — a protocol-wide window, not a per-user countdown.
  • Because credit positions are illiquid and amortizing, redemptions are served from available reserves and scheduled repayments — the protocol does not prematurely terminate credit positions to satisfy withdrawals. This protects the holders who stay.
  • The stable reserve buffer (USDC operational + T-bill deep reserve) services redemptions in the ordinary course without forcing a fire-sale of the book.
06

What protects the holder

  • Holders bear credit risk directly. sOpusAI holders are exposed to the credit risk of the book — there is no first-loss treasury between them and credit losses. OpusCapital is the protocol treasury, not a backstop for sOpusAI holders.
  • Priority of claims. sOpusAI is the senior claim on the credit pool. Losses hit Credit Equity — the protocol’s own money in the book, which belongs to OpusAIET — first, then unit holders. Otherwise "no first-loss treasury" becomes "no priority either," and the instrument isn't really debt-like at all.
  • No cross-collateralization. A treasury drawdown never reaches sOpusAI, and a credit-book loss never reaches OpusAIT. Each instrument’s risk lives in one pool.
  • The reserve floor. Stable, non-volatile ballast that does not swing with crypto.
  • Verification gate. Unverifiable cashflow is not eligible collateral.
07

Lenders, participants, owners — three instruments, two pools

Three separate instruments, three separate claims, three separate securities. Two fenced pools and one residual:

  • sOpusAI — debt-like. A lender's claim. A stake in the credit book's NAV only. Deposit, get units, NAV rises with yield, redeem. No ownership of OpusAI, no governance, no share of Research's trading or Capital's crypto appreciation. If the book returns 6%, holders get 6% — capped, with credit risk borne directly. Closer to a note or fund interest.
  • OpusAIT — a participation unit. Neither debt nor equity: a pro-rata share of the capital pool — OpusCapital’s treasury plus OpusResearch’s book — uncapped both ways, no governance. It ranks pari passu with the protocol’s own retained units in those two organs; there is nothing in that pool to be senior to, because the capital organs take no lenders. It never touches the credit book.
  • OpusAIET — equity-like. An ownership claim. The residual on everything: Credit Equity, settlement fees, Intelligence revenue, cash reserves, and the protocol’s retained share of the capital pool. Uncapped upside, and last in line in both pools. Equity in the LLC.

Different disclosure, different structure, different counsel questions. OpusAIET absorbs losses first everywhere — equity eats before any unit holder in either pool.

Note on NAV: just as sOpusAI principal is netted out of Credit Equity, OpusAIT units are netted out of the Treasury and Research Book before OpusAIET’s claim is computed. Nothing is counted twice.

All three instruments are modeled and counsel-gated; none is offered here.