How $GFOF works as an optional way to pay for Dossier (Operation 02). A payment option, never a gate. Published before the payment flow is built — spec before code. Verify everything against the corrections log.
$GFOF is an optional way to pay for a Dossier subscription. It is not a gate: fiat is always available, nothing is locked behind the token, and you never have to hold or buy $GFOF to use any tier. It is not an investment, pays no yield, and carries no promise of price appreciation. This is a design specification — the payment flow it describes is published before it is built.
This specification defines how the $GFOF token functions as an optional payment method for the Dossier intelligence product — a concrete, non-speculative reason to hold and use the token: paying for the product.
In scope: paying for Dossier with $GFOF; how received $GFOF is handled; the framing rules that keep this utility rather than investment. Out of scope: yield, lending, staking-for-return, hold-to-access gating (Section 04), and any claim that $GFOF will appreciate (Section 08).
Value through use, not through promised returns. Spending a token for a service is consumptive utility. Paying a holder a return for holding is the category currently unsettled in US law — the Digital Asset Market Clarity Act was not enacted as of June 2026, and yield was its most contested provision. This specification stays on the utility side of that line by design. Nothing here is legal advice.
The single mechanism in this spec: the token is spent to buy the product.
Gating a tier behind holding $GFOF is not part of this spec and will not be built. Dossier is pay-for-what-you-need with no token-gate. Accepting $GFOF as a payment method gates nothing — fiat is always available and no tier requires the token. Any future reconsideration of holding-based access would require its own specification and a corrections-log entry.
Subscription value is set in USD so product economics do not swing with the token. The $GFOF amount due is computed at checkout from a single, named price source — DexScreener (pair 3y4NNTfU3y1KzCChAJyQUv5RmX3zuZNxVbXer2vjASGE) — recorded here so the method is auditable.
$GFOF received this way is Dossier revenue. It flows through the existing routing commitment recorded in corrections #011: staged 25% rising to 50% into $GFOF/SOL Raydium liquidity, quarterly, with on-chain proof. The remainder routes to operating treasury. There is no burn mechanism in this version. $GFOF-denominated subscription revenue is counted inside the #011 net-revenue base, so there is one routing rule, not two. The receiving wallet is a dedicated subscription wallet, separate from general treasury, with its address published on creation. Routing is described as plumbing, never as a price-support action.
Set as of this version. Publication is the act that makes them live.
These appear, in substance, wherever this mechanism is described publicly:
The Digital Asset Market Clarity Act was not law as of June 17, 2026; the security / commodity line it would draw is not yet in force, and yield mechanics were its most contested element. This spec is designed to sit on the utility / consumption side of that uncertainty rather than to test it. This document is a design artifact, not legal advice; counsel reviews Sections 03–08 before any public launch.
This is v0.2 — parameters set, ready to publish. Publication is the act that makes these parameters live. Post-publication parameter changes are appended to the corrections log, never edited in place. Sequence from here: publish → counsel review of Sections 03–08 → announce → build the payment flow.