PAXEER NETWORK® — INTRODUCTION
INTRODUCTION
This document establishes the rules that govern how Paxeer Network looks, sounds, and behaves. It is precise, opinionated, and non-negotiable in its core principles. The identity is built on an obsidian aesthetic with Ink Blue as the only accent. Everything else is restraint.
01 — MESSAGING
Messaging
Paxeer communicates through function. Every message leads with what a system can do, then explains how. Marketing copy, technical docs, and social posts all follow the same voice: direct, capable, and free of theater.
Machine-first
Describe what agents and services can do. Humans are builders, not end-users.
Capability-led
Lead with outcomes: settle, earn, prove, pay. Not features.
Present tense
Write what is true now. Not roadmap. Not vision. Proof.
No theater
No yield farming hype, no DeFi superlatives. Rails that work.
02 — CRITICAL STYLE CONVENTIONS
Critical Style Conventions
These conventions are not preferences — they are rules. Every Paxeer publication, internal or external, follows them without exception.
- 01Brand name on first mention: PAXEER NETWORK® (full name, registered mark)
- 02Subsequent mentions: Paxeer Network, or Paxeer — never 'Pax', 'PN', or 'the network'
- 03Do not use possessive form: 'Paxeer's infrastructure' → 'Paxeer infrastructure'
- 04Never abbreviate the name in external or formal communications
- 05Avoid superlatives unless backed by verifiable, cited fact
- 06Write onchain as one word — never on-chain or on chain
03 — TAGLINES
Taglines
Approved taglines for Paxeer Network. These are the only lines to use in brand contexts. Do not create variations or localized adaptations without brand team sign-off.
The settlement layer for the machine economy.
Where machines transact.
Rails for autonomous commerce.
Software that spends, earns, and settles.
The invisible economic layer.
04 — COPY
Copy
Copy is infrastructure. It sets expectations, reduces support burden, and earns trust. Every word in every interface, document, and campaign is subject to the same standards.
APPROVED COPY PATTERNS
Agents settle in one block.
Our platform enables near-instant settlement.
Set a daily cap. Add an allowlist. Done.
Powerful and flexible policy management.
Get paid per call.
Monetize your API services seamlessly.
05 — WRITING GUIDELINES
Writing Guidelines
Paxeer speaks plainly. We do not hedge, qualify, or over-explain. We treat the reader as intelligent and informed. Active voice is the rule.
- 01Write in active voice. 'Agents settle payments' — not 'Payments are settled by agents'
- 02Sentences should be short. If a sentence needs a semicolon, split it into two
- 03Paragraphs should have one idea each. No more.
- 04Technical terms are acceptable when the audience knows them. Define nothing the reader already understands.
- 05Never begin a paragraph with 'We believe' or 'We think'. State facts, not beliefs.
- 06Numbers below 10 are written as words. Numbers 10 and above are numerals.
06 — TONE & VOICE
Tone & Voice
The Paxeer voice has four consistent attributes. They apply equally to technical docs, social posts, press releases, and onboarding flows.
Architectural
Precision in structure. Every decision has intent. Negative space is clarity.
Neutral
The rails stay neutral. We never take sides in the commerce that runs on them.
Direct
State what a machine can do, then prove it. No jargon. No yield theater.
Premium
Premium means nothing is wasted. Every word earns its place.
07 — CLARITY, CONCISION & FLOW
Clarity, Concision & Flow
These are the three writing virtues Paxeer copy is evaluated against. In that order. Clarity is never sacrificed for concision. Concision is never sacrificed for flow.
Clarity
Say exactly what you mean. If a sentence can be misread, rewrite it.
Test: Read it to someone unfamiliar with the product. If they need to ask a question, rewrite.
Concision
Remove every word that does not add meaning. Then remove three more.
Test: Count the words. Try to make the same point in half as many.
Flow
Sentences should move with momentum. Short-long-short rhythm. No buried verbs.
Test: Read it aloud. If you run out of breath before the period, the sentence is too long.
08 — NUANCES
Nuances
These are the subtleties that separate Paxeer copy from generic technology writing. They are not obvious. They require judgment.
- 01When describing the network, lead with infrastructure, not assets. Lead with the rails, not what runs on them.
- 02Describe PAX as a native asset — not a token, coin, or currency unless context demands it.
- 03Never imply human emotion when describing machine behavior. Agents 'execute', not 'decide' or 'choose'.
- 04Avoid 'ecosystem' — it implies organic growth. Paxeer is built, not grown.
- 05Precision over simplicity when stakes are high. On-chain legal and financial statements are not simplified.
- 06Respect the engineer's time. If they can infer it, don't write it.
09 — WHAT TO AVOID
What to Avoid
These patterns are strictly prohibited in all Paxeer communications, internal and external. They undermine authority, confuse the audience, or misrepresent the brand.
Never use jargon that requires a glossary
Avoid passive constructions that obscure responsibility
Do not use exclamation marks in brand copy
Never describe Paxeer as 'disruptive' or 'revolutionary'
Do not use legacy brand colors or unauthorized logo variants
Never compare Paxeer to competitors by name
Avoid hedge words: 'kind of', 'sort of', 'basically', 'essentially'
Do not use 'synergy', 'leverage', 'paradigm', 'cutting-edge'
10 — CORE IDENTIFIERS
Core Identifiers
The fundamental identifiers that define the Paxeer brand at its most reduced form.
SYMBOL MARK
PX Square
Preferred digital identifier
WORDMARK
Paxeer
Full brand name, typeset
TOKEN
PAX
Native network asset
CORE COLOR IDENTIFIERS
Obsidian
#04050A
Paxeer Blue
#004CED
Paxeer Ink
#2841B8
Paper
#FFFFFF