Arthur Costa

Why this design

1. The concept is DDIA chapter 8: a lease holder can pause, wake up and write anyway, so storage must check a fencing token and reject anything older than the newest it has seen.
2. The page is that storage: every section is a write carrying a token, 33 to 43; a token turns from grey to ink when storage has seen it, the tokens only rise as you read, and the bar at the top shows the highest one storage has seen (reads need no token, so scrolling back changes nothing).
3. Safety leads the information architecture: the invariants come first as the spine, then the production work they were written in, then the three records where the rule is most direct (AC-006, AC-004, AC-007), and roles become leases handed from one token to the next.
4. “Remove safety dependency” makes the whole page fail closed: every demo refuses with a reason instead of running, which is AC-006's rule applied to this document.
5. My portrait is the storage: the hero paints it under two writers over a faint copy, so it is never an empty frame; the stale-writer demo shows what an unchecked token does to it, and the contact section shows it whole, written only by the newest token.
6. One family, Archivo, from tokens at width 62 to reading text at width 100 and 17.5 px; its width axis is the pause, so the name narrows while writer A is stopped. IBM Plex Mono is kept for tokens, labels and the demos' output.
7. Colour comes from the plate: warm off-white and ink, teal for the current token and anything accepted, ochre for the stale writer, terracotta only for a rejection or a refusal, each also written as a word.
8. Motion shows only causality and plays once; every demo has a text equivalent, controls are real buttons and inputs at 44 px, reduced motion shows end states, and Pause stops everything.

Facts on this page come from my records; employers and clients are deliberately not named. Demo commands are illustrative.