YES Release Bucket Policy

YES Release Bucket Policy

This policy explains how this YES Release bucket should be read.

This bucket is part of the YES Release record. It exists to show one category of work, routing, or support connected to the release of YES and the continued buildout of Yokefellow. It should be read as a public use-of-proceeds surface, not as a separate promise beyond the purpose stated on the bucket page.

The goal is simple: keep the release structure readable. The bucket should show what this category is for, what kind of work it supports, and what important updates or receipts are posted as funds are used, moved, reserved, or reclassified.

What this bucket coversCopy link

This bucket covers the purpose stated on its public page.

Depending on the bucket, that purpose may include operating support, legal and professional work, growth and media, reserve planning, capital equipment, HQ preparation, platform buildout, or another stated YES Release category.

The bucket name, description, constraints, updates, and receipts should be read together. No single label should be read more broadly than the actual stated purpose of the bucket.

How records will be shownCopy link

Yokefellow may post updates, notes, receipts, or supporting records when there is a material development connected to this bucket.

That may include:

• planned use of funds
• completed work
• material expenses
• routing between release buckets
• changes in priority
• closeout notes
• supporting proof where appropriate

Not every small action will require a separate post. The purpose is to keep the material record readable without turning the bucket into noisy bookkeeping.

Routing and adjustmentsCopy link

The YES Release is an early operating structure. Some costs, timing, vendor needs, legal needs, buildout plans, or operating priorities may change as the release moves forward.

Funds assigned to this category may be used, held, routed, converted, or reallocated in a way that fits the stated purpose of the bucket and the broader YES Release structure. If a change is material, Yokefellow should post an update so the public record remains understandable.

This bucket should not be read as a guarantee that every dollar or token assigned here will remain permanently parked in this exact bucket. It should be read as a record surface for the stated release category.

What this bucket does not meanCopy link

This bucket does not create ownership in Yokefellow.

It does not create equity, profit rights, revenue share, voting control, repayment rights, or any guarantee of future value.

It does not guarantee that YES will increase in price, remain liquid, keep a stable market, or be available for sale or purchase on any particular terms.

It does not guarantee that every plan described near this bucket will happen on a fixed timeline.

It does not replace the Terms of Service, Risk Disclosures, YES Tokenomics Paper, sale terms, or any legally required disclosures that apply to the broader YES Release.

Market and timing limitsCopy link

YES is connected to a live economic layer. Market conditions, liquidity, pricing, timing, gas costs, service availability, and platform sync can affect what users see or what actions are possible at a given time.

Bucket records may also update after the underlying action, expense, transaction, or routing decision. A delayed update does not automatically mean the underlying record is invalid, but users should treat the full record as something that may include onchain activity, offchain updates, receipts, and later reconciliation.

Reading ruleCopy link

Read this bucket as one part of the YES Release record.

The public page states the purpose. Updates explain movement over time. Receipts or proof support material follow-through when appropriate. Later closeout or reconciliation should explain what happened if the bucket reaches a meaningful end point or is replaced by a stronger structure.

The standard is not perfection. The standard is readable follow-through.