CARBON
Always set the product name in all caps. The preferred descriptor is “CARBON, the first AI Agentic Verification Harness.”
Identity
One name. Clear roles.
CARBON is the product and verification harness. testers.ai is the builder and the name of the optional premium cloud service—not the name of local CARBON commands.
Built by testers.ai
Use this attribution in product metadata, footers, about copy, and formal lockups. Keep it subordinate to the CARBON name.
carbon commands
Use lowercase carbon only for commands, skill identifiers, APIs, packages, and .carbon/ filesystem paths.
testers.ai Premium Cloud
Only optional managed cloud commands use the testers prefix. Never imply that local CARBON requires a testers.ai account or API key.
Mark and lockup
A geometric C. A decisive cut.
The supplied mark uses a bold white geometric C with an angled forward cut on an uninterrupted black square. It should feel like an engineering instrument, not a decorative badge.
Use the original artwork
Keep the black square, white geometric C, angled cut, proportions, and generous empty field intact.
Use the supplied wordmark
Use the official horizontal lockup whenever the CARBON name appears as branding. Do not recreate the angular lettering with a substitute font. Keep the beta tag visible on public product and installation surfaces while the framework remains in beta.
Let the mark breathe
Keep clear space equal to at least one quarter of the mark’s width on every side. Use 32 pixels as the minimum digital size.
Preserve the black square
The contained mark works on dark, light, photographic, and report surfaces without recoloring the C.
Do
Write CARBON in all caps.
Use the supplied mark or horizontal lockup.
Keep “Built by testers.ai” secondary.
Pair confidence claims with their evidence boundary.
Do not
Write “Carbon Framework” in title case.
Retype the wordmark in Inter or another substitute font.
Recolor, stretch, outline, round, or add gradients to the mark.
Present candidates, coverage, or confidence as proof of correctness.
Color
Dark structure. Visible evidence.
Near-black surfaces create focus. Orange identifies CARBON actions and structure. Mint identifies evidence. Blue connects systems. Yellow is reserved for beta and caution.
Typography
Editorial scale. Engineering precision.
The system uses platform-native sans-serif typography for speed and reach, with monospace reserved for commands, labels, evidence levels, and machine-readable details.
Testing that keeps up with the code.
Primary interface family: Inter when available, followed by the operating system’s UI sans-serif. Headlines are large, tightly tracked, and direct. The CARBON brand name itself uses the supplied logo artwork—not this interface typeface.
RISK → TEST → EVIDENCE → CONFIDENCE
Technical family: SFMono-Regular, Consolas, or Liberation Mono. Use it for commands, metadata, labels, counts, and state—not long marketing paragraphs.
Naming system
Make the boundary obvious.
Names should tell the user whether they are invoking the local framework, an optional premium service, or a host-specific command surface.
| Surface | Approved form | Example |
|---|---|---|
| Product | CARBON | AI Agentic Verification Harness |
| Builder | testers.ai | Built by testers.ai |
| Codex command | $carbon-* | $carbon-help |
| Claude Code skill | /carbon-* | /carbon-help |
| MCP command | /carbon_* | /carbon_help |
| Local state | .carbon/ | .carbon/runs/ |
| Premium cloud | testers_* | testers_run |
| Release state | CARBON BETA | Keep the beta label prominent. |
Voice and messaging
Lead with evidence, not certainty.
CARBON speaks like a precise testing partner: direct about what it observed, explicit about what remains unknown, and practical about the next action.
Observed failure
“Checkout failed in three recorded runs at the payment transition. Screenshots and network evidence are attached.”
Absolute certainty
Do not say “The product is 94% correct,” “fully tested,” or “bug free.” Confidence is scoped engineering judgment, not product correctness.
Remaining risk
Show missing coverage, blocked evidence, unsupported channels, and the result that would change the current decision.
Interface language
States are part of the brand.
The visual system distinguishes action, evidence, system connections, and caution so reports remain fast to scan without hiding uncertainty.
Run CARBON
Use orange for primary actions, framework labels, active selections, and the core CARBON path.
Observed and captured
Use mint for verified evidence, completed capture, and evidence-qualified outcomes—not generated candidates.
E3 observed: actual behavior and reproducible evidence captured.
Beta or incomplete
Use yellow sparingly for beta status, consequential caveats, and evidence that needs explicit attention.
Coverage gap: network recording was unavailable.
Approved assets
Use the system as a whole.
These assets share the same mark, palette, evidence language, and local-versus-cloud boundary used throughout the CARBON product.
Copyright 2026 testers.ai and Jason Arbon. All rights reserved. See NOTICE.md for redistribution terms.
CARBON beta
Make confidence visible.
Use the brand system to keep product claims, execution evidence, remaining risk, and optional cloud capabilities unmistakably clear.