feat(brand): unify org mark and add brand guide - #22
Merged
Conversation
The organisation had four different visual identities: the GitHub avatar (Agent Manifest's glyph recoloured dark), the site favicon (navy "A"), and two unrelated gradient families across the four product icons. There was no brand guide anywhere in the org, which is why they drifted. Adopt one shield family. The org mark is the shield carrying the "A", keeping the existing navy/red equity from the site while joining the family that the product marks form. Palette is locked to the tokens already defined in index.html rather than the MkDocs Material default purple the product icons had picked up. Regenerate favicons from the new mark, add the vector and avatar assets under brand/, and document the system in brand/BRAND.md so this cannot drift again. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
imran-siddique
added a commit
that referenced
this pull request
Aug 19, 2026
The brand guide added in #22 declared the navy and #F2F4F7 palette canonical and said those tokens were the ones in use. That had not been true since the editorial design system landed, and the theme alignment that followed spread the parchment surfaces to the remaining pages, so the repository was carrying two contradictory sources of truth. Split the palette by the question each colour answers. Surfaces are the editorial parchment and ink tokens, which is what actually ships on every property including the four MkDocs subdomains. Marks and accents are the brand guide's values, unchanged, so no icon needs regenerating. That leaves one correction in each direction. The editorial system had invented its own red and amber, and the hub bridge had retuned four semantic accents the guide names explicitly; all six now use the documented hexes. In particular --at-red becomes #B91C1C, the same red as the mark, so the site and the icons no longer ship two reds close enough to read as a mistake. Document the two legitimate exceptions, dark-scheme and code-surface derivations and third-party logo colours, so the rule that an undocumented hex does not belong stays enforceable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adopts a single shield-based mark system for AgenTrust and documents it, so the org stops shipping four different identities.
Why
An audit of every icon asset in the org found:
cmcpandca2ashipped byte-identicalicon.svgfiles (5ff302ae…). Two products, one mark.brand_comment.py. The icons were drawn ad hoc per repo, which is the root cause of the drift.The two product gradients were MkDocs Material theme defaults (
#7c3aed,#0ea5e9,#5BD2BE,#8251EE,#C661F7), not AgenTrust colours. Meanwhileindex.htmlalready defines a deliberate, internally consistent token set (--navy #15294B,--red #B91C1C, …) used across the site, demos, and extension pages, and the existing "A" favicon matches it exactly. That token set is the real brand, so the mark system is locked to it.Changes
.ico).brand/holds the light and solid vectors plus a 500px avatar raster.brand/BRAND.mddocuments the wordmark, palette, mark system, and the rules that prevent recurrence: no product glyph as the org avatar, no two projects sharing a mark, no Material default purple.Rasters are generated from the same coordinates as the SVG, so vector and raster cannot drift.
Product icon PRs follow separately, one per project repo.
🤖 Generated with Claude Code