The firm behind the brands
One firm, two brands, one system
A company is not its first product.
01Cover — Savison Life, read as a systems designer: one firm, two brands, one token system dressing both.Full size ↗ 
02My relationship to the work — Founded, designed and built by me. This study is written from primary records, not recollection.Full size ↗ 
03The problem — For two months the firm and its first product were the same name, doing two incompatible jobs.Full size ↗ 
04The architecture — One app, one database, one deployment. Brand is resolved from the hostname and forwarded on a header.Full size ↗ 
05Slots, not colours — The base palette is a set of roles. A brand fills them; components never learn a colour name.Full size ↗ 
06The measurement — 1,788 role tokens against 26 brand-named ones — the number that made a second brand affordable.Full size ↗ 
07What a brand may and may not refill — The brand block refills colour slots only. Geometry, type scale and spacing stay with the system.Full size ↗ 
08Four reversible phases — Each phase shipped on its own and could be undone on its own.Full size ↗ 
09The console stays in company colours — The one surface deliberately exempted from the brand it administers.Full size ↗ 
10Where the legal entity surfaces — A brand is not a company. The system renders that fact wherever money and law require it, and nowhere else.Full size ↗ 
11What the system did not catch — Three failures that produced no error at all — the class of bug this architecture is most exposed to.Full size ↗ 
12Stated limits — What this study could not verify, could not show, and deliberately does not claim.Full size ↗ 
13The rest of this project — The other lenses on Savison Life, and the marketplace it operates.Full size ↗