Current operating condition
This is a dated receiving-side observation, not a promise that source code is live. As of 2026-10-03T21:22:01.708Z, the Tidepool runtime is installed-requires-standing, the protocol-clerk seat is vacant, and the first admission → vote → cycle → disclosure loop is unreceived.
Current blocker: Do not seat the prior nine-verb Protocol Clerk. First separate participant-authored admission/sponsorship/vote intent from clerk execution (this source hardening begins that split), then make tally close, total-yield split, and public disclosure depend on admitted close/reconciliation evidence before seating a narrow executor.
The nine protocol operations may exist while remaining unavailable to ordinary Turntide/Board offices. Operation availability is execution capability, not permission to invent a member, vote, weight, yield receipt, witness, or settlement.
Five governance lanes
Tidepool financial governance is separate from Turntide-wide DAO standing. Joining Discord or holding Turntide standing does not grant Tidepool membership or financial authority.
Become a Tidepool member
How do I join Tidepool?
What a participant can do
- submit first-stage public admission intake
- supply Membership v2 settlement destinations
- supply a member-controlled ledger witness descriptor
- supply one supported admission witness when the chosen path requires it
States
- intake-recorded — The public site recorded a request. This is not membership.
- operation-ready — The required identity resources and witnesses are available to the authoritative admission operation.
- admitted — The authoritative Tidepool state contains the admitted member and an append-only receipt.
- refused-or-unavailable — Admission did not occur; the exact missing or invalid authority/witness/state remains explicit.
Authoritative operation(s): admit-pool-member
Authority boundary: The generic MetroPlat runtime does not expose unwitnessed bootstrap admission. A witnessed admission path must be invoked by the subject that owns the witness authority (sponsor, admitted enterprise, or verified Discord subject); a Protocol Clerk cannot manufacture the applicant's admission intent.
Zelo: Explain the path, distinguish intake from admission, identify missing resources, and route; never admit or manufacture a witness.
Put an enterprise on the distribution roster
How does an enterprise become eligible to receive the enterprise distribution?
What a participant can do
- propose a sponsored enterprise with offer and reporting commitment
- participate in the enterprise admission vote when an admitted member has the required voting weight
States
- pending — A sponsored enterprise proposal exists but is not yet on the admitted distribution roster.
- admitted — The weighted admission vote closed with the required quorum and majority and the enterprise is on the roster.
- retired — The enterprise is no longer on the admitted roster after the applicable retirement process.
Authoritative operation(s): admit-member-enterprise, admit-enterprise-vote
Vote rule: Enterprise admission is not a staff choice: the pending proposal closes through the member vote path; the protocol clerk records the already-authorized outcome.
Authority boundary: Sponsored enterprise proposal intent belongs to the sponsor enterprise; the runtime binds the invoking subject to sponsorEnterprise and refuses unsponsored first-roster bootstrap. Closing a passed admission vote is a separate protocol step.
Zelo: Explain pending/admitted/retired state and route the participant to the Tidepool member-governance process; never treat Turntide discussion as the Tidepool vote.
Vote the member-governed half of the distributable yield
How does my Tidepool vote affect a cycle?
What a participant can do
- cast one distribution vote per cycle when admitted and eligible
- allocate their fixed voting weight across admitted enterprises
States
- open-for-member-intent — Eligible admitted members may record their one vote for the named cycle.
- tallied-weighted — At least three nonzero-weight voters participated and weighted enterprise shares are authoritative.
- tallied-equal-fallback — Fewer than three nonzero-weight voters participated; no weighted shares control the voted portion.
Authoritative operation(s): record-distribution-vote, tally-cycle-votes
Voting power: A member's vote weight is their matched-tally count measured at the prior cycle reference point; deposit balance and Turntide standing do not determine the weight.
Quorum: At least three distinct nonzero-weight voters are required for weighted allocation. Below quorum, the voted portion falls back to equal allocation.
Authority boundary: The runtime binds the invoking subject to memberAccount before recording the vote. Zelo, Turntide governance, and a generic Protocol Clerk cannot cast or replay a member's choice.
Zelo: Explain eligibility, weight, quorum, and fallback; route actual voting to Tidepool's authorized operation when received.
Close and settle a yield cycle
What has to happen before a Tidepool cycle is really closed?
What a participant can do
- inspect the public rules and later public receipt
- supply their own ledger witness when reconciliation requires it
- contest contradictory or missing receipt evidence through the applicable receipt process
Authoritative operation(s): tally-cycle-votes, derive-cycle-split, derive-set-of-pool-cycle-transactions, reconcile-pool-books
Split: Directed yield splits 20% reserve / 30% tally-credit float / 50% distributable. The distributable bucket is 50% equal across admitted enterprises and 50% governed by the cycle vote, subject to equal fallback below quorum.
Receiving: A derived split is not by itself a settled cycle. Directed-yield receipts must reconcile to the split, and member/pool books remain agreed, mismatch, posted-only, asserted-only, or unavailable rather than silently settling disagreement.
Authority boundary: The protocol clerk may execute these transitions only from already-authorized state and real witnesses; it may not invent yield, votes, ledger evidence, or settlement.
Zelo: Explain which close stage has been received and which witness/receipt is still missing; do not call a fixture or source-level result an operating cycle.
Publish a cycle receipt
How do I know what Tidepool actually did?
What a participant can do
- read the received public cycle disclosure
- compare the public roster and allocations across cycles
- use named falsifiers and provenance to challenge an inconsistent claim
Authoritative operation(s): publish-cycle-disclosure
Append-only rule: The same cycle cannot be silently republished with different content; a conflict must be reconciled at the producing authority.
Authority boundary: The public site projects an already-produced disclosure and receipt. It is never the financial control plane.
Zelo: Explain the latest received disclosure and its provenance, or say explicitly that no public receipt has been received.