Skip to content

Brand — TLSStress.Art

Read in your language: English · Português · Español

Scope status (post-Scope-Freeze 2026-05-10) — All 37 MÓDULOs.Art use the canonical .Art suffix on customer-facing surfaces. Internal code retains technical naming (vyos-*, web-agent, etc.). See ARCHITECTURE.md for the full MÓDULO table. Brand tokens canonical at brand/tokens/.

The official name of this project is TLSStress.Art. The subtitle is "Web Agent Cluster for NGFW TLS Inspection performance test".

This document defines how the name MUST be rendered across docs, code, telemetry, and reports.

The name

Form When to use
TLSStress.Art Default. Use everywhere user-facing: titles, prose, reports, license footers, dashboards.
TLSStress Acceptable shorthand inside running prose after the full name has been used at least once on the same page.
tlsstress Code identifiers — package names, slugs, filenames, env-var prefixes, GitHub topic slug. Always lowercase, no dot, no separator.
TLSSTRESS Discouraged except inside ASCII art, banners, or env-var names where convention forces uppercase.

The dot before "Art" is part of the name, not punctuation. It is preserved in titles ("TLSStress.Art ships ...") even when grammar would otherwise drop it.

The subtitle

The full subtitle is "Web Agent Cluster for NGFW TLS Inspection performance test".

Always paired with the name on the first reference of any document. Subsequent references can use the name alone.

# TLSStress.Art

> Web Agent Cluster for NGFW TLS Inspection performance test

In contexts that need a single-line tagline (HTML <meta name="description">, README hero, GitHub repo description), use the subtitle verbatim.

Pronunciation

"T-L-S Stress dot Art" — letter-by-letter for "TLS", word for "Stress", spoken "dot Art" with the period audible. Avoid pronouncing as "tea-elle-ess-stress" — the letters are spoken individually.

STATUS — May 2026: official artwork now exists. The full lockup, mark-only, and favicon family ship in brand/ at the repo root. See brand/README.md for the complete specification.

The official wordmark is TLSStress.Art rendered with this precise letter case. The artwork pairs:

  • A shield containing a white padlock (TLS protection)
  • A horizontal waveform passing through the shield (stress test traffic flowing through the NGFW)
  • The wordmark "TLSStress.Art" below in a 3-color split:
  • TLS → #FFFFFF (white)
  • Stress → #00D8FC (brand cyan, sampled from the shield gradient)
  • .Art → #CBD5E1 (light slate, muted)

The dot before "Art" is part of the name and is preserved in titles even when grammar would otherwise drop it.

Canonical assets

brand/
├── README.md               canonical specification + usage instructions
├── STYLEGUIDE.html         interactive visual reference (open in browser)
├── assets/
│   ├── logo-tlsstress-art.png    full lockup, official artwork (1254×1254)
│   ├── logo-tlsstress-art.svg    full lockup, vector recreate
│   ├── logo-mark-only.svg        shield mark only (favicon-ready)
│   ├── favicon.ico               multi-size .ico (16/32/48)
│   ├── favicon-{16,32,48}.png    PNG fallbacks
│   ├── apple-touch-icon.png      180×180 for iOS home screen
│   ├── android-chrome-{192,512}.png  Android PWA icons
│   └── manifest.json             PWA descriptor
└── tokens/
    ├── brand-tokens.css          CANONICAL CSS variables (every UI imports this)
    └── brand-tokens.json         same tokens in design-tokens.org format

Color palette (extracted from logo PNG)

The full palette lives in brand/tokens/brand-tokens.css. Top-level highlights:

Token Hex Usage
--bg-canvas #000018 Logo background exact (87% of pixels)
--cyan-500 #00D8FC Primary brand (shield + waveform)
--blue-500 #0054FC Accent (shield gradient bottom)
--text-primary #FCFCFC Main text on dark surfaces

Code use

