Files
openyield/docs/freeholders/partner-spectrum.md
T
cloudinit-bot 2ef3f2e39f docs(P03): complete freeholders docs + reference phase — REQ-027 complete
P3 complete. 8 docs/freeholders/ pages (signals, standing, stands-guilds,
councils-voice, bonds, partner-spectrum, anchor-preview, index) + 2
docs/reference/ pages (architecture, components). Docs firewall green
across all 26 docs pages. Full docs deliverable (README + mkdocs.yml +
26-page site) complete — REQ-027 complete.

---ci---
project: oy
phase: 3
milestone: v0.3
status: complete
tag_base: v0.2.x
phase_role: execution
requirements:
  covered: [REQ-027]
  partial: []
---/ci---
2026-08-17 22:17:07 +00:00

2.2 KiB

Partner Spectrum

OpenYield defines a four-tier Partner Spectrum (REQ-018, vision §13): Op, Master Op, Pier, and Anchor. Partners are the external actors a Freeholder interacts with through the mesh — service operators, route providers, and institutional bridges. The four tiers are locked as the PartnerTier enum in x/partner (exactly 4, regression-tested).

The four tiers

  • Op — a service operator. Runs a service a Holder uses through a Window (e.g., a Maps provider). The lightest tier.
  • Master Op — a senior operator. Coordinates multiple Ops or runs a higher-trust service. "Op" is the safe short form; the full word is not used as a standalone term.
  • Pier — a routing Partner. Connects the mesh to external venues (e.g., a DEX or an off-mesh service) and sources Forex rates. Piers route; they do not custody Holder value.
  • Anchor — the first institutional Partner tier. Carries a credential (jurisdiction, custody provider, attestations). See Anchor Preview for what is coming in v0.3 P4.

How Freeholders relate to Partners

A Freeholder authorizes a Partner to act on their behalf through a scoped, time-limited, revocable Window — never by handing over custody. The Partner holds a credential, not the Holder's Stash. A Partner's Standing is visible so a Freeholder can choose an operator with a real history over a freshly-spun-up alternative (see Maps & Pay).

Partner status

Each Partner has a status (locked PartnerStatus enum in x/partner): Pending → Active, with Suspended and Revoked as the governance paths. The Mesh Council can suspend or revoke a Partner. The four tiers and the status enum are unchanged by v0.3 — v0.3 only extends x/partner with the Anchor credential shape (REQ-023), not a new tier.

See Storage Pools for why the mesh says "Holder" and "Reach" rather than the legacy custodial words, and Bonds for the coupon market a Partner may route to.