Distribution brand checklist

Use this checklist whenever Evergreen is added to or updated on a public surface. The approved source of truth is the brand guide; do not redesign the identity for an individual channel.

Universal checks

• Use Evergreen as the display name and evergreen-deprecation only where a package or machine identifier is required.
• Use the tagline exactly as Know what breaks next.
• Use the descriptor exactly as Local-first deprecation intelligence for software repositories. when category clarity is required.
• Use Evidence-backed migration context for humans and coding agents. only as the approved supporting message.
• Select an approved dark, light, or monochrome asset; never redraw the mark.
• Preserve clear space, minimum size, and accessible color pairs.
• Keep official brand content in English and omit personal attribution.
• Link to the official repository, documentation, and package.
• Confirm the surface does not imply hosted analysis, automatic code changes, complete ecosystem coverage, or guaranteed migration safety.
• Re-check the platform’s current image and metadata specifications before upload.

Repository and GitHub

• README uses the adaptive dark/light banner and approved descriptor.
• Repository description uses the approved descriptor.
• Homepage points to the public Evergreen documentation.
• Repository topics describe the product rather than inventing brand variants.
• Upload brand/exports/social-preview-dark.png as the repository social preview and inspect a shared link on both light and dark clients.
• Issue templates use Evergreen and evidence-backed language consistently.

Documentation

• Site title and description match approved naming.
• Header uses the adaptive Version Notches mark.
• Home page uses the approved tagline, descriptor, and supporting language.
• Light and dark palettes use approved accessible pairs.
• Brand guidance and asset terms are discoverable from public documentation.
• The site remains static, dependency-light, and free of decorative raster downloads on documentation pages.

npm

• Package ID remains evergreen-deprecation.
• Description matches the approved product descriptor.
• Homepage, repository, bugs, license, and relevant discovery keywords exist.
• Reconfirm packed contents and rendered npm README before each publish.

GitHub Action and Marketplace

• Action name contains Evergreen and identifies lifecycle intelligence.
• Action description is local-first, evidence-backed, and function-specific.
• Marketplace icon/color use the closest supported neutral treatment.
• Marketplace logo and feature-card sources exist in brand/.
• Preview marketplace metadata and images before creating or updating a listing.

Agent Skill and future plugins

• Agent Skill metadata names Evergreen and preserves trigger clarity.
• Skill content states the local execution and evidence boundaries.
• Reuse the approved name, descriptor, mark, and asset terms in every future plugin manifest and directory listing.
• Run host-specific discovery and context-cost evaluations before submission.

Releases

• Use the approved banner or social-preview template for launch posts.
• Keep release notes factual; lead with lifecycle coverage and evidence.
• Confirm changelog, package metadata, Action metadata, and documentation agree.
• Verify every referenced asset exists in the tagged commit.
• Check all external links and render the README and documentation in light and dark modes.

Asset audit

The canonical editable assets live in brand/assets/ and brand/templates/. Canonical raster exports live in brand/exports/. The documentation copy at docs/assets/brand/evergreen-mark-adaptive.svg is the only intentional duplicate; it exists because the GitHub Pages source is scoped to docs/. No legacy logo or pre-brand social asset remains in the repository.