Something went wrong. Try again.
Something went wrong. Try again.
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024@import "tailwindcss" source(none);@import "./tailwind.css";
/* Only the files actually served are scanned -- not node_modules/ or old template experiments. Paths are relative to this file. Several of these pages are generated (git-ignored) by scripts that run BEFORE Tailwind in `npm run build`, so the utilities in their templates exist on disk when the scan happens; explicit @source paths are scanned even though git ignores them. */@source "../index.html";@source "../404.html";@source "../mirrors/index.html";@source "../tech/index.html";@source "../experiments/index.html";@source "../projects/index.html";@source "../infra/index.html";@source "../ai/index.html"; /* generated by scripts/build-ai.mjs */@source "../news/index.html"; /* generated by scripts/build-news.mjs */@source "../art/index.html";@source "../papers/index.html";@source "../papers/essentialism/index.html";@source "../papers/rrf-score-ceiling/index.html";@source "../art/essentialism/index.html";@source "../art/essentialism/play.js";@source "../essentialism/index.html"; /* the forwarding stub left when essentialism moved under /art/ */@source "../archive/index.html";@source "../blog/**/*.html"; /* generated by scripts/build-blog.mjs */@source "../search/index.html";@source "../profiles/index.html";@source "../marfa/index.html";@source "../speaking/**/*.html"; /* generated by scripts/build-speaking.mjs */@source "../search.js"; /* builds the search overlay at runtime */
@layer base { @font-face { font-family: "Public Sans"; /* format("woff2"), not the legacy format("woff2-variations") token: the latter came from an early CSS Fonts 4 draft, and a UA that does not recognise a format token SKIPS that src entry. This @font-face has only one entry, so an unrecognised token means the face is never used -- while the <link rel=preload> fetches all 19 KB of it regardless. */ src: url("/fonts/publicsans-v2.woff2") format("woff2"); font-weight: 400 700; font-display: swap; }}
/* The footer's "Top" link is a plain #top anchor rather than a floating button — a fixed control hovering over the page is the pattern the header rework removed, and on narrow screens it would land back on top of content. Smooth scrolling is opt-out for anyone who has asked for less motion. */@media (prefers-reduced-motion: no-preference) { html { scroll-behavior: smooth; }}
/* Long contract addresses / URLs in prose must not push the page sideways. */main { overflow-wrap: anywhere;}
/* Light mode — auto via OS preference, manually overridable via the header theme button (html.light / html.dark set by theme.js; "follow system" = no stored key). Palette mirrors the dark brand; wordmark + icons stay #a3a3a3 (works on both). Covers the home page, the header, the footer, and every subpage. */@media (prefers-color-scheme: light) { html:not(.dark) body.bg-black { background-color: #ffffff; } html:not(.dark) .bg-zinc-800 { background-color: #f4f4f5; } html:not(.dark) .text-neutral-400 { color: #52525b; } html:not(.dark) h3.text-neutral-400 { color: #71717a; } html:not(.dark) .text-neutral-500 { color: #71717a; } html:not(.dark) .text-neutral-300 { color: #3f3f46; } html:not(.dark) .text-white { color: #000000; }}html.light body.bg-black { background-color: #ffffff; }html.light .bg-zinc-800 { background-color: #f4f4f5; }html.light .text-neutral-400 { color: #52525b; }html.light h3.text-neutral-400 { color: #71717a; }html.light .text-neutral-500 { color: #71717a; }html.light .text-neutral-300 { color: #3f3f46; }html.light .text-white { color: #000000; }/* Same hover query Tailwind emits hover:text-white in (future.hoverOnlyWhenSupported). */@media (prefers-color-scheme: light) and (hover: hover) and (pointer: fine) { html:not(.dark) .hover\:text-white:hover { color: #000000; }}@media (hover: hover) and (pointer: fine) { html.light .hover\:text-white:hover { color: #000000; }}
/* Dark is the base, so these are unscoped and the light rules above and below override them. Tailwind's own neutral-500 (#737373) and neutral-600 (#525252) measure 4.43:1 and 2.69:1 on black; neutral-600 carries the two links in the footer build stamp, the card numbers on /projects/ and /experiments/, and the price on /art/essentialism/. Both go to the same #757575 as --ink-soft, which collapses two dim tones into one -- the gap between "passes AA on black" and "is already --ink" is narrow enough that there is little room for a third. */.text-neutral-500 { color: #757575; }.text-neutral-600 { color: #757575; }
/* ...which means light mode needs its own neutral-600, or the line above would lighten it from 7.8:1 to 4.6:1 there. */@media (prefers-color-scheme: light) { html:not(.dark) .text-neutral-600 { color: #52525b; } /* .bg-zinc-900 had no light override, so the <pre> on /mirrors/ kept its dark #18181b while .text-neutral-400 remapped to #52525b -- 2.29:1, the only light-mode contrast failure on the site. */ html:not(.dark) .bg-zinc-900 { background-color: #f4f4f5; }}html.light .text-neutral-600 { color: #52525b; }html.light .bg-zinc-900 { background-color: #f4f4f5; }
/* Search. Plain CSS rather than utilities because search.js injects the overlay markup at runtime; keeping the class names here means no purge surprises. */.search-overlay { position: fixed; inset: 0; z-index: 50; display: flex; justify-content: center; padding: 4rem 1rem 1rem; background: rgba(0, 0, 0, 0.72); overflow-y: auto;}/* search.js closes the overlay with the `hidden` attribute, whose Preflight rule `[hidden]:where(:not([hidden=until-found])){display:none}` has the SAME specificity as `.search-overlay` — and loses on source order, because this file is appended after Preflight. Without this rule the closed overlay stays display:flex and covers every page. Keep it adjacent to the rule it defends against. */.search-overlay[hidden] { display: none;}html.search-open,html.search-open body { overflow: hidden;}.search-panel { width: 100%; max-width: 40rem; height: max-content; background: #0a0a0a; border: 1px solid #27272a; overflow: hidden;}.search-form { display: flex; align-items: center; gap: 0.5rem; padding: 0.75rem; border-bottom: 1px solid #27272a;}.search-input { flex: 1 1 auto; min-width: 0; min-height: 2.75rem; padding: 0 0.75rem; color: #ffffff; background: transparent; border: 0; font: inherit; font-size: 1rem; /* 16px — anything smaller and iOS zooms the page on focus */ -webkit-appearance: none; appearance: none;}
/* Replaces the outline removed above: the caret alone is not an indicator for anyone navigating by keyboard rather than typing. */.search-input:focus-visible { outline: 2px solid var(--accent); outline-offset: -2px;}.search-input::placeholder { color: #71717a;}.search-close { flex: 0 0 auto; min-height: 2.75rem; padding: 0 0.625rem; color: #a3a3a3; background: transparent; border: 1px solid #3f3f46; font: inherit; font-size: 0.75rem; cursor: pointer;}.search-close:active { color: #ffffff; border-color: #a3a3a3;}@media (hover: hover) and (pointer: fine) { .search-close:hover { color: #ffffff; border-color: #a3a3a3; }}.search-results { margin: 0; padding: 0; list-style: none; max-height: 60vh; overflow-y: auto;}.search-result { display: block; padding: 0.875rem 1rem; border-top: 1px solid #18181b; color: #a3a3a3; text-decoration: none;}.search-results li:first-child .search-result { border-top: 0;}.search-result:focus,.search-result:active { background: #18181b;}@media (hover: hover) and (pointer: fine) { .search-result:hover { background: #18181b; }}
/* The overlay's own arrow keys move focus between results, so this is the primary keyboard path through search. The background tint alone measured 1.12:1 against the panel, which is not a focus indicator. */.search-result:focus-visible { outline: 2px solid var(--accent); outline-offset: -2px;}.search-result-title { display: block; color: #ffffff; font-weight: 600;}.search-result-meta { display: block; margin-top: 0.125rem; font-size: 0.75rem; color: #71717a; overflow-wrap: anywhere;}.search-result-snippet { display: block; margin-top: 0.375rem; font-size: 0.875rem; line-height: 1.5;}.search-empty { padding: 1rem; color: #71717a; font-size: 0.875rem;}.search-hit { background: transparent; color: inherit; font-weight: 700; text-decoration: underline; text-underline-offset: 2px;}
@media (prefers-color-scheme: light) { html:not(.dark) .search-overlay { background: rgba(255, 255, 255, 0.75); } html:not(.dark) .search-panel { background: #ffffff; border-color: #d4d4d8; } html:not(.dark) .search-form { border-bottom-color: #e4e4e7; } html:not(.dark) .search-input { color: #000000; } html:not(.dark) .search-input::placeholder { color: #71717a; } html:not(.dark) .search-close { color: #52525b; border-color: #d4d4d8; } html:not(.dark) .search-close:active { color: #000000; border-color: #52525b; } html:not(.dark) .search-result { color: #52525b; border-top-color: #e4e4e7; } html:not(.dark) .search-result:focus, html:not(.dark) .search-result:active { background: #f4f4f5; } html:not(.dark) .search-result-title { color: #000000; }}@media (prefers-color-scheme: light) and (hover: hover) and (pointer: fine) { html:not(.dark) .search-close:hover { color: #000000; border-color: #52525b; } html:not(.dark) .search-result:hover { background: #f4f4f5; }}html.light .search-overlay { background: rgba(255, 255, 255, 0.75); }html.light .search-panel { background: #ffffff; border-color: #d4d4d8; }html.light .search-form { border-bottom-color: #e4e4e7; }html.light .search-input { color: #000000; }html.light .search-input::placeholder { color: #71717a; }html.light .search-close { color: #52525b; border-color: #d4d4d8; }html.light .search-close:active { color: #000000; border-color: #52525b; }html.light .search-result { color: #52525b; border-top-color: #e4e4e7; }html.light .search-result:focus,html.light .search-result:active { background: #f4f4f5; }html.light .search-result-title { color: #000000; }@media (hover: hover) and (pointer: fine) { html.light .search-close:hover { color: #000000; border-color: #52525b; } html.light .search-result:hover { background: #f4f4f5; }}
/* WebKit renders a native <select> at its own intrinsic height and ignores min-height until -webkit-appearance is cleared — which left this control 18px tall, under the 24px minimum target size. Clearing appearance also drops the native chevron, so draw one (data: URIs are permitted by the img-src CSP directive). */select.ess-control { -webkit-appearance: none; appearance: none; padding-right: 2rem; background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 12 12'%3E%3Cpath d='M2 4.5 6 8.5 10 4.5' fill='none' stroke='%23a3a3a3' stroke-width='1.5' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E"); background-repeat: no-repeat; background-position: right 0.625rem center; background-size: 12px 12px;}
/* essentialism page controls — the dark chips need a light counterpart, or they render as black-on-grey when the light palette kicks in. */@media (prefers-color-scheme: light) { html:not(.dark) .ess-control { background-color: #e4e4e7; color: #3f3f46; }}html.light .ess-control { background-color: #e4e4e7; color: #3f3f46; }
/* Body copy: one measure, justified. The pages used to set max-w-prose (65ch) on every <p> while the containing <main> was max-w-screen-md (768px), so paragraphs wrapped ~150px narrower than the headings and card grids above them and nothing lined up on the right. The container is now the single source of measure; paragraphs fill it.
Justification needs hyphenation or it opens rivers of white space, so hyphens are on wherever body copy sits (the <html lang="en"> declaration is what lets the browser hyphenate correctly). Justified from 48rem up only: on a phone a sans line holds about 40 characters, too few word spaces to absorb the slack, so phone copy sets flush left, and without justification the hyphens would only break words, so they go too.
Reading pages (posts, papers, talks, tech, infra) carry body.read, which narrows the whole page, running head included, to a 35rem text column: about 66 characters a line at 16px. Index and card pages keep the 48rem frame. One width per page, so headings, text and grids still share both edges. *//* DIRECT children only. Card and grid-item paragraphs are nested, and they are UI copy in a ~300px column -- justifying those produced "fig-ure resolve" and "ca-nine representation" on /experiments/. Body copy is the only thing wide enough to justify well. */@media (min-width: 48rem) { main > p, main > ul:not(.toc) > li, main > ol > li, main > .e-content > p, main > .e-content > ul:not(.toc) > li, main > .e-content > ol > li { hyphens: auto; /* No hyphen in a word under six letters ("oth-er"). 6 3 3 was measured too: it takes away so many break points that justified lines stretch further, doubling the word spaces over 0.5em in Chrome and Safari. */ hyphenate-limit-chars: 6 2 2; }}
/* A hyphen inside a link reads as part of the address: 512kb.club broke as "512k-b.club". Links break only where their own text allows. */main a { hyphens: manual;}
/* A blog post's body sits in one .e-content element (its h-entry content), so each rule here names that level as well as main itself. */@media (min-width: 48rem) { main > p:not(.no-justify), main > ul:not(.toc) > li:not(.no-justify), main > ol > li:not(.no-justify), main > .e-content > p:not(.no-justify), main > .e-content > ul:not(.toc) > li:not(.no-justify), main > .e-content > ol > li:not(.no-justify) { text-align: justify; text-justify: inter-word; }}
/* A short code token reads as broken when a line ends inside it ("script-" / "src"), including at a hyphen it contains. scripts/mark-short-code.mjs gives inline code of 30 characters or fewer the class .nb at build time; longer code (hashes, URLs, commands) is wider than a phone column and keeps wrapping. */main :not(pre) > code.nb { white-space: nowrap;}
body.read main,body.read .running-head { max-width: 38rem;}
/* Anything monospace reads as broken when stretched to a full justified line, and .no-justify is the explicit opt-out for a line that should stay ragged.
Font size used to be on this list, on the assumption that text-sm meant a short caption. It does not: /mirrors once styled all 26 of its section blurbs text-sm and they were full-measure body copy, so the page rendered one justified lead above 26 ragged paragraphs (the blurbs are base size now, like every other page's body, but the rule was wrong regardless). Size describes emphasis, not length -- a caption short enough to look wrong justified is a single line, and a single line is its own last line, which justification leaves alone anyway. Mark the exceptions that are really exceptions and let the rest set consistently. */main > p.font-mono,main > .e-content > p.font-mono,main .no-justify { text-align: left;}
/* ------------------------------------------------------------------ *//* The six color roles — knowledge is in the brand doc; the rule here: *//* every color in the components below is one of these six variables. *//* Resolution mirrors the theme model: dark is canonical, the system *//* preference is the silent default, html.light / html.dark (set by *//* theme.js) force a mode. *//* One component is exempt, and only one: the essentialism syntax *//* highlighting at the foot of this file paints in that piece's own *//* on-chain ink library. Its reasoning is written there. */:root { --bg: #000000; --ink: #a3a3a3; /* #737373 measured 4.43:1 on black -- under the 4.5:1 floor, and this token carries running heads, section labels, post meta and table headers on every page. #757575 is the nearest value that clears it. */ --ink-soft: #757575; --title: #d4d4d4; --rule: #27272a; --accent: #ffffff;}html.light { --bg: #ffffff; --ink: #52525b; --ink-soft: #71717a; --title: #3f3f46; --rule: #e4e4e7; --accent: #000000;}@media (prefers-color-scheme: light) { html:not(.dark) { --bg: #ffffff; --ink: #52525b; --ink-soft: #71717a; --title: #3f3f46; --rule: #e4e4e7; --accent: #000000; }}
/* Running head: page label at the left margin (INDEX — the homepage IS the index, so the label is truthful from every page and is the slot a menu would later occupy), controls at the right, the two ends tied by one hairline. Static, not sticky: it occupies real space, so nothing can scroll under it, and it retires with the page like a printed running head. */.running-head { display: flex; align-items: baseline; justify-content: space-between; max-width: 768px; margin: 0 auto; padding: 1.3rem 1.5rem 0;}.running-head .rh-left,.running-head .rh-right { border-bottom: 1px solid var(--rule); padding-bottom: 0.8rem; font-size: 0.72rem; letter-spacing: 0.22em; text-transform: uppercase; color: var(--ink-soft);}.running-head .rh-left { flex: 1 1 auto; }.running-head .rh-right { flex: 0 0 auto; padding-left: 1rem; text-align: right; }.running-head a,.running-head button { font: inherit; letter-spacing: inherit; text-transform: inherit; color: inherit; text-decoration: none; background: none; border: 0; padding: 0; cursor: pointer; position: relative;}/* The labels are about 17px tall; this invisible box makes each one a 44px target. */.running-head a::after,.running-head button::after { content: ""; position: absolute; inset: min(0px, (100% - 44px) / 2);}.running-head a:active,.running-head button:active { color: var(--accent); }@media (hover: hover) and (pointer: fine) { .running-head a:hover, .running-head button:hover { color: var(--accent); }}/* The theme control names the mode a tap switches TO, and the label lives in CSS so it is correct before first paint and with JavaScript disabled. The cascade mirrors the palette resolution above exactly. */#theme-toggle::before { content: "Light"; }html.light #theme-toggle::before { content: "Dark"; }@media (prefers-color-scheme: light) { html:not(.dark) #theme-toggle::before { content: "Dark"; }}html.dark #theme-toggle::before { content: "Light"; }
/* Entry rows. The whole row is the link: destination at the left in the title ink, what-it-is at the right in the quiet register. Structure is drawn with hairlines, never with filled boxes. Below 540px the annotation drops under the title so neither truncates. */.toc { list-style: none; margin: 0; padding: 0; width: 100%; text-align: left; border-top: 1px solid var(--rule);}.toc li { border-bottom: 1px solid var(--rule); }.toc a { display: flex; align-items: baseline; justify-content: space-between; gap: 1rem; color: var(--title); text-decoration: none; font-size: 1.08rem; font-weight: 500; padding: 0.85rem 0.4rem; transition: color 0.15s;}.toc a:active { color: var(--accent); }.toc a:active .who { color: var(--ink); }@media (hover: hover) and (pointer: fine) { .toc a:hover { color: var(--accent); } .toc a:hover .who { color: var(--ink); }}.toc a:focus-visible { outline: 1px solid var(--ink); outline-offset: -1px; }/* A row can carry markers under its title — what is new, what is not mine. They go below rather than in the .who slot on the right, because that slot says what a thing IS and every other row uses it that way; a marker is a different kind of fact and would read as a category if it sat there.
The row is baseline-aligned, so the title and the right-hand annotation stay on one line and the markers hang beneath without pushing anything down. */.toc .lede { display: block; min-width: 55%; }.toc .marks { display: block; margin-top: 0.3rem; font-size: 0.62rem; letter-spacing: 0.2em; text-transform: uppercase; font-weight: 400; color: var(--ink-soft);}/* The loudest ink in either theme, because "new" is the whole point of saying it. */.toc .marks .new { color: var(--accent); }
/* A long annotation wraps right-aligned inside the space the title leaves; the title keeps at least 55% of the row. */.toc .who { color: var(--ink-soft); font-size: 0.68rem; letter-spacing: 0.2em; text-transform: uppercase; text-align: right; hyphens: manual; transition: color 0.15s;}/* Wallet addresses on /support/: a label in the .who style over the address in monospace. An address is copied character for character, so it never hyphenates and breaks anywhere rather than at a hyphen it does not contain. The block and the note under it run the list's full width and sit on the same inset as the list's row text, so every left edge on the page lines up. */.addresses,.addresses-note { margin: 1.9rem 0 0; padding: 0 0.4rem; text-align: left;}.addresses dt { color: var(--ink-soft); font-size: 0.68rem; letter-spacing: 0.2em; text-transform: uppercase; margin-top: 1.1rem;}.addresses dt:first-child { margin-top: 0; }.addresses dd { margin: 0.3rem 0 0; font-family: ui-monospace, SFMono-Regular, Menlo, monospace; font-size: 0.8rem; line-height: 1.5; overflow-wrap: anywhere; word-break: break-all; hyphens: none; user-select: all;}
/* /speaking/: the date and running time are one fact and fit beside any title, so they never wrap. */.talks .who { white-space: nowrap; }/* The /speaking/ intro sits under the title rather than in the header. */.speaking-intro { margin-top: 1.2rem; }
@media (max-width: 540px) { .toc a { flex-direction: column; align-items: flex-start; gap: 0.15rem; } .toc .lede { min-width: 0; } .toc .who { text-align: left; }}
/* Hairline card: the box idiom of the subpage grids, translated — no fill, no radius, structure drawn with the same 1px rule as everything else. */.hairline-card { border: 1px solid var(--rule); background: transparent;}
/* Card figures (/hairline/, mounted by /hairline/mount.js). Plates are filled, so --hairline-plate must equal the page background in each theme. */.hl-figure { position: relative; max-width: 22rem; --hairline-plate: #000000; --hairline-hi: #a3a3a3; --hairline-edge: #525252; --hairline-mid: #404040; --hairline-lo: #262626;}/* The figure is drawn by script into a 400 x 320 viewBox. Holding that shape before it arrives keeps the card, and every card after it, from moving. */.hl-figure [data-hl] { aspect-ratio: 400 / 320;}.hl-read { position: absolute; top: 0; right: 0;}@media (prefers-color-scheme: light) { html:not(.dark) .hl-figure { --hairline-plate: #ffffff; --hairline-hi: #52525b; --hairline-edge: #a1a1aa; --hairline-mid: #d4d4d8; --hairline-lo: #e4e4e7; }}html.light .hl-figure { --hairline-plate: #ffffff; --hairline-hi: #52525b; --hairline-edge: #a1a1aa; --hairline-mid: #d4d4d8; --hairline-lo: #e4e4e7;}
/* The card's title is its link. A card is a container, not a button: anchoring the title is what a printed index does, and it gives the entry one honest destination — copyable, keyboard-reachable, and announced by name rather than as a wall of card text. It also lets a card carry other links (source, run it here) without nesting an anchor inside an anchor, which the whole-card link idiom on /experiments/ could not. Nothing is drawn at rest — the hover is the same quiet dim the whole-card links used before, so a grid of these reads as a page of titles rather than a page of links. The focus ring is not decoration and stays. */.card-title a { position: relative; color: inherit; text-decoration: none; transition: opacity 0.15s;}/* Invisible box that grows a one-line title to a 44px target. */.card-title a::after { content: ""; position: absolute; inset: min(0px, (100% - 44px) / 2);}.card-title a:active { opacity: 0.7;}@media (hover: hover) and (pointer: fine) { .card-title a:hover { opacity: 0.7; }}.card-title a:focus-visible { outline: 1px solid var(--ink); outline-offset: 3px;}
/* Headings wrap to even lines instead of leaving one word on the last. */main h1,main h2,main h3 { text-wrap: balance;}
/* A small sentence-case note under a list or intro (the IPFS archive line on /speaking/): quieter than body copy, but a sentence, so not in the tracked uppercase of .post-meta, which would also print a case-sensitive CID in capitals. */.list-note { font-size: 0.875rem; line-height: 1.5; color: var(--ink-soft); margin-top: 0.8rem;}
/* Section label + the short centered rule under a page title. */.section-label { font-size: 0.75rem; font-weight: 600; letter-spacing: 0.12em; text-transform: uppercase; color: var(--ink-soft); margin: 2.6rem 0 1.1rem; text-align: center;}.section-label:first-of-type { margin-top: 0; }.center-rule { border: 0; border-top: 1px solid var(--rule); width: 34%; margin: 0 auto 2.6rem;}
/* ------------------------------------------------------------------ *//* Blog posts. Generated by scripts/build-blog.mjs, so these classes are written there and nowhere else — the hand-written pages do not use them.
The body copy needs no rules of its own: post prose is a direct child of main, so it picks up the same justification and hyphenation as every other page. What is here is only what a post has and a hand-written page does not — a byline, in-flow images, headings inside the body, and a table. */.post-meta { margin-top: 0.6rem; font-size: 0.72rem; letter-spacing: 0.14em; text-transform: uppercase; color: var(--ink-soft);}/* The author leads the byline and is the one part of it a reader should catch without looking for it — a post here may be written by someone other than the owner of the domain, or by an agent, and both cases are only honest if the name is the first thing read. Everything else on the line stays quiet. *//* The post header — title, byline, what-kind-of-author, tags — centred as one block, the way /archive, /art, /mirrors, /tech, /infra and the blog index already centre theirs. Centring the title alone would leave it floating over a left-aligned byline, so the whole header moves or none of it does.
It holds at both extremes: a title that wraps to two lines sits over a wider byline, and a short one gets a wider byline beneath it. Either way the lead image below anchors the block. A post with no lead image has nothing under it but body copy, which is the case to look at if this ever stops working. */.post-head { text-align: center; }.post-head .no-justify { text-align: center; }
/* Sits with the title, in the title's voice but quieter. Paine's own pamphlet carries its "Addressed to the Inhabitants of America" the same way. */.post-subtitle { margin-top: 0.5rem; font-size: 1.05rem; font-style: italic; color: var(--ink);}
.post-author { color: var(--title); }/* What kind of author this is. A sentence, so it is set as one — the byline's uppercase letterspaced type is for short fields, and a clause in that type ran to a second line and started it with a stray separator. */.post-note { margin-top: 0.4rem; font-size: 0.78rem; color: var(--ink-soft);}.post-tags { margin-top: 0.4rem; }/* A divider inside a post. Same short centered rule the site uses elsewhere, but with room on BOTH sides: .center-rule is built to tuck under a page title and has no top margin, so reusing it here glued the rule to the paragraph above. */.post-rule { border: 0; border-top: 1px solid var(--rule); width: 34%; margin: 2.8rem auto;}/* Underlined rather than coloured: the byline is already the brightest thing on the line, so the link needs to be findable without adding a second signal. */.post-author-link { color: inherit; text-decoration: underline; text-underline-offset: 3px; text-decoration-color: var(--rule);}.post-author-link:active { text-decoration-color: var(--accent); }@media (hover: hover) and (pointer: fine) { .post-author-link:hover { text-decoration-color: var(--accent); }}.post-image { display: block; width: 100%; height: auto; margin: 2rem 0; border: 1px solid var(--rule);}.post-heading { color: var(--title); font-weight: 700; font-size: 1.15rem; letter-spacing: -0.01em; margin: 2.4rem 0 0;}/* A heading has to sit closer to the section it opens than to the one it ends, or it belongs to neither. It did not: every paragraph carries mt-4, so the gap BELOW a heading was 1rem -- the same 1rem that separates two ordinary paragraphs -- while the gap above it was 2.4rem. The heading read as floating rather than as a division.
Tightening below is the fix rather than loosening above: the space above is doing real work, and matching the two would remove the division entirely. Two class names beat the utility's one, so this wins without !important. */main .post-heading + * { margin-top: 0.6rem;}.post-list { margin-top: 1rem; padding-left: 1.15rem; list-style: disc;}.post-list li { margin-top: 0.5rem; }.post-quote { margin: 1.6rem 0; padding-left: 1.1rem; border-left: 2px solid var(--rule); color: var(--ink-soft);}/* No syntax colouring, so a code block ships nothing beyond this stylesheet. Code is set a step brighter than body copy so it reads as the literal text, with room between lines for symbols to separate. */.post-code { margin: 1.6rem 0; padding: 1rem; overflow-x: auto; border: 1px solid var(--rule); font-size: 0.8rem; line-height: 1.6; color: var(--title); tab-size: 4;}/* Transcript pages (/speaking/): each paragraph opens with a timestamp that is its own anchor, then the speaker's name for a new turn. The CID beside the audio link is for readers with their own IPFS node. */.transcript p { margin-top: 1rem; }.transcript .stamp { font-variant-numeric: tabular-nums; font-size: 0.8rem; color: var(--ink-soft); text-decoration: none;}.transcript .stamp:active { color: var(--accent); }@media (hover: hover) and (pointer: fine) { .transcript .stamp:hover { color: var(--accent); }}.transcript .speaker { color: var(--ink); }.cid { font-size: 0.75rem; word-break: break-all; color: var(--ink-soft);}/* In a caps meta line the address sits on its own line in its real case: a content address is copied character for character, and uppercase changes it. */.post-meta .cid { display: block; margin-top: 0.3rem; text-transform: none; letter-spacing: 0;}/* The table scrolls inside its own box. Letting it widen the column would put a horizontal scrollbar on the whole page on a phone. */.post-table-wrap { margin: 1.6rem 0; overflow-x: auto;}.post-table { width: 100%; border-collapse: collapse; font-size: 0.85rem; text-align: left;}.post-table th,.post-table td { padding: 0.5rem 0.9rem 0.5rem 0; border-bottom: 1px solid var(--rule); vertical-align: top;}.post-table th { color: var(--ink-soft); font-weight: 400; font-size: 0.72rem; letter-spacing: 0.14em; text-transform: uppercase;}
/* Footer: three quiet lines — contact, site nav, build stamp — one spacing rule between them, one step (2.4rem) up to the content above. The build stamp <p> is injected at dist time by scripts/build-stamp.mjs after the last </nav>; its classes are fixed there, not here. */.site-footer { text-align: center; color: var(--ink-soft); padding: 2.4rem 1.5rem 2.2rem;}.site-footer .footer-line { font-size: 0.7rem; letter-spacing: 0.14em; text-transform: uppercase; margin-top: 0.45rem;}.site-footer .footer-line:first-child { margin-top: 0; }.site-footer a { position: relative; color: inherit; text-decoration: none; }/* The footer type is 0.7rem; this invisible box makes each link a 44px target. */.site-footer a::after { content: ""; position: absolute; inset: min(0px, (100% - 44px) / 2);}.site-footer a:active { color: var(--accent); }@media (hover: hover) and (pointer: fine) { .site-footer a:hover { color: var(--accent); }}/* The build stamp <p> is injected by scripts/build-stamp.mjs with a hardcoded mt-3 in its marker string (the marker doubles as the idempotency check, so it stays untouched there). This wins on specificity and keeps all three footer lines on the same 0.45rem rhythm. */.site-footer p { margin-top: 0.45rem; }
/* ------------------------------------------------------------------ *//* Syntax highlighting for the on-chain generator on /art/essentialism/.
Drawn with the CSS Custom Highlight API, which colours live Ranges rather than wrapping tokens in <span>s. That is the reason this approach is on the page at all. The block claims to be the bytes read from Tezos and verified against the code the page just ran, so its textContent has to stay exactly what came off the chain — selection, copy and the comparison all read the same string highlighted or not. A span-injecting highlighter would have made the claim false.
The one component on the site not drawn from the six roles above. Its colours are the generator's own ink library, read out of the very code this block is listing: LIB in art/essentialism/essentialism.js, plus BONE. The listing is painted in the inks the listing paints with.
ink 2 #85dad9 tiffany blue from "together" keywords, storage ink 1 #dd68a4 pink from "together" strings BONE #f3e7d4 svg noise workprint numbers ink 5 #87c2e4 background from "mr. blue sky" functions ink 4 #36597d dark blue from "overhead" comments, dimmed
Red is left alone throughout: it is spoken for by the mismatch state under the block, where it means the chain and this page disagree.
On white the light inks fall under 4.5:1, so each becomes the same hue taken darker, and ink 4 is used at full strength rather than dimmed. The comment and operator greys are tuned for contrast, not sampled - they are the only values here with no counterpart in LIB.
Colour is all there is to work with. Highlight pseudo-elements accept a short list of properties — colour, background, decoration, shadow — and font properties are not on it, since a highlight cannot be allowed to change metrics and reflow the line under it. Italic comments are not available at any price; do not add font-style below expecting it to render. */:root { --syn-keyword: #85dad9; --syn-string: #dd68a4; --syn-number: #f3e7d4; --syn-function: #87c2e4; --syn-property: #8cadd7; --syn-comment: #5f82a1; --syn-operator: #6a7d90;}html.light { --syn-keyword: #1f7a78; --syn-string: #b0356e; --syn-number: #8a6320; --syn-function: #36597d; --syn-property: #4a6d99; --syn-comment: #6b7885; --syn-operator: #6d7681;}@media (prefers-color-scheme: light) { html:not(.dark) { --syn-keyword: #1f7a78; --syn-string: #b0356e; --syn-number: #8a6320; --syn-function: #36597d; --syn-property: #4a6d99; --syn-comment: #6b7885; --syn-operator: #6d7681; }}
#code::highlight(keyword),#code::highlight(storage) { color: var(--syn-keyword);}#code::highlight(string),#code::highlight(regexp) { color: var(--syn-string);}#code::highlight(numeric),#code::highlight(boolean),#code::highlight(constant) { color: var(--syn-number);}#code::highlight(function),#code::highlight(support) { color: var(--syn-function);}#code::highlight(property) { color: var(--syn-property);}#code::highlight(comment) { color: var(--syn-comment);}#code::highlight(operator) { color: var(--syn-operator);}