Identifier kind Form
npm/cargo/Go module name (future) tlsstress
Docker image base tlsstress (e.g. ghcr.io/<owner>/tlsstress-dashboard)
Kubernetes namespace tlsstress-system
Prometheus metric prefix leave existing web_agent_* prefix in place — that is the cohort identifier and is fingerprinted; do not retroactively rename
Env var prefix TLSSTRESS_ (e.g. TLSSTRESS_LOG_LEVEL)
GitHub topic slug tlsstress, tls-stress, tls-inspection-testing

Notably, the existing web_agent_* Prometheus metric prefix is kept: telemetry continuity is more valuable than naming consistency, and the prefix is part of the forensic fingerprinting strategy (see IP_PROTECTION.md). New metrics MAY use a tlsstress_* prefix; existing metrics MUST NOT be renamed.

License attribution

When citing the project in a third-party document, license filing, or compliance form:

TLSStress.Art (Web Agent Cluster for NGFW TLS Inspection performance test) is licensed under PolyForm Noncommercial 1.0.0 + Appendix A. © 2026 André Luiz Gallon.

In a one-liner footer:

TLSStress.Art · PolyForm Noncommercial 1.0.0 + Appendix A · No commercial use · No use in RFP/tender against competing products

Open questions — actions required from the project owner

These are NOT decisions for the codebase to make. Tracking them here so they are not forgotten.

1. Domain — tlsstress.art

The .art TLD is open to anyone. The owner SHOULD register tlsstress.art and www.tlsstress.art to prevent squatters. Cost is approximately US$15-20/year per domain.

If the domain is unavailable, decide before the brand spreads further whether to: - pivot to tlsstress.io / tlsstress.dev (and rename the project to drop the dot) - pursue acquisition from current registrant - accept that the brand exists only in code and docs, not as a public web presence

2. Trademark — TLSStress

Independent search recommended at: - USPTO TESS (United States) — https://tmsearch.uspto.gov - EUIPO TMview (European Union) — https://www.tmdn.org/tmview/ - INPI (Brazil) — https://gru.inpi.gov.br/ - WIPO Global Brand Database — https://branddb.wipo.int/

If clear, the owner SHOULD file a trademark application. The class is likely Nice 9 (computer software for testing) and possibly 42 (software-as-a-service / testing services), depending on commercial use plans (per the license, there are none, but a trademark protects against future misappropriation).

Because this project explicitly relates to Cisco NGFW products, Cisco Legal MUST review: - the project name itself ("TLSStress" is sufficiently distinct from Cisco trademarks; "Art" is generic; the combination should pass) - the trademark filing strategy (filed in the owner's name? In Cisco's name? Joint? Cisco employee work-product clauses may apply) - the audience policy text in USAGE_POLICY.md which currently names Cisco

The owner is a Cisco employee. Cisco's IP-and-employee agreements typically claim ownership of work products created in the course of employment or using Cisco resources. The right resolution may be that this becomes a Cisco-owned project under a Cisco GitHub organization — that is a strategic decision for Cisco IT / Open Source Office, not a unilateral choice.

Until Cisco Legal has reviewed: continue using TLSStress.Art in code and internal documents, but do not publicly market the name (no public website, no press, no conference talks under this brand) without legal sign-off.

Stylebook

Language

The project is presented in three languages: English, Portuguese (pt-BR), Spanish. Documentation files use the .md, .pt-BR.md, and .es.md suffixes. The brand name does not translate — TLSStress.Art is the same in every language.

Tone

The project's tone is technical, sober, candid. Not marketing-led. We measure NGFW behavior; we do not sell rhetoric. Avoid superlatives in product copy ("the best", "the only") unless backed by a measurable claim with citation.

Forbidden

  • Do not use TLSStress.Art to attack a specific competitor's product by name in marketing copy
  • Do not pair the brand with phrases that imply Cisco endorsement until Cisco Legal has confirmed the relationship
  • Do not use TLSStress.Art in derivative works that have not received written authorization (per Appendix A)