No Exchange or WN Coin surface should be read as approved for value transfer, liquidity, custody, sale, or secondary trading.
Launch language needs launch evidence.
This public gate defines the source record White Noise must retain before WN Exchange or WN Coin language can move beyond preview, prototype, or review-gated status into any live market, token sale, custody, liquidity, settlement, creator payout, or launch-readiness claim.
One launch action, one source record.
The existing public posture stays unchanged: WN Exchange is a preview catalog and WN Coin is a concept/prototype/reservation-review surface. This gate defines what must exist before any narrower launch action earns warmer language.
The record must name the exact action, terms, rights, wallet/mint state, payment path, support route, rollback owner, and board decision.
Preview, provenance, curation, and member preparation language remains acceptable; market and sale language stays blocked.
Draft evidence, prototypes, local records, or owner intent do not become launch approval without the board decision record.
Launch scope and terms
Define the exact requested surface and participant boundary, including refund posture, eligibility, prohibited claims, and no-investment language.
Rights and provenance
Retain source asset rights, generation provenance, metadata schema, attribution, takedown route, and marketplace/resale permission state.
Wallet, mint, and chain state
Separate prototype, disabled, test, audit, deployment, pause, and release states before any wallet, mint, transfer, bridge, or custody language.
Payment and settlement ownership
Record payment processor path, treasury role, settlement owner, refund owner, tax/reconciliation owner, and blocked value-transfer state.
Compliance and communications
Capture offering or non-offering status, counsel status where applicable, eligibility posture, KYC/KYB/AML state, and copy review.
Support, incident, and board decision
Name support routes, abuse handling, takedown authority, incident log, rollback owner, stop condition, and dated board decision.
Ten gates before launch language changes.
A private launch record can support a bounded public summary only when scope, evidence, owners, counsel status, copy boundaries, rollback controls, and board approval are all explicit.
Scope, terms, rights
Lock the launch action, participant boundary, rights/provenance record, metadata state, attribution, and takedown route.
Wallet, payment, compliance, chain
Separate wallet, mint, payment, settlement, offering, KYC/KYB/AML, contract, chain, audit, and security states.
Support, language, decision
Assign support and rollback owners, clear public language, and record the dated board decision naming what remains blocked.
Publish a narrow launch summary.
- Dated review window, approved or blocked launch action, and preview/catalog state.
- Evidence categories reviewed, owner-role summary, counsel-status category where appropriate, and unresolved gap categories.
- Board decision date, rollback owner role, and next review trigger.
Do not publish sensitive or unsupported claims.
- No private wallet addresses, keys, admin controls, contract secrets, payment account details, buyer records, tax records, or support records.
- No legal conclusions, securities conclusions, regulatory clearance claims, investment advice, return, yield, liquidity, trading, or price-performance language.
- No sale, allocation, entitlement, token delivery, custody, settlement, live-market, or launch-approval claims without accepted evidence and board decision.
Start with a preview-only handoff.
The lowest-risk candidate is usually a preview-only Exchange collection handoff with no payment, no mint, no token transfer, no custody, no allocation promise, and no liquidity language.