AKRIBIS GroupBrand

AKRIBIS Brand

Where AKRIBIS's identity is decided, specified and delivered.

Decide
The reasoning is on the page: the question, the criteria, the options, the evidence, the choice and its status.
Specify
Rules someone can follow without asking.
Deliver
Files and data the sites and teams use, built from the same source as the page.

Starting point: only Branding/brand-architecture.md is settled, together with the line "Una unidad de AKRIBIS One". Everything else (the 0.2 draft, the earlier records, the palette, the source artwork and what each site invented) is evidence to re-reason.

29 topics7 open21 proposed1 ratified

1

Foundations

What every decision is judged against, who we are and how we speak.

  1. 1.1CriteriaWhat is every brand decision judged against, and in what order?Ratified
  2. 1.2Brand architectureHow do AKRIBIS the company, AKRIBIS the unit, the nine units and AKRIBIS One present themselves when they appear together?Proposed
  3. 1.3NamingHow is each name written, in text, in web addresses, in files and in every language?Proposed
  4. 1.4Unit registerWhat is the single record of each unit that every site and document reads from?Open
  5. 1.5Voice and messagingHow does AKRIBIS sound, and what may it claim?Proposed
2

Identity

Marks, colour, type and imagery. They are decided together, because each depends on the others.

  1. 2.1Parent brandWhat does AKRIBIS the company look like, as distinct from AKRIBIS the instrumentation unit?Proposed
  2. 2.2AKRIBIS One markHow is AKRIBIS One drawn, what colour is it, and how does it endorse the units?Proposed
  3. 2.3Unit wordmarksAre the nine wordmarks one consistent design, and how are they used?Proposed
  4. 2.4ColourWhat colour is each brand, and how does colour behave on screen, in print and in shared contexts?Proposed
  5. 2.5TypographyWhich typefaces does AKRIBIS use, and do all ten brands share them?Proposed
  6. 2.6Unit motifsWhat can each unit express itself with, beyond colour?Open
  7. 2.7ImageryWhat do AKRIBIS images look like? Photography, products, icons and diagrams.Proposed
3

Digital system

What the twelve sites share, what each may change and what is its own.

  1. 3.1TokensWhich values does the system define, and how does each site receive them?Proposed
  2. 3.2Site anatomyWhat must every AKRIBIS site have, what may it change, and what is its own?Proposed
  3. 3.3Shared patternsWhich components are built once and used by every site?Proposed
  4. 3.4Web standardsWhat quality bar does every site meet?Proposed
  5. 3.5Unit-site templatesWhich template draws each page of a unit site that reads the CMS, and what does each carry?Proposed
4

Applications

The brand beyond the web. Prioritised by real use, not built all at once.

  1. 4.1Office templatesWhich Office templates are needed, and what do they contain?Proposed
  2. 4.2Email signatureWhat does each unit's email signature look like?Proposed
  3. 4.3DatasheetsHow are product and service datasheets laid out?Open
  4. 4.4Certificates and reportsHow are AKRIMET's and SOLFARMA's calibration certificates and reports designed?Open
  5. 4.5StationeryWhich printed pieces does each unit need?Open
  6. 4.6Social mediaHow do the units appear on social media?Proposed
  7. 4.7EventsHow does AKRIBIS present itself at trade fairs and events?Open
  8. 4.8VideoHow do videos open, close and carry titles?Open
5

Delivery

How each decision reaches whoever uses it, as a file or as data.

  1. 5.1Asset libraryWhere does anyone get the right file, in the right format?Proposed
  2. 5.2PackagesHow do the sites receive tokens and components?Proposed
  3. 5.3Data for sites and agentsWhich facts and rules are published as machine-readable data?Proposed
  4. 5.4ChangelogHow does a site know what changed in the brand?Proposed
6

Decisions

Every decision is recorded in MADR 4.0.0. Records are written in English (ADR-0001).

  1. 0000Use MADR 4.0.0 to record Design's decisionsAccepted
  2. 0001Write Design's decision records in EnglishAccepted
  3. 0002Publish content in English, Spanish and PortugueseAccepted
  4. 0003Do the new work on a branch named nextSuperseded
  5. 0004Rename Design to Brand, with its own repositoryAccepted
  6. 0005Endorse every unit as "Una unidad de AKRIBIS One"Accepted
  7. 0006Structure Brand as one page per topic, each with its statusAccepted
  8. 0007Build Brand with Astro, as static files on its WorkerProposed
  9. 0008Compose every wordmark from one glyph library on a shared gridAccepted
  10. 0009Rank the criteria every brand decision is judged againstAccepted
  11. 0010Present the units by category, in fixed grid, circular and linear ordersAccepted
  12. 0011Set "one" and "group" from the glyph library; the parent mark is "akribis group"Accepted
  13. 0012Derive the AKRIBIS One ring from the letters, and make the ring lockup primaryAccepted
  14. 0013Generate the nine signatures from one lightness band on a 12-slot hue wheelAccepted
  15. 0014Colour the parent mark in the deep tone of the AKRIBIS tealAccepted
  16. 0015Build the ramps, neutrals, semantic colours and roles on one lightness gridAccepted
  17. 0016Colour AKRIBIS One in the teal ink, and draw the ring as one continuous spectrumProposed
  18. 0017Set the favicons as two letters on the signature, with the ring for One and the cloud for the AKIoT appProposed
  19. 0018Give every unit a profile picture: its letters inside the AKRIBIS One ringSuperseded
  20. 0019Make the tile the profile picture, fit its letters to the circle, and centre the stacked One lockup without the ringAccepted
  21. 0020Set IBM Plex Sans and Plex Mono for every brand, self-hosted and subset by rule, on a documented scaleProposed
  22. 0021Build the shape tokens on one 4 px base: spacing, radii, layout, motion, focus and elevationProposed
  23. 0022Publish the brand as data at stable addresses, with llms.txt as the rules for agentsProposed
  24. 0023Build every site in four layers and verify what each must carryProposed
  25. 0024Build the shared patterns once in Brand and prototype them on this siteProposed
  26. 0025Set the web standards as data and check every build against themProposed
  27. 0026Generate the email signature per brand and language from the registerProposed
  28. 0027Generate the Office theme per brand and publish the print values and swatchesProposed
  29. 0028Publish one asset page per brand with every file at stable addressesProposed
  30. 0029Build the tokens package on every build with a calendar versionProposed
  31. 0030Version the brand by build date and publish the decision log as the changelogProposed
  32. 0031Deliver the shared layer of every site as one Astro package with a starter, and check each build inside itProposed
  33. 0032Name the shared pages in each language and check the spellings on every buildProposed
  34. 0033Write impersonal with usted, keep a claims register, and check the voice on every buildProposed
  35. 0034Photograph real work, draw icons from IBM Carbon, and check every image a site servesProposed
  36. 0035Render each site's own layer from the CMS's windows inside the site package, cached at the edge by tagProposed
  37. 0036Build every unit site from one information architecture: the tree, the axes and the relationsAccepted
  38. 0037Render every site light by default and dark only on requestProposed
  39. 0038Check AKRIBIS's own words, not the partner's it quotesAccepted
  40. 0039Let a site keep its own proven contact formAccepted
  41. 0040Allow YouTube's privacy-enhanced player for partner videoAccepted