Email signature

Specification

1. One template per brand and language, generated from the register on every build (/signatures/<brand>.<lang>.html): the brand's mark in colour as a PNG hosted on Brand (150 px wide from the 512 px file, sharp on dense screens), the name in bold, the role, the brand's line (name and area) in its text colour, phone, mobile, email and site, a hairline, the endorsement "Una unidad de AKRIBIS One" with the AKRIBIS One lockup (units only) and the company's legal line.
2. A 480 px table with inline styles, in the recipient's Arial: no mail client loads web fonts, and the mark is the one element that must be exact. No background images, floated columns or social icons.
3. The colours are the tokens: ink for the name, neutral 700 for what is secondary, neutral 200 for the hairline and the brand's text colour (step 600, at least 4.5:1 on white) for its line and its links; the parent and AKRIBIS One use their signature.
4. A person's data is five fields: name, role, phone, mobile and email. The generator on this page fills the template in the browser, drops the empty rows and copies the signature as rich text to paste into Gmail or Outlook, or as HTML. Nobody edits the HTML by hand.
5. The legal line is one, the company's, in the three languages; proposed until Voice (1.5) and legal review fix it.

To re-reason

• How it renders in each client (desktop Outlook, Gmail, Apple Mail, phones): test with real accounts before ratifying.
• How it reaches each person: this page's generator, or a central rollout (Google Workspace, Exchange) from the same HTML.
• Whether the legal line also carries a data-protection notice per country.

Evidence to audit

• brand/signature.yaml · brand/src/signature.ts · public/signatures/
• AKRIBIT/ESG · email signatures repository (the earlier, per-person HTML files)
• Mail client font support: web fonts are not loaded by Gmail, Outlook for Windows or most phone clients; Arial is the common fallback

Delivers

• One template per brand and language with its sample
• an index (signatures/index.json) and the generator on this page.

Decision

• ADR-0026 Generate the email signature per brand and language from the register Proposed