docs/brand-system.md

# Plugin Autopilot Brand System

## Brand idea

**Many useful workflows, one installable Plugin.**

The Plugin Autopilot mark visualizes several repository/workflow inputs converging into one packaged destination. It is intentionally based on the product's real job: finding separate agentic workflows, deciding what belongs together, and preparing one coherent Plugin artifact.

## Geometry

The mark uses three horizontal input bars on the left, three controlled routing paths in the center, and one vertical package/module on the right. The center path is the distinctive part of the symbol: it shows separate source material being routed into one public Plugin boundary without implying that everything in the repository is copied blindly.

Rounded terminals keep the mark readable at small sizes. The large square field and simple geometry are intended to remain clear as a composer icon or directory thumbnail.

## Light variant

File: `assets/logo-light.svg`

- background: `#F7F8FC`
- primary ink: `#172033`
- routing accent: `#4F6FFF`

Use on light or neutral surfaces where the full square mark is appropriate.

## Dark variant

File: `assets/logo-dark.svg`

- background: `#0D1324`
- primary ink: `#F4F7FF`
- routing accent: `#7895FF`

The dark version preserves the same geometry rather than becoming a second logo concept.

## Composer icon

File: `assets/mark.svg`

The existing compact mark remains the declared composer icon in the current Plugin contract. Future revisions may simplify the convergence geometry further if small-size testing shows it reads better than the current icon. Do not change the composer icon solely for visual consistency without testing it at the actual small UI size.

## Usage rules

- Keep the light and dark SVG geometry synchronized.
- Do not add AI robots, brains, sparkles, circuits, or chat bubbles as secondary decoration.
- Do not add a wordmark inside the square icon.
- Do not stretch the square viewBox.
- Keep all SVG files self-contained with no remote resources or font dependencies.
- Do not invent undocumented Plugin manifest fields just to declare the dark variant.

## Product meaning

The logo should be explainable without branding jargon: **separate agentic workflows enter from the left; Autopilot decides how they fit; one clean Plugin comes out on the right.**