Naming

Already settled

• Unit names are written, in order of preference: all capitals (AKRIBIS, AKURALAB, AKUTEMP, AKRIMET, SOLFARMA, AKLEIA, AKZOTEC, SINGULAR4, AKIoT); all lowercase; initial capital only when truly necessary.
• AKIoT keeps a lowercase "o", because it refers to IoT.
• SOLFARMA is one word. Never "SOL FARMA" or "Sol Farma".

Specification

1. In running text, headings and buttons the names are in capitals (AKRIBIS, AKURALAB, AKUTEMP, AKRIMET, SOLFARMA, AKLEIA, AKZOTEC, SINGULAR4, AKIoT); all lowercase only where the mark is lowercase or a design asks for it; an initial capital only where capitals would shout (a legal text, a long list). The names do not change in English or Portuguese.
2. The parent is AKRIBIS Group; the offer is AKRIBIS One, two words and a capital O, never with the lockup's middle dot: "AKRIBIS · One" set in type is a redrawn mark. The endorsement is "Una unidad de AKRIBIS One" (ADR-0005), never "Parte de".
3. Identifiers: the brand id is lowercase ASCII (akribis, akuralab, akutemp, akrimet, solfarma, akleia, akzotec, singular4, akiot, akribis-group, akribis-one), the same in file names, CSS files, data-brand, the register and the repositories; the Workers drop the dot (akrimetcom). Files follow ADR-0028: <brand>-<piece>-<colourway>[-<variant>].<format>.
4. Addresses: under the URL grammar of ADR-0025 (lowercase ASCII, hyphens, a trailing slash) the shared pages are called, in Spanish, English and Portuguese: home /; contact: contacto, contact, contato; thank-you: gracias, thank-you, obrigado; privacy: privacidad, privacy, privacidade; legal notice: aviso-legal, legal-notice, aviso-legal; the 404 is one file at the root. They live in anatomy.json; the site package reads them, so no site types a slug; the checker verifies that each exists in every language. A site's own slugs follow the same grammar, translated, without accents.
5. The check: standards.yaml lists the spellings that are never written (SOL FARMA, Sol Farma, AKIOT, Akiot, AKRIBIS · One, AKRIBIS ONE, Akribis One, Parte de AKRIBIS, among others); the checker's naming rule reads every page's visible text and fails the build on one. What quotes a wrong form as an example says so with data-naming="quoted"; code is skipped.

To re-reason

• Whether the lowercase form may ever be used in running text, and capitals in long legal texts: both wait for Voice (1.5).
• The list of forbidden spellings grows with the cases that appear.
• Names in email addresses (name@unit) and in new domain names.

Evidence to audit

• communications-platforms · Branding/brand-architecture.md (settled source)
• Websites/solfarma_com · writes both AKLEIA and akleia on the same page
• Websites/akribis_info · Spanish slugs under /en/ and /pt/ (privacidad, gracias, terminos)
• brand/anatomy.yaml · pages (the slugs); brand/standards.yaml · naming (the check)

Delivers

• Spelling rules with examples
• and an automated check for the sites.

Decision

• ADR-0032 Name the shared pages in each language and check the spellings on every build Proposed