02Brand guidelines
Messaging
Covenant communicates the way it operates: every claim is backed by something the reader can verify. We keep one voice across documentation, posts and announcements, and adapt the tone to the audience.
Messaging
Positioning
Our positioning fits in one sentence. When there is room for only one message, lead with it.
Every agent runs under a signed grant, and every action leaves a receipt.
- Category
- Open agent-native operating layer
- Promise
- Permission, not trust
- Proof
- A receipt for every decision
- Audience
- Builders first, then everyone who runs agents
Messaging
Voice
The voice stays the same across every channel. Only the tone changes.
Exact
Calls things what the system calls them: grants, receipts, primitives, capabilities.
Not · Vague verbs, loose nouns.
Plain
Short sentences, common words. New ideas explained through familiar ones.
Not · Jargon for its own sake. Unexpanded acronyms.
Proven
Links the evidence: the commit, the audit entry, the transaction, the test.
Not · Claims without evidence. Numbers without a source.
Calm
Level and certain. The facts carry the weight.
Not · Exclamation marks, superlatives, urgency.
Open
Credits others, publishes the source, states what is unfinished.
Not · Vague about status.
Messaging
Tone by audience
The reader sets the depth and the pace.
| Audience | Where | Tone | Example |
|---|---|---|---|
| Builders | Docs, CLI, GitHub | Exact and imperative. Lead with the call or the command. | “Send request bodies as JSON; responses default to JSON.” |
| Everyone | The website, product pages | Plain and confident. What it does, then why it matters. | “Covenant lets people and agents share one computer safely. Every agent runs under a signed grant, so it can only do what you have allowed.” |
| Community | X, Telegram, the blog | Short and concrete. One idea, one link. | “Covenant Compute is live on Solana mainnet.” |
| Partners & press | Announcements, the partners page | Factual and specific. Both products, and what the integration does. | “Covenant publishes signed attestations of its audit root, a fingerprint of the full audit log, to Synapse on Solana, so other parties can verify an agent's identity.” |
Messaging
Style conventions
The small decisions, made once.
- Name
- Covenant, capital C, in running text. COVENANT in capitals only in the lockup and in tracked labels.
- Category
- Call Covenant an operating layer, not an operating system. The phrase appears only in the headline, “An operating system that builds itself,” where it works as a comparison.
- Products
- Covenant Guard, Covenant Compute, Covenant Desk on first mention; Guard, Compute, Desk after it.
- Token
- $CVNT: capitals, with the dollar sign.
- Protocols
- MCP, A2A, x402 (lowercase x), Solana.
- Hyphens
- Always hyphenate on-chain, agent-native, local-first and hash-chained. Hyphenate open-source only before a noun: open-source code, but Covenant is open source.
- Headlines
- Write headlines in sentence case; the display style sets them in capitals, and screen readers keep the original casing.
- Labels
- Two to four words in tracked JetBrains Mono capitals: Built in the open, What you plug in.
- Figures
- Numerals for data, prices and measurements, tabular in tables: 4 protocols, $3.00, 150 ms. In running text, spell out one to nine: eight primitives.
- Punctuation
- No exclamation marks. One idea per sentence.
- Emoji
- None on the site or in product; at most one in a social post.
Messaging
Taglines
Each line has one job. Use them as written.
Messaging
Boilerplate
For bios, directories, press and partner pages. Choose the length; keep the facts.
Covenant is the operating layer for agentic software: every agent runs under a signed grant, and every action leaves a receipt.
Covenant is the open, local-first operating layer for agentic software. It gives humans and agents eight host-level primitives (intent, runtime, memory, identity, permissions, communication, a compositor, and on-chain settlement) so they can safely share one computer.
Covenant is the open, local-first operating layer for agentic software. It gives humans and agents eight host-level primitives (intent, runtime, memory, identity, permissions, communication, a compositor, and on-chain settlement) so they can safely share one computer. Every agent runs under a signed grant, every action leaves a receipt in a hash-chained audit log, and Covenant's own code is written in the open by agents running on it. Covenant is open source under Apache-2.0. Learn more at opencovenant.org.
Messaging
Vocabulary
The words that carry the idea, and the ones that dilute it.
Messaging
In practice
Before your agent pays or trusts another agent, it checks an on-chain track record, confirms a real identity, and verifies a signed claim.
Says what happens, in order, in the system's own nouns.
Guard is a revolutionary, AI-powered trust solution for the next generation of web3 agents!
Every commit to Covenant is made under a signed grant, checked before it goes through, and leaves a receipt in a hash-chained audit log.
A mechanism the reader can check, not an adjective they have to believe.
Our cutting-edge autonomous engine keeps everything secure and transparent.
Covenant Compute is live on Solana mainnet.
Status, product, place. Nothing else needed.
BIG NEWS 🚀🚀 Compute is finally here, and it changes everything!!