Q markQUADCommunications

Communications Guardrails

Public copy should make QUAD easier to inspect without selling access, implying rewards, inflating team posture, or replacing proof with excitement.

Public UpdatesUsage EvidenceSecurityBoundary

Access And Reward Boundaries

These rules apply to public testnet copy, community posts, status notes, and onboarding paths.

No pay-to-play testnet access

Public testnet use must not require real-money payment. Testnet funds are test tokens only.

No guaranteed future rewards

No real-money payment, faucet use, Discord activity, validator interest, bug report, or docs contribution creates reward eligibility, allocation, ownership, governance rights, leverage, or future entitlement.

No referral or prize signal

Referral farming, prize campaigns, claim traffic, or speculative engagement cannot be presented as product-market fit or public traction.

No sale framing

Public pages are orientation, evidence, and observability surfaces. They are not token-sale, airdrop, exchange, custody, or investment pages.

Update Discipline

Silence should not become the public posture when a visible surface is blocked, stale, or changing.

  • Meaningful updates beat hype. Updates should name the affected surface, current state, evidence link, blocker if any, and what remains closed.
  • Blockers count as updates. A public blocker or delay is a valid update when it is dated and specific.
  • Advertised surfaces need cadence. Vault, Data Chain, testnet, and security work should not go more than one public month without a meaningful status note after being advertised.
  • Date slips need reasons. If a public target date is later published and moves, the reason should be visible instead of silently rewritten.
  • Updates do not replace proof. Public notes should point to owner surfaces, receipts, route records, or readiness pages.

Voice And Team Posture

Public copy should be accountable without building personality mythology or implying a larger team than exists.

Chosen public voice

Use role-based project voice for public pages: Core, Infra, Bridge, Liquid, operator, validator, provider, reviewer, and tester labels.

No personal identity details

Do not disclose personal identity details, private origin story, private operator details, or personal credentials unless explicitly approved.

No invented team size

Do not imply a larger team, foundation staff, audit bench, partner network, or governance body than has been publicly disclosed.

No personality authority

Founder, operator, or public-personality inference does not create Core authority, safety, launch status, or value.

Rejected Copy Shapes

These lines stay out of public communication unless later evidence changes the factual basis.

No hype-only copyProgress should be specific, dated, and tied to visible evidence. No moon languageNo price excitement, guaranteed upside, scarcity bait, or urgency language. No fake tractionEndpoint inventory, faucet traffic, Discord activity, and testnet churn are not product-market fit. No raw safety claimCode existence, receipts, or liveness do not prove Bridge, Vault, Treasury, or relayer safety. No launch upgradeTestnet observation does not become mainnet, production value custody, or final freeze.