Shad Abbaslou / Contexts
● Open to global roles
~/colophon
FILE 008
File 008 · How this workspace is built

Colophon

This portfolio is built the way I build products, so instead of describing my standards, it has to meet them. This page is the record of how, and of the versions it took to get here.

One grid  building itself from the left. Run a hand over it.

How this site is built, in three hundred words

The shell is hand-written HTML, CSS and plain JavaScript: no framework, no build step and no cookies, and no analytics but one count on the CV, made without cookies and explained below. Every font, image and script it uses is served from this domain, and nothing is fetched from anyone else while you read. Vercel serves the repository’s portfolio folder as it stands, so what was reviewed is exactly what is served.

The products inside the case files are a different kind of thing, and are built like one. They are React applications on Radix primitives, styled with Tailwind over a shared set of tokens, charted with Recharts and React Flow, bundled by esbuild into chunks they share, and committed beside the pages. They run on fictional data, each case file links the states around its main screen, and nothing they do leaves the page.

Figures live in one file. Each says what it counts, where from and as of when, and the ones counted from this repository carry the command that reproduces them. One suite reruns every command before a release, and another fails if a page states a number the file does not hold.

Nothing ships with a check failing. Seventy-three suites open the site in a browser or read its files: axe-core on every page and every product view, contrast in both settings, layout from 320 pixels up, print, structured data, the captions on every recording, the measurement plan in case file 002, and the figures. Twenty-four of them run on every pull request, and two check the live site each morning.

Every release is a numbered version with its own entry in the changelog, and past entries are never edited. A correction is a new entry, and it names the number or the line it corrected, which is how this page came to say that the token count was once 3,444.

01The product

There is no homepage

One application, one frame, nine files. Move down it: the view takes the open product's colour and the chrome does not move.

A portfolio for a systems designer, shaped like the software I design: a case-file workspace whose navigator, search and keyboard controls persist on every page. There is no "homepage": every URL, this one included, is a file open in the same application. Information first, decoration last.

It's hand-written HTML, CSS and vanilla JavaScript. No framework, no build step, no cookies, and no analytics except a count on the CV. The shell makes no external requests, every font and image it uses is served from this domain, and since v3.2 the work itself lives here too: six artifact sites under /artifacts, embedded live in the case files.

Since v3.8 the products live here as well. Each case file describes a piece of software, so each case file now runs it: four rebuilt applications under /products, each a single self-contained page carrying its own branding, embedded in the file that tells its story. Someone reading about the NHS dashboard can pick a patient and write a session note in the same scroll.

01b · Product inside the product

Case files that run the software

A screenshot proves a picture existed. A working screen proves the thinking behind it.

The shellContextsCool paper, ink and one cobalt. Owns the chrome, the navigator and the story.
The boundaryAn iframeA fixed 1280×800 screen scaled to fit. Neither design system can leak into the other.
The productIts own brandNHS blue, Astrato crimson, Villa terracotta, OI teal, each app looks like itself, not like this site.

The frame is deliberate. Embedding a product by copying its components into the host stylesheet produces a costume: everything ends up wearing the portfolio's typeface. An iframe keeps two design systems honest: the workspace stays cool paper and Bricolage, the clinician dashboard stays NHS blue and Inter, and the seam between them is a one-pixel rule. It also means every product is a real URL you can open, send, or use full screen.

Each product boots only when it scrolls into view, carries a visible demonstration tag, and runs on invented data. No real patient, booking or tenant record appears anywhere on this domain.

02Type & tokens

Three faces, each with a job

Three faces, each with a job. Bricolage Grotesque, drawn wrong on purpose, for display headlines; Inter for interface text; IBM Plex Mono for data, labels and margin annotations. Bricolage replaced Archivo in v6.0: Archivo is clean, wide and neutral, which is what every statement headline on the internet is set in, and neutral is the house style of software nobody chose the type for. There was a fourth face, Instrument Serif, carrying the italic asides; it was the warm voice on a page whose argument is forensic, and it went in v5.1. The Inter-plus-Plex pairing comes from the design system I run at work. This site borrows the habit along with the rules, then puts a louder voice on top.

The tokens below are read from the stylesheet this page loads, at load, so the table cannot drift from it; the values in the markup are the ones it carried when this was last set, and four of them had drifted a version behind before that was true. Change one and the whole site follows.

Icons are not drawn by hand here. The interface uses Lucide for controls and Simple Icons for the brand marks that appear inside the rebuilt products, 116 files vendored into /assets/icons so that, like the type, nothing is fetched from anyone else at runtime. Brand names and logos remain their owners' and appear only to identify the real products these demonstrations rebuild.

TokenValueUsed for
--bg#f1f3f6canvas · cool paper, not screen
--bg-raised#fbfcfdcards and panels
--text#0e131bprimary text · ink
--accent#1a3fb0the chrome accent, each case file overrides it with its own
--snap140mscontrol transitions
--spring280mspanel transitions
--pad24pxcanvas edges
--gap12pxbetween bricks

The system, rendered from itself

Each specimen below is measured from this page as it loads, so a change to the stylesheet changes it here first.

DisplayFile-
SectionFaces-
StandfirstThe argument-
BodyProse, at length-
LabelTYPE & TOKENS-
--snap -
controls answering a press
--spring -
panels arriving, a little past and back
--r-s -
--r-m -

--line, between parts

--line-strong, where it must be seen
03Colour

One hue for the chrome, and a reason for every other

The site is cool paper, ink and a cobalt, and every other colour on it has to argue its way in. This is the argument, with the values the stylesheet actually carries.

The accent is one hue, used for one job. Cobalt: #1a3fb0 as a mark and a button, #17399a as text, because the same hue has to drop until it carries 4.5:1 on the sunken well. In the dark it is lifted to #6b96ff and #8fb0ff, because chroma reads darker on ink, and a colour that keeps its lightness across the switch is the same colour to the eye where the same number would not be. It is the colour of a thing a hand can act on: a link, the lit pill in the section bar, the live hint on a caption, the one hot point in a drawing. It is never a decoration.

The hot mark is a sibling, not the accent. The drawings mark exactly one thing per screen, and that mark is #1f45c4, the accent's hue a step lighter and more saturated, so a reader sees a different object from a link while the page stays in one family. The rules suite counts the hot marks on every screen.

On a dark ground the accent is lifted, not swapped. A ground section keeps 64 parts of the accent base to 36 of white for a mark and 55 to 45 for text, and the bands and invert suites measure the result against the ground it sits on, so a chip or a link on ink carries the contrast it carries on paper.

Five files, five hues, none copied. Each case file wears a hue its client's own identity suggests and none of their marks: teal for the design system, violet for Astrato, the NHS blue, a clinical cyan for Novo Nordisk, a forest green for JBS, each with its dropped text pair and its dark lift. The skin colours the file's chrome and its product's frame; the workspace around it keeps its cobalt, which is how a reader can tell which is the site and which is the work.

Red and green mean a direction, nowhere else. The products carry an up and a down for a number that moved, and a warn, and they appear only inside the product frames beside the figure they describe. The site itself has no red: the vermilion accent of v6.0 and Astrato's crimson both went in v7.22, for the reasons above.

Every pair here is measured, not asserted. contrast checks every skin in both themes, invert the inverted grounds and bands every band a label can land on, all to WCAG AA, and a change to any value fails the build before it ships.

  • Cobalt, the accent#1a3fb0 mark · #17399a text · #6b96ff dark
  • The hot mark#1f45c4 · #6f9bff dark · one per screen
  • 001 · teal#0f9887 · #1daf9c dark
  • 002 · violet#5b3fc4 · #b49cff dark
  • 003 · NHS blue#0e5fbf · #3b8fd9 dark
  • 004 · cyan#0d7d9e · #3fc3e8 dark
  • 005 · green#1a6139 · #44b573 dark
04House rules

Eight rules, checkable on this page

Ninety-one numbered slots, eighty-nine live rules. Two were retired and their numbers kept vacant, so no rule number is ever reused. Hold one for its number.

The site runs on eight rules, borrowed from the 91-rule system documented in case file 001. Here they can be checked against the page you're reading.

  • One accent per view, and the view follows the accent. The workspace is a deep cobalt on cool paper (vermilion on cream from v6.0 to v7.21, cobalt on cream until v7.46); opening a case file re-skins the whole application in that product's palette, taken from the deliverable rather than picked nearby: OI teal #0f9887, Astrato violet #5b3fc4 (the deck's plum, crimson until v7.22), Safe Space NHS blue #0e5fbf, Novo Nordisk turquoise #0d7d9e, JBS forest #1a6139, surfaces and all, and never more than one at a time. Open any case file and read --accent off the root.
  • A product keeps its own skin. An embedded application never borrows this site's type or colour; it runs behind a frame, branded as itself, or it isn't the product.
  • Motion only when a hand causes it. Nothing on this site animates unprompted.
  • Mono for data, never for prose. Labels, figures and captions sit in Plex Mono; sentences sit in Inter.
  • Every number carries its source. Inline where it can, in the source notes where it can't.
  • Spacing in 24/12 bricks. Canvas edges at 24px, gaps between bricks at 12px.
  • Themes cost zero component code. Light and dark are a token swap. Press t.
  • One hot mark per screen. The drawings use a single deep blue, #1a3fb0 (vermilion until v7.22), and it marks exactly one thing: whatever a leader line is pointing at. Two hot marks and neither is marked. Per screen is not per page: where a file carries two drawings they sit more than a screen apart, which is measured rather than asserted (case file 001's are 3,982px apart against a 900px viewport). Because it is a drawn marker it answers the 3:1 a graphical object needs, not the 4.5:1 type needs, so anything actually set in it uses --hot-text at #bb3410, measured against the worst surface it can land on.

What the battery checks before a version ships

Seventy-four suites, each a script that opens the site in a browser or reads its files, and fails the build on the first thing it finds. Their names are the ones the changelog uses.

SuiteWhat it holds the site to
figuresevery number on the site agrees with the canon in figures.js, and a superseded or contested figure fails
dimsevery picture declares the width and height of the file it points at, and no two pictures on a page are the same file
socialevery page unfurls with a title, a description and a share card that exists
nestingevery page closes every element it opens
linksevery link and asset reference resolves the way the deployed site resolves it
twicenothing is offered twice within one screen on any page
sweepevery page at both widths: no script errors, no failed or external requests, no sideways overflow
nojsevery page still reads with scripts off
clipno text is clipped at any width
boxesnothing draws a box that the house allow-list does not know
shapeevery picture is shown in the shape it is
edgesevery border drawn is visible against its ground
rulesthe site keeps the rules this page publishes: one hot mark per screen, and no second one in the markup
microthe small print, the status bar and the chrome say what they should
contrastevery file skin passes WCAG AA in both themes
invertthe default palette and the inverted grounds both pass AA
bandsevery run of text on a ground band reads at AA or better
dossierthe About dossier holds up in both themes
paperevery ground reverts to paper for print, with no near-white text left on it
printedevery page still means what it says once printed
stripthe landing’s case grid, directly under the hero: every file’s mark, summary, contents and tags, the hiring question, the internal products and their flags, and cards that turn softly on a hover, a tap and a key with the back inside the card
playevery hero plate answers the hand
secplayevery section plate is there and answers the hand
enterthe keyboard: the palette, the theme switch, the single-letter shortcuts, and nothing fires while a control is focused
navthe navigator lists every file and opens each one
navstatethe navigator remembers its state and reflects the page
anchorsevery section heading lands clear of the sticky chrome
deeplinkevery deep link lands on its section, clear of the chrome
notesthe margin annotations sit square, beside their paragraph, uncovered
inlineevery inline link in prose is distinguishable from the prose
touchevery plate answers a finger
inkevery label drawn into a plate stays on the plate
plateclashno label on any plate draws on another
svginkevery label in every drawn figure carries against its ground, both themes, and no class paints nothing
fignumfigure numbers run in document order on every case file, none repeated, no shared title
claimsno page states the same fact two ways, and each case file agrees with its own artifact
canvasesevery canvas with a box has been sized and drawn into
scrollanimon a phone every drawing is driven by the scroll and holds still otherwise
perfevery page opens inside its byte, request and iframe budgets
overprintno header text is printed over its drawing
narrowno page scrolls sideways at 320 pixels, the smallest phone still in use
a11ykeyboard, skip link, focus, heading order, reflow at 200% and target sizes, beyond colour
foldthe value line is on the first screen on a desk, a laptop and a phone
readtimeevery case file quotes the minutes its words and figures add up to, and the skim folds what the count assumes
frameevery case file says what it is, for whom, how long it takes, what I owned and with whom; every card carries one outcome; the now line is fresh
jsonldone structured-data graph about one person, and every node agrees with its page
asofevery block that states a figure counted from the repository says when it was counted
samplessmall samples read as counts, and a share whose base is not given says so
scrollcosta full scroll of the landing stays under 1.5MB and boots no product nobody reached for
lighthousethe landing scores at least 80 on a phone and 95 on a desk, served compressed as it is deployed
productsevery control in the products does what it says, the interaction suite the case files cite
bundlesevery product boots from the shared chunks and renders clean
imagesevery picture offers AVIF first, at 2x where it was shot at 2x
labelsa case file labels in one system: the section, the figure and the caption
emphasisone bold run in a paragraph at most, and never bold and italic at once
forcedunder a forced palette, in both schemes, every shape, every state and every focus ring still reads
floorno text under 11 pixels on a phone, figure labels included, and the desk and paper keep their drawn sizes
cornersevery drawn phone keeps its screen inside its bezel, standing and leaning toward the hand four ways
pdfsevery case file links the PDF its page prints today, page for page, with its pages and size
tracedevery decision a case file draws from its research holds in the running product, opened at the state the case file links to
onerowevery case file’s section bar is one row at six desk widths, each name in the row or under More
axesiteevery page passes axe-core’s WCAG 2.1 A and AA rules, at desk in light and on a phone in dark, and the statement says what it ran
axeprodevery running product, and every state a page links into, passes the same rules at both widths
chartsevery chart in the products reads 3:1 against its card, or prints the value of every mark, in both settings
platformevery control in the three phone apps is a target of at least 44 pixels
recountevery derived figure in figures.js comes out of its own command, run from the repository root, and every figure a page places by name prints the canon
clipsevery recording on a case file plays only when pressed, and its captions, its transcript and its caption line say the same thing, timed to the same second
trackedthe measurement plan on case file 002 is the one the Astrato rebuild runs: every event fires, no call breaks the plan, no question’s words reach a call, and both arms of the test open as designed
budgetevery product’s first visit fits its budget in kilobytes, the products build fails past it, and every case file prints the weight it measures
headersevery path is served with its security headers, the policy written is the one the pages need, and every page runs under its Content-Security-Policy without a violation
livethe site at withcontexts.com is main, byte for byte, page by page and script by script, the notes kept beside the pages are not served, and the CV’s counting script sets no cookie and keeps nothing; run every morning
rebuiltthe committed product bundles are the ones their source builds, to the byte
flowsthe portal, the diary and the carers’ app each do the job they exist for, start to finish, focus returned where a layer closes
countsthe CV counts what the privacy section says, once a visit, with no cookie and nothing stored, and nothing is counted on another page, on this machine, against Global Privacy Control or Do Not Track, or after the reader says no
05Figures

Every number on this site, and how it was counted

House rule five says every number carries its source. For a year that was a promise kept by hand, and by hand it was not kept. The component library appeared on this site as 216 on the landing screen, 216 three times on case file 001, 220 further down that same case file, and 214 inside the product demo under the words one source of truth. Three numbers, one library, two of them on one page.

None of them was invented. Each was true of a different count taken at a different time, by a method nobody wrote down, and because nothing was watching they drifted apart where anyone could see. That is the exact failure a design system exists to prevent, happening to a portfolio whose argument is that design systems are worth having.

So the figures live in one file now, /assets/figures.js, and the table below is rendered from it: the page cannot disagree with the canon because the page is the canon. Every figure carries a definition, a source, the date it was counted, and, where the thing is countable from the repository this site lives in, the command that reproduces it. Run the command, get the number. A test reads this file and every page on this site, and fails the build when a page states a figure that disagrees.

The weaker figures are marked attested. They come from a document rather than a count I can re-run, which is a real difference in how much weight they will bear, and hiding it among the derived ones would be the same mistake in a quieter form.

What the drift actually cost. Nothing, yet, and that is luck rather than process. A hiring manager who counted would have found a portfolio arguing for canonical truth whose own canon had three values, and the charitable reading of that is carelessness. The uncharitable one is worse. The fix is not that the number is now right; numbers go stale on their own. The fix is that the next time one goes stale, a test says so before a reader does.

06Changelog

Shipped, learned, logged

Ninety versions, each as tall as its entry in the log below; a square marks a new major. Run a hand along them.

Every entry is a headline sentence; the newest is open.

v7.58NOV 2026
The Astrato deck told in pictures: the problem set on the tangled canvas and answered on the ordered one, the test sessions and recordings from the original deck with every face blurred, the two pods as a constellation with the designer between them, and the product toured at the end rather than only run.

Shad on 11 November: the Astrato deck was walls of text. He asked for more of the AI story, a telling that is easier to follow, the problems that came up and how they were solved, pictures so that it looks like a presentation, the user-testing and interview pictures from the original site, his own part and the collaboration, the brief, what was delivered, and the finished product made far better. The deck, forty-eight slides now, is rebuilt around that order: the problem, set on the canvas as it was found; the evidence, six sessions watched; the answer, the geometry first and the assistant that shows its SQL; what shipped; the product, toured. The rebuilt product itself is on six boards, photographed in its states, with the spec line each state answers to; on the tour it boots itself when the board is reached. The research has a chapter of its own: the programme, four of the sessions, both recordings, each heatmap on its own board, the task-difficulty rating with its interval, and the table of what was asked and found.

The pictures are the work’s own. Six come back from the original 2025 deck, out of the site’s own history: the join canvas as it was found, the six UserTesting sessions, two recordings with the moderator’s notes beside one, two attention heatmaps over the canvas, the Insights panel in three frames, and four panels of the scope of a question being refined. The faces of the participants are blurred in the files themselves, as the site’s rule on people who never agreed to appear requires. The words are still the case file’s, read by selector as before; a picture’s alt says what it is of and nothing the file does not say.

Four new kinds of slide. A picture that fills the board, with the file’s line on it in white or beside it in a column, drifting slowly and leaning toward the hand; the crew, every person in the two pods a point, the designer the one point both pods share and a line from him to each of them, with the counts counting up; a table as one card a row, each with its status; and the tour, the product running with four stops above it, the workbook, what shipped and when, the join canvas, and Insights with its SQL, each a button that puts the product into that state with the file’s own caption under it. The stop keeps the focus, so the deck keeps its keys.

The constellation. Behind the cover, each door and the close, the site’s own copy of three.js draws the tables and joins of a model as a hundred and twenty points and their lines: tangled on the Discover door, long lines in the red ink crossing anything; in order everywhere else, each point joined to its two nearest neighbours in the phase ink. It is built when its board is first reached, runs only while that board is on screen, is rebuilt when the theme flips, and is absent under reduced motion or without WebGL. On a phone the deck is a document, the pictures above their words in the page’s own colours, and no constellation is drawn.

Not in it. How the client was kept informed is not in the case file, so it is not in the deck; a deck cannot say what its file does not. The pictures are all of the work: none is bought or borrowed.

v7.57NOV 2026
The decks from every page: Present in the bar opens a list of the five case files as forty slides, and the navigator carries them too.

Shad on 3 November: a way to the presentations on every page, not only from each case file’s own bar. The bar of every page that has one now ends in Present, which opens the five decks by number and name; it is a details element, so it opens without script, and a click elsewhere or Esc closes it. The navigator gains a Presentations group under the case files, one row a deck.

v7.56NOV 2026
The phones keep their corners: a product running in a drawn phone no longer shows its own square corners past the bezel while the phone leans toward the hand, the island no longer sits on the app, and on paper every phone is whole.

Shad’s screenshot on 2 November: the clinician tool running in the phone beside “On a phone” on 003, leaning toward his pointer, had a grey square standing out past the bezel at each of its four corners. The screen is the product at 390 by 844, scaled into a round rectangle. v7.27 clipped it with a radius and a clip-path, which holds while the phone stands still. v7.48 made the phone lean toward the hand, which draws it in 3D, and there the browser lets a round clip on a running frame fall back to a square one, so the product’s own corners showed past the bezel’s.

Every drawn phone on the site was found and leaned. Seven run a product on the case files, the large one beside “On a phone” on 002 to 005 and the three apps on 003; seven are in the decks; one is inside the clinician tool, running the young person’s app. Only the four large phones spilled, in sixteen of fifty-six leaning views. The decks’ phones hold pictures, which keep their corners, and the clinician tool’s phone does not lean.

The screen is now masked to the same round rectangle as well as clipped. A mask is a layer of its own, which the 3D drawing keeps, and this one is solid, so only the radius cuts. A seventy-fourth suite, corners, finds every page with a drawn phone, puts the pointer on each bezel’s rim near each of its corners, checks that the phone leaned, and reads the pixel halfway between the screen’s curve and the bezel’s: bezel where the corner holds, the product where it spills. With the old rule it fails on the same sixteen views; with the new one all fifty-eight pass, the clinician tool’s phone read standing at desk and phone width.

Two more things the same screenshot showed, once looked at. The island sat on the app. The diary and the parents’ app draw a status bar of their own and the island falls in it, but the clinician tool, the older adults’ app and the products on 002, 004 and 005 do not, so it covered the end of their titles and the bell beside them: “Clinician da”, “Q3 Workbo”. Those five now keep the strip a phone keeps above an app, coloured from the app’s own top once it has loaded, so the strip and the header read as one in both settings, and the app starts under it. The island and the strip are drawn to the phone’s width now, as a phone’s are; at a fixed 90 by 24 pixels the island had covered the diary’s own greeting on a phone printed smaller. And on paper the three apps on 003 printed too large and cut off at the right of their phones, because the frame is fitted to its bezel by a script that does not run again when a page is laid out for print. On paper a phone now shows its still, the same opening screen, and the 003 PDF is rebuilt with them whole.

v7.55NOV 2026
Every case file as forty slides to present: the problem, the answer and the product running at the end, told in the order of the double diamond, opened by a link and walked a point at a time, with a speaker window that keeps the notes and the clock.

Shad’s brief on 2 November: for every project, a forty-page case study he can open by a link and present in an interview, the problem, the solution and the double diamond, full of small motion, with examples of the product and the finished product at the end. Five decks, at /present/ and each file’s name, two hundred slides.

Nothing in them is new writing. tools/build-decks.mjs reads every heading, line, figure, table, drawing, still and clip from the case file it belongs to, by selector, and stops if a selector finds nothing, so a deck cannot say what its file does not. The only words it supplies are the names of the phases, what each phase is for and the labels on the controls. A sentence that tells a reader of the page to drag or scrub something is dropped, since a slide has nothing to drag. Every slide carries speaker notes, the file’s own longer prose for the section it comes from; a drawing’s notes are the description the file already gives it for a reader who cannot see it. 004 and 005 carry the reconstruction note on their first and last slides, and their last phase claims no outcome.

The order of telling. Six slides of context: the cover, the short version, the outcome up front, a map of the two diamonds with the slides in each, the brief in three lines and the product in motion. Then Discover, Define, Develop and Deliver, each opened by a door that lists what is in it, then the finished product, booted inside its slide, and Questions. The map says plainly that the double diamond is the order of the deck, not a claim about the order the work happened in; the case file keeps that.

Presenting. P fills the screen. The arrows walk a point at a time where a slide has points, the earlier ones stepping back, and shift with an arrow skips them; a number and Enter go to that slide; O shows all forty at once; N shows the notes; S opens a speaker window with the slide, the next one, the notes and two clocks, which follows the presenting window and can drive it; B shows every point at once; T switches between light and dark; Esc returns to reading. The address carries the slide, so a link opens on it.

What moves. Headings arrive a word at a time; figures count up to themselves with their separators kept; each drawing draws its strokes, then its labels; the token chain’s bars and the survey’s bars grow; the before-and-after handle on 003 shows once that it moves; frames round the products lean toward the pointer and a soft light follows it; stills and drawings open full size, a still with a link into the product in that state; the walkthroughs play when their slide arrives and stop when it leaves. Reduced motion stills all of it, and without script a deck is a plain column of slides with everything showing.

Where it reads. On a desk the slides are 16:9 boards sized in container units, so the same markup is a page, the whole screen and a thumbnail. Below 1100px the boards let go of their ratio and become a document with fixed type, the drawings scrolling sideways as they do in the files. Printed, a deck is one slide a page. Each case file’s bar has a Present link beside the product.

Checked by photographing all two hundred slides presented at 1280 by 720 and measuring each for anything that spills off its board, and by pressing through a deck: P, the arrows, points, a slide by number, the notes, the before-and-after handle, a drawing and a still opened and closed, the overview, the product booted in its slide, and the speaker window following and driving, with no page errors. The decks joined the accessibility audit, which found the phase colours too faint as small type, the double diamond’s links held inside something announced as a picture, buttons whose spoken names did not match their words, and wide tables and drawings that scrolled on a phone where a keyboard could not reach them. A phase colour set as type is now pulled toward the text until it reads at 4.5:1, a table or drawing takes the focus and scrolls by arrow, a drawing opens full size on Enter, and all five pass at desk and on a phone.

v7.54OCT 2026
Every page walked through every moving part, on a desk and a phone, and what was broken mended: a page that shook with no hand on it, drawings that stated counts they had never read, demos a phone could not see, and the parts that moved the page under the reader.

Shad’s brief on 31 October: page by page, case file by case file, look at every animation and interaction, see what is broken or wants replacing, and fix it. Each page was photographed a screen at a time on a desk and a phone; every moving piece was parked and photographed on its own; every control was pressed; and every page was scrolled by a real wheel with the browser’s record of layout shifts running. In order of harm:

A page that would not sit still. The width axis that narrows the display type while the page moves could change a heading’s number of lines. On 002 that moved the page, scroll anchoring moved it back, Lenis read the correction as a scroll and narrowed the type again: with nobody touching it the page jumped 59px about once a second, a layout-shift score of 19 over one scroll. The same reflow broke a heading on Practice onto a second line mid-scroll. Type that wraps now takes the motion as a horizontal scale from its left edge, which cannot move a line; the section number, which cannot wrap, keeps the true axis; the pulled quotes, which are paragraphs, take neither. 002 now scores 0.0001.

Drawings that stated what they had not read. The ledger over every case file’s table of fixes drew nine rows of seeded random lengths whatever the table held: seven on 001, six on 002 and 003, five on 004 and 005, where it was captioned five decisions. It is a scene now that reads the table under it, crossing each row off as the page is read and ending on the row’s own figure; a hand on a row lights it in the table. The colophon’s versions, captioned as drawn to the size of each change, had random heights; each bar is now as tall as its entry in this log, with a square under each new major and the version named under the hand. The rule book drew 93 slots under a caption of ninety-one; it draws 91. On a phone the lattices of people and rules lost their last rows to the hole cut round their notes, so Safe Space’s ninety-two people drew as seventy-five and 001’s ninety-one rules as fifty-two; they draw whole. The landing’s shelf said four artifacts under five spines. The memory on 001 is captioned as the diagram it is.

Hidden or broken on a phone. The before-and-after, the dependency ladder and the join geometry showed only their headers and captions on a phone, “Drag the line” over nothing, because the rule that sets the product frames aside under 760px took them too. The first two run on a phone now, the board’s cards two by two and its pins placed for them, the ladder’s rules under each layer; the join geometry, an 800-unit drawing whose labels came out under 5px there, is set aside on a phone whole, the way the products are, and no demo is printed, since paper has no hand. The labels on About’s figure and on Work’s lineage were under the 11px a phone is held to; they are not. The governance matrix’s labels ran through its first two columns and its foot off the edge; it is taller there, its labels fit and its foot is two lines. The shell plate printed its sub-line through its title. A case card carried 85px of nothing when its back was the taller face; its picture takes the room. Every case plate kept an empty band under its notes.

What moved the page. Work opened 10,464px tall and fell to 4,081 the moment it was scrolled: the lineage was laid out only by the sheet its engine loads on demand, so until then its rows were five full-size stills, and without scripts they stayed that way. Its layout is in the sheet every page carries now. A figure counting up held its stat at a different height as its digits ran, moving the text under it four times in a second on 004; it is held at its finished height while it counts. The CV’s print bar hid its note when it stuck and took 25px out of the page under the reader; the note sits under the bar.

Smaller. The pulled quote on every case file had its dither cloud painted over the sentence instead of under it. The after side of the before-and-after carried its notes in the page’s paper ink on a near-black board. The Storybook opened on a colour story whose panel said only that it had no controls; it opens, and its still shows, the Switch docs page the file already links to. The landing’s shelf is a shelf’s length instead of a band of empty panel. Two vendored majors of motion were both labelled motion. Every page logged a header warning for a browser feature Chrome does not know.

v7.53OCT 2026
The scenes redone, by Shad’s word that the idea was good and the execution was not: the AI chapter’s sentence types into a prompt box and fills an app window slot by slot, the landing’s five products stand up as their real stills, About’s line bends one session at a time, Work’s lineage is wired out of each case file, and a section’s number rolls in once instead of standing behind it twice.

Shad’s word on v7.52, the same day: the idea is good, the execution is trash. The photographs agreed before anything was touched. The AI chapter’s leaders tangled through the prompt they came from and its window stood half empty; the landing’s windows were a hairline knot in the middle of a grey panel; About’s drawing read as a stock chart with a second, ghostly 01 through its heading; the lineage was an empty box with half its links ending in the air; and every finale landed under the sticky bars. All four were drawn on canvases in the system’s monospace. v7.53 draws them as real DOM and SVG in the page’s own type and tokens, so a ground and the dark theme reach them without a line of script, finishes each one where the reader can see it finish, and lets nothing move by itself: the scroll draws, the hand lights, and nothing runs on a timer.

The AI chapter. The prompt quoted on the page types into a prompt box. The window beside it opens a list page’s slots as the first clause lands, and each clause after it sends a pulse from a numbered port on the box’s edge to the window, where its slot flashes and fills with the component it asked for: the breadcrumb, the title and its count badge, the subtitle, three KPI cards, the six-row table, then the names and the mixed statuses in its columns. Under the box the pipeline’s own steps from FIG. 005 run and tick, and the verifier’s cold read stamps the finished page. Hold a clause and its slot and wire light, or hold a part and its clause does. The landing. The five products, as the same small stills the grid above already loaded, stand up off one gridded ground one after another and are named by their case files; hold one and it lifts. About. On graph paper that fades at its edges, a dashed line for taste; nineteen sessions land along it one by one and each pulls a second line away from the first, until the gap between them is hatched and marked where they contradicted it. A diagram of the idea, not data, and the caption says so. Work. The lineage is real markup, readable with no script: each case file is the hub of its row, what it handed over on its left and the product rebuilt from it on its right, in the file’s own colour, with the wires grown out of the case file as the page is scrolled; on a phone it is a tree.

Every section. The second copy of the section’s number is gone. Its own number in the rail rolls in like an odometer as the section arrives, a reel per digit, the second a beat behind the first, and the plain number is put back the moment it stops; the rail’s rule draws across under it as the section enters. A figure taller than the screen finishes when its foot is in view, and the landing’s labels, which under reduced motion all stood on one point, are measured again once the cards have their places.

v7.52OCT 2026
The scroll is the pen: four scenes drawn by the reader’s own scroll on every pointer. On the AI chapter a sentence is typed out and assembles into the page it describes; on the landing five products stand in depth on one ground; on About the line taste draws is bent by nineteen sessions; on Work the fifteen files are a lineage. And every section now arrives under its own numeral.

Shad’s brief on 30 October: the best illustrations the site has had, an animation for the AI chapter, and a reader who goes wow at each section. The answer is one engine, scenes.js, under the law of v7.48: no library, nothing on a timer, the hand and the scroll the only things that move it. A scene is a drawn plate, hairlines, hatching, mono labels, whose state is where it stands on the screen: nothing while its top is at the bottom edge, whole once it has climbed most of a screen, and it comes apart again when the reader scrolls back, on a desk as on a phone. Stop and it holds, which the scroll suite reads byte for byte. A hand over it lights a part and names it, a finger is a hover, and while nobody is over it the page’s own travel runs a hand across it. The engine is fetched as the first scene comes near, so no page is heavier at open.

The AI chapter. The prompt quoted lower on the page, read from that one element, is typed by the scroll, and beside it the page it describes assembles as each clause lands: the shell, the breadcrumb, the title with its count badge, the subtitle, three KPI cards with their figures and deltas, the six-row table with the names and the mixed statuses it asked for. A leader joins each clause to the part it produced; a column the prompt names but gives no values for is drawn as a value bar, not a number nobody asked for. The verifier’s cold read stamps the end: no colour, no spacing, no font in the ask, which is Rule 4, as the page says. The landing. The five products the lede names stand in depth on one ground, each with a sketch of its own interface, raised out of the floor by the scroll and named by the Work shelf’s own line. About. A drawing of the first principle, not data: a dashed line for taste, nineteen marks for the nineteen sessions, and the line drawn through what they said. Work. The fifteen files in three columns, a case file joined to the product rebuilt inside it and to what was handed over; two of the artifacts stand alone, and the drawing says so.

Every section. Its number, huge and faint behind its heading, moves up as the section enters, so a reader arrives at each section under its own numeral: a view timeline, transform only, from the rail’s own number. The foot’s rule draws itself across as the foot comes in. A scene near the foot of a page can never climb a whole screen, since the scroll runs out first, so its climb is cut to what the page allows and it is whole when the page is at its end. The CV keeps its rule and takes none of this; it is a document of record.

v7.51OCT 2026
The v7.50 count corrected: the speculation rules it claimed as new have been on every page since the recruiter round, so the shared pieces are thirteen, not fourteen, and each page’s count is one lower.

The first cut of v7.50 added a rules script to every page behind a guard that skipped any page already carrying one, and every page already did, since the recruiter review round: the next page is fetched when a link is hovered and rendered when a pointer goes down. The guard did its job and the entry claimed the piece anyway. The counts in the entry below are now the true ones, forty-five on the landing, forty-two on Work and on About, forty on the CV, fifty-one on a case file, and the rule the mistake left is written down: the inventory, this changelog included, is read before a piece is counted.

v7.50OCT 2026
Forty things on each primary page, by Shad’s brief: the scrollbars and the selection take the site’s ink, the keyboard gets what the hand gets, going back slides the file the other way, a spotlight follows the hand across the dark bands, a question mark opens the keys, a sheen crosses the pointed card and its back arrives row by row, the segmented filter’s thumb slides, and a recording can be watched while reading.

Shad’s brief on 29 October: forty cool things on each primary page. The law is v7.48’s: the platform, not a library; each piece behind the engine that has it; driven by the hand or the scroll; nothing on a timer; ink, never opacity; and nothing moving once the page has painted. Thirteen pieces are new on every page and the rest are each page’s own, so a page’s count is the shared pieces plus its own, each counted once per page it is on: the landing forty-five, Work forty-two, About forty-two, the CV forty, a case file fifty-one. It weighs thirty-four kilobytes of stylesheet and script across the site, uncompressed, and the one case file that drew a field at open now takes that engine on demand like the rest, so every page still opens inside the budget v7.49 restored.

On every page. The pane’s scrollbar is drawn in the site’s ink, and the selection is the accent on every ground. Every piece that answers the hand now answers the keyboard too, a focus twin outside the hover query. Going back slides the file the other way, a type the two documents agree on from the navigation’s direction. On a touch screen a pressed card or row compresses under the finger and the finger’s own flash is off. A spotlight follows the hand across the dark bands, the on-ground ink at a tenth under the band’s content. A question mark opens a sheet of the keys the navigator has had since the workspace took them (j, k, Enter, the slash, t), a native dialog with a blurred backdrop, and the question mark keeps their rule: a single key is live only while nothing on the page has focus. A reader asking for reduced transparency gets solid blurs, and one asking for more contrast gets the strong lines and none of the dimming. A deep link lands with a wash, the heading in the accent settling to ink. The pane keeps a stable gutter, so a shorter page never shifts sideways; figures that sit in columns are tabular; the focus ring settles on the spring; and the version in the status bar opens its own entry here.

The landing. A sheen follows the hand across the pointed card, and its number takes the accent and steps forward; the card’s back arrives row by row when it is turned. The answer line arrives anew with each press. Start here counts in padded mono. The proofs recede round the pointed proof and its unit lights; the threads keep their ink round the pointed one; a fact’s figure and the bio window’s title take the accent; a Start here row lights its label; and the hero’s kicker is decoded on arrival. Work. The sheen again; the card lifts a hair and its number takes the accent; the grid’s titles recede with its stills; the foot’s links lift; the segmented filter’s thumb slides to the pressed name on the spring; and the arrow keys walk the grid. About. The id fields recede round the pointed one, the logos go grey round the pointed logo, the sources recede round the pointed source, a plate number steps forward with its light, the foot’s role lights with the name, a drop cap opens the first section, and the seek line’s key is decoded on arrival.

The CV, still by its own rule, takes hover and keyboard states and craft: the print bar stays in reach as the sheet scrolls and condenses when it sticks, the name is trimmed to its cap height, the bullets and references wrap pretty on screen, the selection is the CV’s own accent, the bullet under the hand keeps its ink, the tenure’s years light with the bar, a degree takes the accent, the proofs recede and the pointed proof’s bar grows, a skills line’s lead word takes the accent, a still’s caption lights with it, a reader asking for more contrast gets the tenure bars in full ink, and on a phone the print bar offers Share. The case files. The section bar’s names take full ink while the bar is stuck, and on a phone the bar snaps pill to pill. A recording can be watched while reading, in a picture-in-picture window, and the file can be shared from its foot on a phone. A hand-written note takes the accent and its signature lights; a note’s number steps forward; a pass lights its rule; the HUD notes’ figures take the accent while the hand is on the figure; a see-also card lifts; the checks and the decisions keep their ink round the pointed one; the sources recede; and on 001 the chain bars fill as the scroll brings them in.

v7.49OCT 2026
The drawing engines load when what they draw comes near, not at open: the landing opens a tenth lighter on a phone and the case files drop five requests each, the ruler is fetched only on a desk, a recording’s poster only when its clip is near, the value line stays on a laptop’s first screen, and nothing on a page moves once it has painted.

Speed first, as the brief said. v7.48 found the two phone weight budgets red on main, where the suite that holds them is not in the pull-request group; this version takes the weight down instead of raising the line. The heaviest script on the site, the plate engine at 96KB, was fetched at open by the landing for one drawing at the foot of the page, and the lattice, callout and dither engines by every case file for figures screens away. Each is now fetched when the first thing it draws comes within about a screen and a half of the viewport, and starts the moment it lands; a page that needs an engine at open, as a case file needs its hero plate, keeps the script where it was. The ruler down the right edge is loaded only where it is shown, from 1080px, and never on the 404, which was built light on purpose. A recording’s poster was an image the browser fetched at open however far down the clip sat, whatever preload said: it is held back until the clip is near, and handed to the printer at once. The demo script leaves the two case files that have no demo.

The landing opens at 0.97MB over 28 requests on a phone, from 1.07MB over 30, and at 1.00MB on a desk, from 1.10; case file 001 at 1.18MB over 28 on a phone, from 1.22 over 33. The budgets are back where they were set. And at 1280 by 720, a laptop, the hero’s value line had run 21px past the fold since the slogan grew; where the screen is short the slogan is a size smaller and the band’s paddings a step tighter, so the first screen says what it is for again.

And nothing moves once it has painted. Lighthouse scored a layout shift of 0.17 on every run on a phone and blamed a thumbnail; read with the browser’s own Layout Instability API, shift by shift with its sources, it was the top bar. The search button was styled only by the sheet the palette script adds when it runs, so until then it painted as plain text, wide enough to push the right-hand group onto a row of its own, and the whole page climbed 15px when the script landed. Its rules live in the first stylesheet now, and the palette’s sheet arrives on first open. The same reading found two more: on a desk whose first paint beat the script, every work card painted with both faces stacked and the grid collapsed a moment later, so the no-script layout is keyed on the browser’s own scripting media feature instead; and on every case file the read-time line grew from one row to two when its buttons arrived, so it reserves their height. The landing, the projects page and the five case files now record 0.000, on a phone and on a desk.

v7.48OCT 2026
Every page answers the hand and the scroll in twenty or so more ways, none of them a library: a card’s title grows into the file’s headline, the question’s answer slides into place, the section bar’s pill moves, the prose focuses on the paragraph under the hand, and three pages drop scripts they never used.

Shad’s brief on 28 October: make the portfolio cool, twenty things on every page, speed first in every step. The research came back the same way on every count: the fastest animation library is the one not loaded. So the whole of this version is the platform itself, gated behind the engine that has each part, each a function of the reader’s own scroll or hand, nothing on a timer, nothing looping, and under reduced motion none of it runs. It weighs about nine kilobytes of stylesheet and script across the site, and About loses a hundred and fifty kilobytes and two requests it was spending on a drawing engine with nothing to draw; the landing loses a plate engine and a callout engine it never used, and the 404 a clock it had no face for.

On every page. Opening a case file from a card on the landing, the Work page or the 404 grows the card’s title into the file’s headline, through the cross-document view transition the site already ran; from one case file to the next, the headline itself moves. The panels, the toast and the pointer ring settle on a damped spring curve. The sun on the theme switch turns toward the hand and the wordmark’s accent dot walks a cell. The navigator’s rows, the shelves and every table recede a step round the one pointed at, in ink, never in opacity. An opened entry breathes in. Prose wraps so no line is a word on its own, and the paragraph under the hand keeps its ink while the rest of the prose recedes. A section’s number lights while the hand is in it, its foot’s arrow leans toward the next, a headline’s full stop lands half a second after the page, and the kickers and the hero’s rail leave with their band as the scroll takes it. The controls a script shows arrive instead of appearing. The inline links’ underline rises to the word.

The landing. The slogan leans away from the pointer while the field leans toward it. Press a question and the cards slide to their new places instead of jumping. The pointed card keeps its colour and the rest of the grid loses some. The scope, the Start here list and the proofs arrive row by row; the proofs’ figures and the cards’ outcomes count up; the threads’ numbers step forward; the bio window tilts a degree. Work. The filter slides the cards too, the window with the running product tilts toward the hand and its lights come on, a still swells a little when pointed at and the directory’s section lines are decoded. About. The identification card’s lines decode on arrival, the card tilts toward the hand, its meter fills, a phosphor line crosses the panel with the scroll, the facts and the logos arrive in turn and answer the hand. The CV, which by its own rule never animates, takes hover states only: a tenure bar in full ink, a proof lifting, a role’s title in the accent, the stills breathing, the clients and skills receding round the pointed one.

The case files. The section bar’s pill slides to the open section instead of lighting a new one. The product window’s three lights come up under the hand. The sessions, the pods, the flows, the passes, the matrix, the seven questions and the facts arrive in turn; the boards, the bar table, the task table, the fixes, the see-also cards and the pager rise as the scroll brings them in; a meter fills to its figure; a figure’s rail, a board’s tag and a pulled quote’s source line are decoded; a figure lifts a hair, the pager’s labels lean the way they point, the phones on Safe Space tilt toward the hand, a diagram’s stations recede round the pointed one, and a still breathes. Practice. The steps, the calls and the after-launch list arrive row by row and recede round the pointed row, a step’s number lights and steps forward, a memo tilts a degree and lights its row’s key. Writing. A drop cap opens each essay, a rail along the top fills as the essay is read and holds where the reader holds, and a paragraph says which it is when the hand is on it, the number the hero plate draws a bar for. The colophon. Eighty entries breathe open, a swatch grows and copies its value, the token table’s swatches grow with their row, the specimens arrive in turn and a drop cap opens the three hundred words. The 404 decodes the path that was asked for and sets it as a chip, wipes its stills in, and its buttons arrive in turn.

Two things found on the way. A word split puts markup back through innerHTML, so a pulled quote that holds a drawing could not be split without handing the engine a blank canvas: the quote keeps still and its source line settles in instead. And where the browser carries the page change itself, the doors in stagecraft.js now stand aside: a file faded to nothing by a script before the browser took its picture had nothing left for the title to grow out of.

v7.47OCT 2026
Astrato was over three years, not four: the site said four years in ninety-four places across sixteen files, from the case file and its deck to the CV, the menu and the share images, and each one now says three.

Shad gave the dates on 21 October: November 2021 to January 2025, on contract from January 2024, which is three years and two months. The site said four: in the case file’s title, its facts, its figures and its lede, in the deck it was drawn from, on the CV as “4+ years”, as the 4 yrs beside Astrato in every page’s menu, on its card in the grid, and in the descriptions a search engine or a share card reads. Each now says three, or over three where it said over four. The CV draws its tenure bars to the longest role, which is still Astrato, so the shorter roles’ bars grow to match; the share images, the case files’ PDFs, the presentation deck and the CV’s PDF are made again from the corrected pages.

Two older entries in this log said four as fact; they say three now, and this entry is where the four is kept. The claims check reads every file the site serves for a four-year tenure, outside the blocks whose job is to name a corrected figure, so it cannot come back.

v7.46OCT 2026
The site leaves cream for cool paper and graphite, the case files come directly under the headline, ahead of the text that used to come first, and the three internal products join them in the grid, each flagged as one; the cards turn over more softly.

The grid sat below the overview’s text, so a reader met a wall of words between the headline and the work. It now comes directly under the hero band, on a desk and on a phone, and the overview follows it. The three things built for the team at Open Innovation and used inside the company (the UX Files deck, the Everyone Builds class and the design system’s story site), which rode on the old track and moved to the shelf in v7.45, sit in the grid under a row of their own. Each says it is an internal product on its front and on its back, says what it is and what is inside it, and opens its own artifact. The question at the top still marks case files only, and leaves them be.

The turn now starts as gently as it lands, over nine tenths of a second, where the last one left at full speed and read as a snap; and a resting pointer waits a little longer before starting it, so a pointer crossing the grid sets nothing spinning.

And the colours, which Shad said looked too much like Claude’s: warm ivory paper, warm ink and cream type on a dark ground is that house’s look, not this one’s. The cobalt he chose on 16 October stays, and everything around it turns cool: a porcelain canvas with a blue cast, ink with no brown in it, and a graphite ground with cool-white type where the petrol green and the cream were, in the light theme and the dark. Each case file keeps its own palette, taken from its product, except where its paper was cream: Safe Space moves to the NHS’s own pale grey, and the About page’s paper loses its warmth. Every pair of text and surface still clears 4.5:1.

v7.45OCT 2026
The case files under the hero sit in a grid instead of a sideways track, as cards that turn over: the front says whose work it was and what it moved, the back what is inside the file and which roles it speaks to; a question at the top marks the files that show what you are hiring for.

The track showed one and a half files at a time and said little about what was in them, on the one screen where a recruiter decides which file to open. The five files now share one grid at every width, with room between them. Each card’s front carries the product’s still, the client’s mark where the site already carries one (Astrato and the NHS) and the name set in the page’s own face where it does not, the role, the title, its one outcome and how long it takes to read. Its back says what the work was, in a sentence from the file’s own plain line, what is inside the file, in three or four lines from its own section headings, and which roles it speaks to, and it holds the one link to the file.

On a desk a card turns over when the pointer rests on it, a soft turn of most of a second with nothing to overshoot; on a phone a tap turns it and a tap on its back opens the file. The two faces share one place in the grid, so a card is as tall as its taller face and the back never runs past it. With reduced motion the faces trade places without turning, and without a script they simply stack. The first row asks what you are hiring for: each of seven answers is a button that marks the files that show it, moves them to the front and says which, and pressed again puts them back in their numbers. A phone gets the same grid where it used to get a second set of cards with less in them. The cards show stills; the running products are the first thing in each file. The three artifacts that rode on the track are in the shelf below, where each already had a line of its own.

v7.44OCT 2026
The CV now counts its readers, and which of its sections they read, without a cookie and without keeping anything on their device; no other page counts anything, and anyone can say no.

Until now this site counted nothing. It still counts nothing on any page but the CV. There, Vercel’s analytics, served from this domain by the host that already serves every page, records the visit, each section read (half of it, or half the screen, in view for three seconds), the section a followed link sat in and the kind of place it led, and whether the CV was downloaded, printed, copied or saved as a contact, each once a visit. It sets no cookie and stores nothing, and a browser that sends Global Privacy Control or Do Not Track is not counted at all.

The new privacy section says all of that, why it needs no consent banner under UK law, and how to object: a button there and under the CV that stops the counting, remembered as one setting that identifies no one. A new check holds the CV to what the section says on every pull request, and the morning check now reads the counting script the host serves and fails if it ever sets a cookie or stores anything. This page’s line that the site has no analytics now names the one exception.

v7.43OCT 2026
The site gives no email address now, and one name and one city: LinkedIn is the way to get in touch, and every page, the CV and the contact card say London.

The address is off every page, the CV and its PDF, the contact card, the structured data and the command palette, and the copy button went with it from every footer; a printed page carries the site’s address where it carried the email. The contact section on About now points to LinkedIn. The long form of the first name is out of the CV’s contact block, the contact card and the structured data, the design-system talk and its story pages say Shad, and the made-up people in the Storybook’s sample records have other made-up names.

The current role is in London on the CV and everywhere else, the clock in the breadcrumb row keeps London’s time alone, and the drawing of two working days in About’s contact section is gone with the second city. One earlier entry, v7.12, quoted the old contact block; the quotation is out of it, the one time an entry here has been changed after it shipped.

v7.42OCT 2026
Every one of the seventy-two checks has now run on a clean machine as well as on the one this site is built on; doing it parted two captions in the Safe Space deck that met on other fonts, and made the PDFs print the same way anywhere.

Until now twenty-three of the checks had run anywhere but here. All seventy-two have now run in CI from a clean checkout, and forty-six of the forty-eight that never had passed as they were. In the Safe Space deck, two captions of the live beta figure drew on each other in the runner’s fonts; each is now three shorter lines, in the same words.

And the case files’ PDFs would not print there. A picture still loading after a page had printed took the printer down, and the browser it fell back to writes spaced capitals letter by letter, so a fresh print read differently from the one shipped. Both are fixed: the PDFs, the deck and the CV print with the same browser on any machine.

v7.41OCT 2026
The first run against the live site, by hand on the day v7.40 shipped: every page, script and stylesheet is main to the byte, and the notes kept beside the pages are not served; the host’s firewall turned the check’s headless browser away, so the morning check now reads the site without one.

v7.40 said three checks would run against withcontexts.com every morning, and that there the site would be held to load clean and to run under its policy. The first run found every page, script and stylesheet identical to main and every file kept off the site a 404, which also shows the host honours the list of files to leave out. The two checks that open a browser were challenged by the host’s firewall, which treats a headless browser from a data centre as a bot, rightly.

So the morning check is two checks that read without a browser: the files, and the headers and policy each path is served with, compared with the policy written. Loading clean and running under the policy are held on every pull request instead, against a server that sends the same headers, and since the files and the policy served are the ones tested, what passed there is what is live.

v7.40OCT 2026
Wave ten, engineering and operations: every product’s first visit weighed and held to a budget; a Content-Security-Policy every page runs under; three hundred words on how this site is built; and the checks moved off one machine into the repository, where they run on every pull request, against the live site every morning, and through the job each product exists for.

Each case file now prints what its product downloads on a first visit, measured from the build, against a budget the products build enforces: past it, the build fails. React Flow left the first visit of the two products that only open it on request. Every page is also served with security headers and a policy that runs scripts from this domain and the exact inline scripts the pages carry, nothing else, so a script slipped into a page runs nowhere. The reproduced Storybook and the delivered decks keep the inline scripts they shipped with, and the policy says so.

The checks lived on one machine, with its paths written into them. They are in the repository now: twenty-three run on every pull request, and three run against withcontexts.com every morning, which must be main byte for byte, load clean and run under its policy. Writing that check found notes and scripts sitting in the folder the host serves, with nothing keeping them off the site; they are kept off now, and the morning run checks that each is a 404. The built products stay committed, because what is checked is then what is served, and a new check rebuilds them from source and fails on any byte that differs.

A last check uses the portal, the diary and the carers’ app for their jobs, start to finish. It found that closing the portal’s detail panel left keyboard focus on a button inside the panel it had just hidden. Focus now goes back to what opened it. Moving the checks found one more: a section heading, split into words for its rise, could take a line more than it takes whole, and when the words joined up again everything under it jumped. A heading that would do that now rises whole. And the drawing of the versions above this record had drawn only its first twenty-five, whatever its caption counted, because each bar waited its turn on a clock that stops: all seventy-two are drawn now. Still waiting on a yes or no: a public mirror of this site’s code, a signed link to request a gated file, and first-party counts kept without cookies. None of them is built.

v7.39OCT 2026
Wave nine, trust and reach: three essays, each the argument a case file makes; a walkthrough of each desk product, with every recording captioned and transcribed; the token chain counted from the stylesheets; and the two strongest files as a forty-minute deck, every line read from the files.

A new page, file 010, holds three essays: rules as case law, private by default, and the number that is true twice. Each is the argument a case file makes, taken out of its evidence so it can be read on its own, and each ends with the links to where the evidence is. None of it is new: every claim is in a file or on this page already.

The four desk products each have a walkthrough under them, recorded from the rebuild and played only when pressed. A silent recording needs its text alternative, so the recorder now times each step as it runs and writes the sentence that says what it shows into a captions track, and the case file prints the same sentences as a transcript. Writing them caught two lines that said more than the screen did, and both now say what is there. Case file 001 now shows the token chain as the stylesheets have it, every one of the 3,396 names followed to the value it ends at. And 001 and 003 are a twenty-slide deck for a panel’s forty-five minutes, built by reading each line from the files, so it cannot drift from them.

Still waiting: Figma files for the design side of the pipeline, any recognition, official logos and permission, the CV’s dates, and the level, timing and terms a looking-for line would need. Nothing has been invented in their place.

v7.38OCT 2026
Wave eight, evidence: every derived figure on this site is now recounted from its own command before each release, which corrected the token count to 3,396; case file 001’s rule against raw values is counted rather than asserted; and case file 002 carries the measurement plan its hindsight asked for, and the test that plan makes possible, both running in the rebuild.

figures.js has always published, beside each derived figure, the command that reproduces it. Nothing ran them. The first run found three that could not reproduce their figure: the token commands put their file filter where grep reads a file name, so they counted the token docs and story files as well as the stylesheets; the rule command printed a word with its number; and the wave command sorted as text. Read as their own definitions say, the tokens are 3,396 and their declarations 4,255, not 3,444 and 4,852. Every page, the CV, the share cards and the PDFs say so now, and a new suite runs every command before each release.

Case file 001 said no component touches a raw value. It now says what a count of the source finds: none of the 1,304 colour declarations in the system’s component stylesheets is a hex, rgb, hsl or named colour. Case file 002 said nobody instrumented the query bill and that I would from the first sprint. It now carries that plan, in the order Amplitude’s taxonomy playbook gives and with Segment’s event names, and the rebuild runs it: every call is checked against the plan and shown in an Events panel, nothing is sent, and a question’s words never reach a call. Under it sits the test the plan makes possible, designed after Kohavi, Tang and Xu, with both arms in the product and a check on the split that works on the reader’s own counts. It is marked as a design that has not run.

The rest of this wave asks for figures this site does not hold: the Villa Plus launch report, counts from the prototyping pipeline, Astrato’s own numbers, what followed the NHS beta, what each client decided on 004 and 005, and whether any experiment ran. None of them is invented to fill the gap.

v7.37OCT 2026
Wave seven, part two: the products show their phone layouts, their empty and failing states and three recorded moments; every chart says what it has to say and every mark reads; 004’s position on who may see a figure is a setting in the rebuild; the phone apps’ controls are all 44 pixel targets; and this page draws its own system.

Case file 004 said a figure whose derivation a reader is not entitled to see should not be on a shared screen. The rebuild now does it: view the cockpit as one segment’s controller and a row access policy limits the rows before any query sees them, the group figures are withheld with the reason in their place, and the segment chart draws that segment alone.

Every product gained the states around its main screen, each one a link from its case file: the warehouse not answering, where nothing is extracted and so nothing stale is shown; a search that finds nothing; a sheet with nothing on it yet. The four dashboards each have a live phone beside their desk window, and three short recordings, played only when pressed, show the moment each file argues about. A new suite holds the 32 charts to 3:1 on their cards or a printed value on every mark; the first run failed 13. Another holds the phone apps’ 164 controls to 44 pixel targets; 54 were short.

Right to left is not built: nothing in the record says the design system supported it, and a switch in the portal would claim it did.

v7.36OCT 2026
Wave seven, part one: every page and every running product held to WCAG 2.1 AA by axe-core, 162 views in all, the failures fixed rather than waived; an accessibility statement on this page that says what is checked and what is not; and the case files’ section bar back to one row.

The site had its own accessibility suites but had never been run through axe-core, and the products inside it never had any. Two suites do it now, before every release. The first run failed 28 of the 36 product screens and 43 of the 54 page views. Menu buttons that were spans, search buttons whose labels left out their own printed words, sliders named on the wrong element, scrolling panels a keyboard could not reach, a closed dialog still in the tab order, and a long list of quiet greys, ambers and brand colours set as words at three or four to one. The signal colours in the products are text too, so each now passes 4.5:1 on a card and on its own tint; the light ambers sit near GitHub Primer’s attention ink.

One figure is exempt, by name: the before half of the before and after page in 001’s deck, which draws the old interface’s faults on purpose. The statement in section 07 says so, and says what has not been done: no screen reader, voice or switch testing, no external audit, Chromium only. It is partially conformant, in the W3C’s words, and says why.

Shad saw the section bar wrap to two rows on a desk once the case files reached twelve and thirteen sections. From 701 pixels the names that do not fit now sit, in order, under a More list at the end of the row, and a new suite holds every bar to one row at six widths. The known-issues list also stopped mentioning a photograph that left the site in v7.31.

v7.35OCT 2026
Wave six, the AI case: Astrato Insights in the rebuild now works the way case file 002 says it does, scoped, asked and answered with its SQL open to edit; 001 says what kind of AI system its pipeline is, how it fails, and reads one of its prompts line by line; and 003 states where AI does not go, which both NHS products now say where the data is set.

Case file 002 had said for a long time that Insights is scoped to the fields it may draw on before it is asked, answers with measures, dimensions and the SQL that made them, and keeps that SQL visible and editable at every step. The rebuild’s panel read the sheet back in prose and did none of it. It does now: based on 23 fields, the rebuild’s own model, with a picker to take fields out; a prompt or a suggestion; the answer in Default, Blocks and SQL views of the same thing; an edit to the SQL marked as the analyst’s own; and the answer added to the sheet as an object they own. A field out of scope is left out, and the answer says so. The SQL starts at the measure’s own table and joins along the model, so a tenant’s revenue is summed once per tenant and not once per user who joined it. Beside it on the case file, three assistants that write queries for analysts, each described from its own documentation and none ranked: Snowflake Cortex Analyst, ThoughtSpot Sage and Power BI Copilot.

Case file 001 now says what kind of system its prototyping pipeline is, in the patterns of Anthropic’s guidance on building agents: a short, fixed workflow with checks after it, not an agent left to roam, chaining a sentence to a story, routing a request for a missing part to a person, and grading its work with a verifier that reads it cold. It names the ways it fails, from what the file already records, and reads one prompt from its library line by line, the company and the deployments in it invented. The Brain section draws how the memory is read, for the page and not from the vault, which is never served.

Case file 003 takes a position, labelled as one: nothing a young person writes is read, summarised or scored by a model, why not, what it would take under NICE’s evidence standards for digital health, and where a model might one day earn a place. The diary says it on its own screen and the clinician tool lists it as a setting marked Never; the traced suite now checks 31 decisions across the two files. Two rounds wait on Shad: a sixth case file on the enterprise AI work, which needs his permission and its anonymisation line before a word of it is written, and the pipeline’s quality numbers, which need the numbers.

v7.34OCT 2026
Wave five, leadership and collaboration: a ninth file, on how the work is led, with its own drawing; every case file’s record names its friction; two decisions written as one-page memos; and the design system’s contribution model, a first week on it and the class that taught it, each linked to where it can be checked.

A panel hiring at lead or staff level asks how the decisions got made and who had to live with them. The case files answered it one file at a time; file 009, Practice, is the index across them. Who the work reached and what was mine. Six calls other people lived with, each with what it cost, and two of them written as one-page memos: who sees a teenager’s diary, and one number or the basis with it. The seven steps the work went through in every file. Where each file rubbed. What stayed after launch, and what nobody measured. How a change gets into the design system, a first week on it written fresh in its published rules, and the class that taught it to the whole company. Every line links to the file that shows it, and nothing on the page is new evidence.

No management is claimed, because the CV claims none: the page is about reach, not rank, and its drawing says so, one mark and the people each file’s work reached, nine designers on five product teams, twenty-nine people in two pods, twenty-one in a clinic. A draft line saying that none of them reported to me went before it shipped, because the record says nothing either way. Every case file’s record gains a line, Friction, where the hard part was people or ownership, and the frame suite now requires it. Testimonials, the wave’s seventh round, wait on four to six people with a name, a role and their permission; nothing is written in their place.

The workspace has nine files now, on the front door, in the navigator, the search palette, the sitemap and this page’s drawing of the frame. And 003’s share card, which still described a diary and a dashboard, now carries the story the file tells.

The battery caught two things worth keeping. The new page linked three times to a section of 001 that does not exist, and the links suite passed it, because it only asked whether the page existed; it now checks that a fragment lands on an id. And a jump inside a page, 003’s phones to its running product, landed with the product under the section navigator on a phone, because the motion layer exempted a deep link only when the page opened; a jump now finishes its target’s entrance at once and lands again.

v7.33OCT 2026
Wave four, research made visible, and the NHS file told as it happened: care sent home in 2020, a clinician’s hour of four or five calls, three apps and one clinician tool for two teams, and the notes system before rebuilt so a reader can feel what it cost; on two case files the scripts, the surveys, the tasks and the heatmap are shown as they were, and every finding opens the product where it holds.

Shad’s account of the NHS work: an agency’s access across a trust’s projects, the largest of them this one, in the months COVID sent the clinicians home and the people they cared for were already there. Young people who live on their phones but are not at home on Zoom, and want to decide how much they share; older adults reaching a doctor through a screen for the first time; clinicians at a kitchen table with four or five patients an hour, needing the trust to come back quickly and a note good enough for the next call to start from. Case file 003 now tells that story, in a new section on what moved home. The notes system before is rebuilt and runs on the page, labelled a reconstruction with every name invented: a form that requires a room, a free-text box, the history as a printout, a fixed 1024 pixels wide. Beside it, a table of what the old system assumed and what the new tool does, each row opening the product where it shows.

The products changed to match. The clinician tool shows the hour, how many calls and how many done, opens every call on a brief (what changed since you last spoke, the body beside the mind from the person’s own check-ins, what matters to them), keeps one thing to remember for next time, and serves a second team, older adults, whose chart measures pain and getting out. The young person’s diary chooses how much of an entry is shared, the mood alone by default, and joins a session inside the app with a chat instead of talking offered first. And a new app, for older adults: one button to join the call, a phone call always offered instead, four yes-or-no questions on the body, text size and read aloud on every screen, the nurse and the family named. The service’s dates and the canon’s four discovery figures are now as of 2020, the year the work was done.

Shad’s other note: the research has to show in the products, not only in the case files. So 003 shows its three interview scripts as the topics the deck records, both surveys whole on one scale with the three rows that shaped the product marked, the usability tasks word for word with what each found and its 95% interval, six findings grouped by who said them with their evidence and the product state each became, and four job stories, labelled as written from the interviews. On 002, the heatmap’s caption states its finding, that eyes went to the table headers and not the join lines, and the product acted on it: every table now names its joins under its header, and hovering one lights its line. Earlier in the wave the two products were brought into line with their own research, the chart that says which way is better, no read receipts, notifications not pushed, joins from any side in four clicks. A new suite, traced, opens the product at each of those states and fails if the decision does not hold.

v7.32OCT 2026
Wave three, the page itself: the landing’s product cards wait for a hand, its largest paint no longer waits on a script, the six products share one copy of React, every picture offers AVIF and every still a 2x, a case file labels in one system and bolds once a paragraph, the site holds up under a forced palette, no text on a phone is smaller than eleven pixels, and every case file has a PDF of itself.

The third ten rounds, each its own commit. Scrolling the landing used to boot the applications behind its product cards as they came near the screen, 5.21MB for a reader who touched none of them; the cards are facades now, a poster until a pointer, focus or touch reaches them, and a full scroll costs 1.03MB. Lighthouse on a phone scored the landing 72, because the largest thing on the first screen was a line the motion layer faded in, and a hidden word does not count as painted; on a touch screen the title now arrives whole with the page, and served compressed, as it is deployed, the landing measures 85 to 95 on a phone and 97 to 100 on a desk. The six products each carried their own React, 6.25MB together; they build in one pass now, 44 to 120KB each over 1.24MB of shared chunks that a browser fetches once. Every picture offers an AVIF before its WebP (2.45MB against 4.19MB at 1x), and the stills of the running products are shot at 2x, with a 2560-wide AVIF for a high-density screen.

A diagram on a case file carried four labels at once and every section closed on a footer naming the next, which the navigator already does; a case file now labels in one system, the section, the figure and the caption. Two paragraphs bolded twice; each now bolds once, after Butterick. The house labels are set at 9.5 to 10.5 pixels, which reads on a desk and not in a hand: on a phone every size under eleven is raised to eleven by one variable, and the diagrams, which drew their smallest labels at 7.4 pixels on a phone, now pan at the width that sets them at eleven. Under a Windows Contrast theme the CV’s tenure bars and a meter in case file 002, both drawn only in colour, vanished; they draw in the reader’s own system colours now.

Every case file now has a PDF of itself, printed from its own print stylesheet and linked beside the deck with its pages. Printing them showed what paper had been losing: the phone rule that folds the source notes also matched an A4 sheet, so every printed case file had dropped its notes, the reconstruction notice on 004 and 005 with them; the workspace chrome printed on page one; and the footer offered a copy button and no address. Each is fixed, and the stills of the five service blueprints, which had the page’s section nav baked across their top edge, are reshot. Ten suites join the battery: scrollcost, lighthouse, products, bundles, images, labels, emphasis, forced, floor and pdfs.

And About is about the work now. The window left over from the found text is gone, and the page’s section on how I work reads as how I design: understanding first, the experience as a set of decisions, the interface where it either reads or it does not, and code as a design material, each with an example from the case files.

v7.31OCT 2026
Wave two, every file’s frame: each counted figure says when it was counted; each file says what was theirs and what it ran under, opens its outcome on the result against its own bar, closes on what I would do differently, and points at two other files; every case file has a row of the seven questions a portfolio round asks; small samples read as counts; the CV closes with references; and every page says when it last changed.

The second ten rounds of the plan, each its own commit. A figure counted from a moving repository is true on a day, so every block that states one now carries one stamp, as of Jul 2026, the way a chart carries one source line. The record at the top of each file, which answered what I owned and who with, now also says what was theirs (the code, the constraints set by others, the beta the clinic ran) and the constraints the work ran under, each in the file’s own words; the two reconstructions say that their teams’ roles are not part of the reconstruction and claim none.

Every outcome now opens on a table: the measures the file set, the result against each, and its status, met, held in the rebuild, or not measured. Four files had set their measures early, in each blueprint’s tree, and Safe Space’s were agreed before its beta ran; what was missing was the loop closed beside them. Every outcome closes on what I would do differently, and every line of it restates something the file already admitted, from a rule reverted hours after it was mandated to a feature built before the teenagers killed it. Under each section nav, the case in seven questions, problem to reflection, each a jump to the part that answers it. After each outcome, two other files that argue the same thing from another side.

The best-known research figure on the site was 80%, and it was four people of five; it now says 4 of 5 everywhere, the CV included, because a percentage claims a precision five people cannot carry. The NHS beta’s 94% stays, because it is what the beta report says, but the report gives no base and 94% of twenty-one is not a whole person, so the case file now says that the base is not given and no sentence pins it to the twenty-one. One correction on the way: a round gave each facts block an id and the frame suite, still looking for the old tag, went red after the round committed; the commit helper now refuses to commit while the fast suites are red. Two new suites, asof and samples.

And two things went, at Shad’s request: his photograph, from the About page, from the About and CV share cards, and from the repository, so no copy of it is served; and the found text on the About page, the line about fixing the world without the source code, with the answer that was built on it. So did the lines on the live pages that told a reader what could not be named, published or shared: the pages say what is true and no longer point at what they leave out. The About panel is now one column around the identification card, and the dossier suite fails if the photograph or the quote comes back.

v7.30OCT 2026
Wave one of a hundred rounds toward the bar the largest design teams hire at, and it is the first thirty seconds: a value line on the first screen, scope in the words panels level by, a start-here route by the kind of role, a reading time and a skim on every case file, a plain line under every literary headline, an outcome or an honest badge on every card, the name before the brand, a dated now line, what I owned and who with on every file, and one structured-data graph about one person.

Shad’s note: do a massive study of the site, find the hundred things that make it short of that bar, and plan how to close them. The study found them in ten themes, from the first screen to the operations behind the site; the plan gives each its own round in ten waves of ten, and every round runs the same way: measure what the site does today, research the competition and the technology, decide, build, commit on its own, and add a check so the gap cannot quietly come back. The plan lives at the repository root, outside the site. This is the first wave, ten commits.

The first screen said who and what, a name, a title and a slogan, but not at what scale or with what result: the lede began at the fold on a desk and on a phone. A value line now sits under the slogan inside the band, and a four-part strip under the lede says what kind of scope the numbers are: five product teams on one programme, the platform nine designers build on, the only designer for 29 people across two pods, design to code. It claims no people management, because the CV claims none. The two generic buttons became a route: AI, platforms and systems start at 001, product, research and health at 003, then 002 either way. The first version offered 002 twice, forty-two pixels apart, and the suite that exists to catch that caught it.

Every case file now says how long it takes, counted rather than typed: 238 words a minute, Brysbaert’s figure for reading non-fiction from a meta-analysis of 190 studies, plus Medium’s allowance for each figure, over the words a reader actually meets. Twelve to fifteen minutes in full; a skim, one press away, folds the long prose and the spec tables and keeps the headings, standfirsts, numbers, figures and decisions, in six to eight. Under each headline, a plain line in three labelled parts, what it is, for whom, and the problem, so the literary title can stay literary. Every case card on the landing, the Work directory and the 404 carries one outcome with its number, and the two reconstructions a dashed badge that says they claim none. The facts on every file answer the two questions every portfolio round opens with, what I owned and who with, in roles and in the file’s own words.

The top bar now leads with the name and keeps Contexts as the workspace’s; the share cards and the structured data say the same. Three pages had carried a Person each that disagreed with the others and shared no id; one tool now writes one graph, with a WebSite, a profile page, an article and breadcrumbs per case file, and dates from git rather than from memory. Four new suites hold all of it: fold, readtime, frame and jsonld.

v7.29OCT 2026
The design system’s real Storybook, built from this repository’s own source, runs on the site: 2,082 Storybook stories and 203 docs pages of the components the platform ships, under the portal in case file 001, open from the portal, the landing, the work directory and the 404.

Shad’s note: the files on the actual OI design system are much richer, it has a Storybook, bring those files in. The source has been in this repository all along, which is where the canon counts its tokens and components from; what the site ran was the portal, a token browser and component explorer rebuilt by hand. Now tools/build-storybook.sh builds the real Storybook from src/shared/ui/src and packages/oi-ui, the same globs the engineers’ Storybook uses, and places a sanitised static copy under /products/storybook: the two story files that fetched avatars from outside get an inline placeholder, so the page makes no request beyond this domain; the visual-tests addon’s own assets are left out; the title names the site; and nothing from the brain is in a Storybook build to begin with. One thousand and fifty-six files, twenty-five megabytes, every atom, molecule, organism and template with its controls, its docs page and its themes.

It sits in case file 001 as a second window under the portal, with its own Reset, Expand and Open. It is the heaviest thing on the site, so its stage carries data-boot="view": it boots only once a sixth of it is on screen, with no margin, behind a still of a docs page, and the page’s byte budget holds. The two counts went into the canon with the command that produces each from the built index, and the pages that cite them cite the canon. The battery runs over the Storybook’s pages too, through the sweep.

v7.28OCT 2026
The two phone apps wear the shipped app’s own language now, taken from the four screens in the case file’s figure: a cobalt band for the morning, pale blue for the diary, mustard for the tracker, navy for the planner, white cards, rust and mustard and pale blue as the three day marks, and the navy pill along the bottom; and every phone screen clips its frame, so nothing spills past the bezel.

Shad’s note: follow the same design language as the app in the NHS case study, and the prototype frames were overflowing the phones. The apps had been built in the clinic dashboard’s calmer skin, which is the clinician’s side; the teenager’s side had a language of its own in the deck, and it is in the case file as a figure: four screens, one band of colour each, white cards on a ground that runs from pale blue through cream to sage, a book face for the one line that is not a label, and a pill of two segments along the bottom. So the apps have a skin of their own now, appended to their stylesheet by the build so the other bundles do not carry it. The home screen carries the tracker’s percentage and bar and the planner’s navy card as the original did; the tracker screen has the week’s split bar, good moments against hard ones with the Ok under it, and the day-by-day calendar with a dot a day, big and rust when it was hard, small and mustard when it was okay; the planner has its cards in pale blue, mustard for the one due now, navy once done, and the grid of empty slots. The parents’ app is the same family. The dark setting reads navy ink as ink and keeps mustard’s ink navy, because mustard is as light in the dark as in the light.

The frames: a scaled frame is a composited layer, and overflow:hidden with a radius does not reliably clip one in every browser, so a frame’s square corners could show past the screen’s round ones. Every phone screen, in the case file and in the dashboard’s record, now carries a clip-path of the same radius, which clips the layer itself. The posters and the three phone stills were reshot.

v7.27OCT 2026
The three surfaces of Safe Space meet: the clinician dashboard’s “Patient app” tab runs the real diary and the real parents’ app in a drawn phone, the case file carries phone-shaped stills of both at the points the prose argues, and the landing says “two phone apps” on a phone as well as a desk.

The dashboard’s record had a tab called Patient app that drew two screens by hand, a mood strip and a planner, from the deck. Now that the diary and the parents’ app are applications of their own, the tab runs them: a phone drawn in the record, a switch between the two apps, and the frame mounted only when the tab is open so nothing boots behind the summary. The frame reads the dashboard’s theme through the kit’s own hook, so case file, dashboard and phone change together. The address learned ?state=app for it. The prose beside it says what is true now: what David logs in the diary feeds the indicators above, only the entries he shares reach the record, and his mother sees that he wrote and which way the week went, never the words.

The case file’s stills had all been the dashboard. The design section opens on the two sides of the privacy model as the two apps run them, the diary’s share sheet with its three readers all off, and the parents’ what-you-can-see with its four things seen and four not; and in the outcome the booking dialog and the phone it lands on stack in the sticky column, so the reader sees both ends of the same act. The stills tool learned phone-sized shots, 780 by 1688, and the placement tool leaves hand-placed entries alone. On a phone the landing’s NHS card wears the flag and the peeking diary the desk card got in v7.26, and the third core thread says two phone apps and a dashboard came out of the research.

v7.26OCT 2026
The NHS work has its two phone apps now, running: the young person’s diary and the parents’ and carers’ app, in drawn phones above the clinician dashboard they feed, and the landing says so before a word is read.

Shad’s note was short: build the two NHS mobile apps, put them above the dashboard, make it clear on the home page that the NHS work has mobile. The case file had been running the clinician’s side only, which is the side the clinic bought but not the side the research was about. So the diary is an application now: a check-in that takes one tap, entries that are private by default and shared one at a time with the reader’s name going on the entry, the mood chart only the young person sees, goals with the two recommendations from the session of 14 July arriving in the same thread as the conversation, the thread with the keyworker, five minutes of breathing, the numbers for right now, and the one screen that says who can see what. The parents’ app is the other side of the same model: that David wrote this week and how often, which way the week went from his own ratings, the visits, what to do if something looks wrong and when not to worry, the safety plan written with his mother in April, and never a word of an entry unless he shares it. Every figure the two phones show is the figure the dashboard shows for the same young person, because the three are one record.

They sit in two drawn phones above the dashboard, a band the section navigator now opens on, each a 390 by 844 application scaled to its column, booting when it comes into view and holding a still until it has. On the landing the NHS card carries a flag and the diary phone peeking over the running dashboard, the pane’s lede says two phone apps before it says dashboard, and its first button opens them; the work directory, the 404 and the case file’s metadata say the same. The parents’ side is a reconstruction from the weekly summary and the guidance the research asked for, and the case file says so under the phones. One bundle, products/nhsapp, built with the other five; tools/build-phone-posters.mjs shoots the stills. Five products still: Safe Space is one product with three surfaces. The deep-link suite caught something older on the new band: the block a link points at was being staged for its rise, so on a phone it landed under the navigator by the part of the rise it had not finished, and the title’s word split was costing the hero a line that came back after the landing. The linked block is left alone now, and the landing is repeated once the title is whole.

v7.25OCT 2026
The next tier of the backlog: the CV's four proofs on the landing's first screen, every still on the case files a door into the product in that state, the two reconstructed files saying so under their heroes, the battery named on this page, and the smaller items each page had queued.

A recruiter decides on the first screen, so the four numbers the CV leads with, the fifteen seconds, the eighty per cent, the ninety-four and the eighteen, now sit under the landing's two buttons with their sources, counting up as the page arrives, the same strings as the sheet and nothing new claimed. The twenty-five stills beside the prose on the case files had been pictures; each is a link now that opens the running product in the state the still shows, with a pill on hover and always on a phone, so a reader who sees a screen can be in it one tap later. Novo Nordisk and JBS say under their hero captions that they are reconstructions, which the source notes at the foot had said and nobody reads first; the two kickers that wrapped to two lines are shorter; the quote bands' clouds, which smudged the type at 1440, are dimmer; JBS's next card says it goes back to the first.

This page names the battery. The house-rules section carries a table of the forty suites with what each one holds the site to, in the words the changelog has been using for them without ever listing them. The 404's five case files carry their product stills, and the About page says in one line, in the CV's words, what the role being looked for is. On the CV the title sits on one line at 1440, the alias has the contact block's last line to itself, the stills in the aside are a size larger and the proofs read larger on a phone.

v7.24OCT 2026
The backlog the third review wrote, worked page by page: the section bars on one row, a colour section that says why every colour is here, the CV's loose ends tied, the 404 made useful, and a print that would have come out blank.

The print first, because it was live. The motion layer that arrived in v7.23 holds a block at opacity nought until the scroll brings it in, and a print never scrolls: the CV's lower half and every case file's later sections would have printed blank, and the ATS check caught it on the CV within the hour. Two rules came out of it. Nothing on the CV animates, which was already written down and is now enforced in the one place it can be, the top of the motion script, which leaves the sheet alone; and on paper every staged block is whole, by a print rule that outranks whatever the script set. The same afternoon the token table on this page turned out to be carrying four values a version behind, including an accent that had not been the accent since v7.22, under a sentence that said the values were copied from the stylesheet. They are read from it now, at load, so the table cannot drift again; the sentence says so and says what it used to say.

Then the backlog. Four of the five case files' section bars had grown to ten or eleven names and wrapped to two rows at 1440, which read as two bars; the long names are shorter and the pills tighter, and all five sit on one row. The hero drawing of tables bled off the band's right edge, which the field does on purpose, but a table cut in half reads as a crop rather than a bleed, so the tables are placed in the three quarters of the canvas a reader can see. Four still captions repeated the standfirst above them and say something else now. The source notes at the foot of each file fold under their heading on a phone, with a control that says how many there are. The CV's current role carries a bar that runs on instead of no bar; its reference lines are a size larger; the Villa Plus launch figures are two bullets rather than one with five numbers in it; the sections breathe a little more; and the sheet carries a stamp at its foot saying where it lives and that this changelog records every edit to it. The 404's hero is a third the height, its five-item lists sit five across, its products say running rather than demo, and it echoes the path that was asked for with the nearest file by name. The landing's thread numbers are readable, its grain is lighter, the window about me is set in type a reader can read, and the page ends with a way into the work rather than only a way to write. The work page's filter chips carry a count. The About record carries the name.

And the colour section, which the note asked for by name. Section 03 of this page now says why the site is cream, ink and one cobalt; why the hot mark in the drawings is the accent's own hue a step up rather than a second colour; why a dark ground lifts the accent instead of swapping it, and by how much; why each case file wears a hue its client's identity suggests and none of their marks; and why red and green appear only inside the products, beside a number that moved. The values sit under the prose as swatches, and every pair is the one the contrast, invert and bands suites measure. The type section's heading said four faces over a paragraph that said three; it says three. The sections after it moved up a number.

v7.23OCT 2026
The note said the case files were walls of text with ten-step drawings, that nothing on them was interactive, and that the site should move the way the good ones do. So: a running service blueprint on every case file, a still of the product beside every block of prose, and a motion layer on the type, the figures, the pictures and the pointer.

The blueprint is an application now, not three plates. It is built with React Flow and lives at /products/blueprint, one file per case: six lanes in the service-blueprint convention, evidence, user actions, frontstage, backstage, support and where it fails, with the three lines between them named; one column per moment, sixteen for the workbook builder and eleven to twelve for the rest; the happy path drawn along the user lane with the clicks each moment costs and a running total to any moment the reader picks from a control; the sad paths as dashed edges from the moment that fails to the one it lands on, with a severity; a star on each moment of truth; a phase band across the top that fits the map to one phase at a time, because sixteen columns fitted to a window is a barcode; an inspector for any moment, an aside on a desk and a sheet on a phone, with the evidence behind it; find, keyboard walking, the product's own skin. Each case file carries it embedded under its blueprint heading with a full-screen link, and the embed is honest about its weight: a still of the map holds the frame until the reader reaches it, the application boots then, and the still fades. The four products learnt to open on a state from the address at the same time, so the stills tool could shoot each of them in the state a section is about.

That is where the pictures came from. Twenty-five blocks of prose on the five case files had no picture of their own, so each now has the running product beside it, opened in the state the paragraph describes, in a two-column grid from a thousand pixels with the still sticky beside the paragraph being read, stacked under it on a phone, and set at a reading width under the sections that have no prose at all. The captions are the sections' own words and claim nothing new. The strip on the landing page shows the same stills under its cards while the products boot behind them, where it had shown the word booting on empty paper for as long as the queue took.

The motion layer is stagecraft.js, on GSAP and SplitType, which the site already carried for the artifacts, and it keeps the house rule that a thing moves once, when the reader arrives or when the scroll brings it in, and then holds. A headline's words rise one after another on arrival and a section heading does the same when it comes into view, and the split markup is put back when they have, so the page is byte for byte what it was. A mono label is decoded, its glyphs settling left to right, drawn over the real words rather than written into them, so a parser reads the page and only the eye sees the settle. A figure counts up to itself once. Prose, drawings, plates and stills arrive with a short rise, a still is wiped in from its top edge, a picture drifts against the scroll, the hero's ground moves slower than its type, cards arrive one after another, a primary button leans toward the pointer, a ring follows a fine pointer and opens over anything that takes a hand, the theme switch sweeps the new theme out from the switch, and the open file fades on its way to the next one. Every reveal is driven by an observer and caught by a measuring net on scroll, so nothing can be left hidden; under reduced motion none of it runs. Four things found on the way: under reduced motion the dossier's portrait and its cloud had painted ink on ink for a year, because the reset that gives every element a 0.01ms transition made the engine's colour probe read the previous colour; the matrix plate drew arcs of negative radius on a phone; the landing's shelf still said three client decks after Villa Plus left; and this changelog, fifty-six entries open on a desk, was thirty-six thousand pixels of prose before the first drawing, so it folds now at every width and unfolds on one control. The CV's products moved from the foot of the sheet into the aside, which had stood empty under the degrees, and travel with the reader there; the profile is three short paragraphs with the ask on its own line, and the four proofs keep their file links on one line. One more, found reading the Safe Space file as a first-time reader would: the figure captioned as the patient timeline had been, byte for byte, the appointments picture above it since the site's first commit, and nothing had caught it because every check reads a picture's shape and size and none reads what it is of. It is the deck's patient overview now, cropped to the quality-of-life chart the caption names, and the backlog carries a check that two figures on one page must not be the same file. What the note also asked for, twenty improvements and ten additions on every page, written down and done, is the next version's work; the review that feeds it is captured, every page walked screen by screen at both widths, and the backlog file holds the landing's thirty.

v7.22OCT 2026
Three asks in one note: the CV set again as a proper document, a sheet with its employers and clients on it; the house accent a deep blue instead of the vermilion, and the one other red on the site, Astrato's crimson, a deep violet; and every case file opening on the running product under a hero half the height it was.

The CV first, because Shad's note on the v7.20 page was blunt and right: wrong spacing, too many accents, a glyph beside every number, the look of something put together fast. The page is set as a document now, the way the people who shortlist designers expect one: a paper sheet on the desk in both themes, two columns, one accent used only for the four proofs, the figures and the links, two weights of type, section heads as rules, every gap on a scale of four. The profile and the four proofs, then the roles with their tenure in the margin, then the five products as stills; beside them the employers and clients, the toolkit and the degrees. The employers and clients are set as wordmarks in the page's own face, one ink, a thin rule between: Open Innovation, Astrato by Vizlib, the NHS, Novo Nordisk and JBS on Astrato, Villa Plus, Travel Direct. Not the trademarks. The NHS identity and the client marks are theirs to license, and a CV is not the place to borrow them; where Shad has an official mark with permission to use it, it drops into the cell. On paper the aside folds under the experience in three columns, the bullets stay in the flow so a parser reads each role's evidence under the role (a positioned bullet had been painting, and therefore reading, after the next heading), and nothing is tracked, because a parser reads tracked capitals as spaced letters. The PDF was rebuilt; two pages either way; the ATS check reads it in order.

The accent had been vermilion since v6.0, chosen because a pigment colour sits on cream the way press ink does. Shad does not like the red, which is the whole of the argument, so it is a deep cobalt now, picked for the same job the vermilion did: one saturated note against a warm neutral ground, dark enough to carry near-white type on a button and to read as text on the sunken well at better than seven to one, and not the electric blue the site retired in v6.0 because nobody picks it. The dark theme takes a brighter pair of the same hue. The hot mark in the drawings follows the accent, the printed CV uses the same ink as the screen, and the share cards were rendered again from the pages so they carry it too. Astrato's file was the one other red here, the deck's crimson; it is a deep violet now, in the file, on the directory's chips and in the product itself, which was rebuilt and re-shot. The other four skins were never red and keep their colours.

Since v7.18 each product case file opened on its blueprint and reached the product four screens down. The note was that the built thing should be the first thing after the hero, so it is: the hero, the section navigator, the running product, then the facts, the blueprint and the rest, on all five files, with the navigator's first pill pointing at the product. The hero is about half a screen now rather than most of one: the band is shorter, the title a size smaller, the drawing the same. The design-system file, which had its product above the navigator and its facts above both, took the same order.

v7.21OCT 2026
The Work page rebuilt from the platform's own parts, with a still on every card, and the scroll now runs a hand over every drawing on every page: a plate answers the page's travel the way it answers a pointer, the token field turns twice as far under the thumb, and the dossier portrait is acquired line by line.

Two notes from Shad, both right. The first was that the Work page looked like somebody else's homepage, and it did: it had been modelled on a directory from elsewhere, with a serif title, a tinted banner and a line drawing, icon tiles in rounded cards. It is built from this platform's parts now and nothing else. The kicker in mono, the display face, the thin rules, the same buttons as everywhere, a shelf plate at the head with all fifteen files standing on it (the shelf drawing reads its spines from the page now, and the directory's fifteen are thickest where the case files are), and a still on every card: the five products on the case-file cards, and the five delivered sites, decks and classes shot at their own size for theirs. The featured file carries the running product in a window frame, and each card's number chip wears its file's own deep ground. The serif is gone. The landing page was not touched.

The second note was that on a phone the hero drawings read as still images, and they nearly were. Since v7.9 the scroll has assembled them, but once a drawing was whole nothing happened to it unless a finger landed on it, and on a desk nobody reaches for a drawing they are scrolling past. So the scroll runs a hand now. As a plate comes up the screen a point sweeps across it, left to right in a shallow wave that visits the upper rows and the lower ones, and the plate answers through the same hover, scrub and pick it already had for a pointer: the tables on the join canvas are picked up one after another, the weeks of the ribbon are scrubbed, the rules light in turn, the shelf is read spine by spine. Five kinds whose hit maps a wave would pass between (the shelf, the tenure rows, the ledger, the memory, the bench) take the hand in their own order. A real pointer over the plate, or a finger holding it, wins, and the sweep resumes on the next scroll after they leave. The point is a function of where the box stands, not of time, so holding still holds the drawing still, scrolling back runs the hand back, and the scroll check's byte-for-byte assertion holds as it did.

The token field on the landing page and the design-system file turns about twice as far as it did over a screen of travel, through most of a right angle, and the scroll turn composes with the pointer on a desk instead of being phone-only, so the wheel and the cursor both move it. And the dossier portrait, which was painted once and never moved, is acquired the way a surveillance still is: line by line from the top, a band of half-exposed rows at the scan line and paper below it. On a desk that plays once when the frame comes into view; on a phone the scroll does it, and undoes it. The canvas check walks every page in finer steps now, because its five-hundred-pixel stride could step clean over a section plate two hundred and thirty pixels tall and report it never drawn, which was the one check that used to go red under load for no reason anyone could find. And a plate reads its ink from the stylesheet only when it is measured, so the theme button had been leaving every drawing on the page in the other theme's ink, dark on dark, until the window changed size; the plates watch the theme now and re-read their colours when it moves.

v7.20OCT 2026
The CV carries its own figures now, drawn: a tenure bar on every role, what each role moved as marks under its bullets, a glyph beside each of the four proofs, and the five products as stills. On paper the same drawings, and the parse unchanged.

Shad asked for a real professional CV with the site's visualisations in it, so the round started with what a senior product design CV is held to by the people who shortlist them: outcomes before tools, a figure in every bullet that can carry one, leadership shown as things made rather than people managed, a clean single column a parser can read, two pages for a senior role, and links to full case studies rather than a gallery. The CV already met the text of that; what it lacked was the drawing. Its three plates were canvases, screen only, and the printed sheet, which is the artefact a recruiter actually keeps, had none of them.

The figures are drawn into the document now, in both media, as geometry with no text. Each role carries its tenure as a bar on the date line, months of the longest. Under each role's bullets a row of marks draws what the role moved: the three-layer token chain, ninety-one rules as ticks, three hundred and seventy-eight documents as a grid, eight of ten dots for the join task, the twenty-nine people in two pods, the ninety-four of a hundred who said keep it, the twenty-one in one clinic, the five launch moves as signed bars. Each of the four proofs at the top has its glyph beside the number. And the five products run as stills under the proofs, each opening the thing itself.

Every glyph is an inline SVG with no text in it, and the number and its label are HTML beside it, in the flow, so the PDF's text stream reads the same words in the same order it did before the drawings. The ATS check still opens with the name, finds the four sections in order, every role followed by its own bullets, no spaced letters and every accent figure as text, in two pages either way. Two of the marks are screen only, because paper has no room for them and their numbers are in the bullets above; the case-file line folded into each marks row paid for the rest. The skills set in four columns on screen and a line each on paper. The shipped PDF was rebuilt and matches the page line for line.

v7.19OCT 2026
The second look after the rebuild: a link to the product landed under the section bar, the bar itself stood three rows tall on a phone, and the workbook builder was three slivers wide in the window the case file gives it.

Every version here gets looked at again after it ships, at both sizes and in both themes, and this one found six things. A link to the running product, from the section bar or shared, put the top of the launch window under the bar by about thirty pixels: the window rises into place as the page scrolls, and a fragment scroll aligns the box as it is at that moment, still part way down its rise. The linked window no longer rises. On a phone the section bar had grown to ten names with the blueprint and the product in it, and ten names wrapped to three rows of chrome stuck over every heading; it is one row that scrolls sideways now, with the lit pill kept in the middle and the right edge faded so the row says it goes on. Nothing was dropped.

Inside a case file the workbook builder gets a window of 912 by 570, and its data panel, canvas and inspector shared that width three ways: the charts were a hundred and fifty pixels wide and the tiles read "1,…". Between a phone and a desk the panels open over the canvas as sheets now, and the objects take the whole row. The note that explains the Novo model sat open on the one table it explains at 1280 wide, so it starts folded unless the window is a real desk. And the canvas check, reading the model inside its new shell, found the Historian join's leg two pixels into the QMS join's label; the semantic layer moved right until every leg clears every label. The review and its grades are in the session's report; the fixes are these.

v7.18OCT 2026
All four products rebuilt as full applications with a dark setting and a phone layout, and each case file now opens on a blueprint: the system drawn end to end, what it is measured on, what it was built from, and a spec the product is checked against before every release.

Shad asked for the four products to become feature-rich, modern, closer to the real thing, on a phone as well as a desk, in the dark as well as the light. The Safe Space dashboard and the Astrato workbook builder were the last two hand-written pages here, each a few thousand lines of one script, and both are React applications now beside the cockpit and the spread board, on one kit. The clinician dashboard has a day and week calendar, a caseload table that sorts, filters and exports, an inbox with the conversation beside it, a booking dialog, an escalation that writes to the risk history and raises a notification, and a settings page where the risk alert has no switch. The workbook builder has sheets, seven object types bound to fields from a data tree, filters that restate every object and say how much data is left, variables a chart can read as a reference line, actions on click, undo and redo, a joins editor drawn with the same canvas library as the cockpit's model with its generated SQL beside it, Insights and Ana that read only what the sheet shows, and publishing with a version history that restores.

The two older products gained the same shell: a ⌘K palette, notifications, a user menu, keyboard shortcuts, a period and a bridge on the cockpit, a scenario sheet with sliders and approvals on the board. Every product follows the site's theme and keeps its own when opened alone, and below 760 pixels the sidebar gives way to bottom tabs, the inspector becomes a sheet that rises from the bottom, and a table becomes cards. Two things fought back. A breakpoint added to the Tailwind config silently switched off every inline breakpoint in the kit, so the sidebar vanished and the tabs showed on a desk until the config entry went. And the canvas controls stayed white in the dark setting through two builds, because a rule written inside a Tailwind layer for a class that only exists at runtime is dropped at build; it is a plain rule now, in the canvas library's own variables.

The blueprint is the other half of the ask. Each product case file opens, before the running product, on plate 00: the system drawn as stations on one line with its one gate and its return leg, a tree of what it is measured on, the evidence as input, finding and decision, and a spec ledger. On the Safe Space and Astrato files the tree is the beta and the research; on the Novo Nordisk and JBS files it is a set of design targets and says so three times, because those files claim no measured result and a blueprint may not invent one. The ledger is the part that is new in kind: six sentences per product, each written as an acceptance test, and each verified by a named check in the battery that runs before every release of this site. Spec-driven in the plain sense, with the spec on the page and the check in the right-hand column.

The figures are generated from their content rather than placed by hand, so the four files share one geometry, and the generator renumbers every figure on the page in document order. The interaction suite now drives all four products and ends with a phone pass; the canvas check covers the joins editor as well; the stills were reshot; and the five case files no longer tell a phone reader that the product is built for a desk, because four of them are not.

v7.17OCT 2026
The two products built for this site looked like the BI tools of ten years ago, and Shad said so. They were redrawn as the software people use now, and the redraw found the spread board had been showing no board at all in a small window.

The Novo Nordisk cockpit and the JBS spread board are React applications written for these case files, and both were drawn in the idiom of an enterprise dashboard from about 2015: a navy or black title bar, every label in spaced monospace capitals, flat boxes with hard borders, and a sixty-four pixel rail of icons with eight-pixel captions under them. They worked. They did not look like anything a recruiter has used this year.

The shell is light now, with the product's own mark, a breadcrumb, and its one global control in the bar where a date range sits in every other dashboard: the basis on the cockpit, the lot on the board. The sheets are named in a sidebar at a desk and become an icon rail with tooltips in a smaller window. Everything a person reads is in sentence case, and monospace is kept for what is code: field names, table names and the query. Every raised surface is the same soft card. The generated SQL is the one dark panel, with line numbers and a Copy that works, and it folds to its bar when the frame is short. The cockpit's tiles each carry a four-bar spark of the same figure on all four bases with the current one solid, which is the case file's whole argument at the size of a thumbnail, and an insight above them says in one sentence what the basis just did to group sales. The canvas nodes have icons, key markers on joined fields and a read-only mark on the validated systems, and the spread board's destinations show their redirected share as a chip.

Shooting every sheet at 912 by 570, the size of a small window, found what the old layout had been hiding. The spread board's four readings, the allocation table and the query were laid out as a strip along the bottom that wrapped at that width, and the strip took the whole height: there was no board on screen, and the note explaining the board sat on top of the numbers. The readings are one row now, their sentences fold away in a short frame, the allocation and the query moved to an inspector, and the note starts folded when there is no room for it. The board also turned out to have been drawing its tooltips and charts in the cockpit's blue, because its green skin was set on a div below the root and both of those read their colours from the root.

Two checks came with it. A new suite clicks every control in both products, nineteen assertions, because a redesign that moves every control is exactly when one stops being wired to anything. And the canvas check that lives with the products' source had been timing out unnoticed since the cockpit began opening on its matrix rather than its canvas; it opens the Model sheet first now, runs in the battery, and was shown to fail with a label pushed under a node and a shut route drawn solid.

v7.16OCT 2026
Work is a directory now: a serif title, a filter and a search, the newest case file in a tinted banner with a drawing, and every other case file and deck as a card you can open or, for the products, use.

Shad pointed at a directory page and asked for more pages in its manner, so /projects is built on its shape: a large serif title, a segmented filter for AI, health and data next to a search field, a dark button that downloads the CV, one featured item in a tinted banner with a line drawing, then two columns of quiet bordered cards, each with an icon tile, a sentence, a line of particulars and one small action. The top bar's "Work" opens it on every page, and it is in the sitemap and the palette.

It is the one page here built from cards, and that is a decision rather than a lapse. The case files lost their trays in v4.0 because a frame round a paragraph gives the paragraph a rank it has not earned. A card on this page frames nothing but itself: it is one file, and the whole card opens it. The case files, the CV and the colophon keep their unboxed sheets, and the suite that holds that line still does not list this page.

Case file 001 is the banner and is not repeated in the grid, because the same destination twice on one screen is a suite failure here. On the four other case files the title opens the case file and "Use it" opens the product running inside it, so a recruiter who wants to touch the work rather than read about it is one click from it. The five sites, decks and classes are cards with one link each. The filter and the search are a few lines of script that hide what does not match; without a script they are not shown and every card is listed, which is the whole page anyway. The serif is the one the reader's system already has, so nothing new is downloaded, and every colour is a token the contrast work already cleared, in both themes.

v7.15OCT 2026
The five case files, made modern: the sheet floats, the section bar is glass with a reading line under it, the running product sits in a browser window, every picture has depth and rises into place, and the words got a calmer, larger voice. And every case file had been printing its own name across its own drawing.

Modern here does not mean cards. The case files were unboxed in v4.0 because trays round prose read as old and tired, and a suite has held that line since, so nothing in this pass puts a frame round a paragraph. It goes where depth belongs, on the things that are pictures, and where calm belongs, on the things that are words. The sheet is rounded and lifted off the desk. The section bar is a floating glass pill that blurs what passes under it, with a thin line beneath that fills as the file is read, drawn by a scroll timeline so it costs no script. The running product is framed as a program: a window with three lights, a bar and a soft glow in the file's own accent behind it. Every demo, plate, screenshot and frame shares one corner and one shadow, and rises a few pixels into place as it enters the screen; transform only, never a fade, because a picture that is not there yet is worse than one that does not move. Body text went from 13 to 15.5 pixels with a reading line height. The callouts on the figures were sentences set in spaced monospace capitals, four lines deep, and are sentences now; their titles keep the small caps. The fixes ledger is numbered and lights the row under the pointer. The way out of a file is a large link to the next one.

The drawing in each case-file header began at 34% of the band, and the title, the lede, the kicker and the caption were allowed to run to 54%. So on every desk, at every width from 900 pixels to 1920, the first thing a reader saw was the file's name and its opening sentence printed over the boxes of its own plate. The colophon did the same with its title, and its caption had been auto-flowed into a second grid column and printed under the drawing on the right, because three of the header's four children were placed in column one by a shared rule and the fourth was placed by nothing.

The drawing now starts at the half-way line and the type stops two points short of it. The kicker wraps inside its half rather than running under the boxes, and the caption keeps its full-width rule while its words are held back. The colophon header is one column, said out loud. The first attempt at the CV's caption did nothing at all, because a width set earlier in the stylesheet at the same weight loses to the shared caption rule that comes after it; the widths now live in one desk-only block after that rule, which is also what keeps them off phones and paper.

None of the forty-one suites asked, because each of them looks at one thing at a time and this is two things in the same place. A forty-second does now: it measures the text itself, line box by line box, against the drawing's box, at five desk widths on eight pages. With the drawing put back at 34% it reports ninety-four overlaps.

And the title. It is Product Design Lead, in Shad's own words, and it replaces both titles the last four versions carried: "Senior Product Designer", which v7.12 put in front of the role so a search would find it, and "Hands-on Lead across AI, Agents and Workflows" as the name of the current role. It is now the name line under the top bar on every page, the browser tab, the search result, the headline of every link preview and every share card, the CV subtitle and its current role, the Role fields, the footer rail, the structured data and the contact card. "Hands-on across AI, agents and workflows" follows it wherever there is room, which keeps the three words a shortlisting parser is checked for. The entries below still say what the title was when they were written.

v7.14OCT 2026
The most-read line on the site carried the wrong title, every case file led with its problem, and the hero compiled its shaders before the headline could paint. And a correction to the entry below.

The first line under the top bar, on every page, on a phone, is the workspace title bar. It read "Shad Abbaslou · Hands-on Lead · AI, agents, workflows", which is the role and not the thing a recruiter is looking for. It reads "Shad Abbaslou · Senior Product Designer" now, and the hero kicker on a phone keeps the role, since the line above it has the rest.

Each case file opens on a three-part summary, and the three parts ran problem, move, proof: the order the work happened in, which is not the order a reader needs it. The outcome comes first now, or the position on the two files that claim no measured outcome, then the problem, then the move. The loud type moved with it.

The landing hero's field compiles its shaders on the main thread, and on a phone that was the longest task between the first paint and the page being usable. The field now waits for the first idle moment, or 600 milliseconds, whichever comes first, and the headline, the kicker and the caption, which are HTML, paint before it. On the same box, the same software renderer and the same uncompressed local server, Lighthouse's performance score for the landing page went from 53 to 71, 72 and 72 across three runs, largest contentful paint from 5.6 to 3.4 seconds, and total blocking time from 1,170 to about 700 milliseconds. The absolute numbers belong to that box; the direction is the point.

The fonts now carry a cache lifetime of a year and the pictures a week, so a recruiter's second page does not ask the edge for the same 170 kilobytes of type again. The display face was already a Latin subset of 262 glyphs; what it weighs is its three axes, and those are used.

The correction. The entry below said the smooth-scroll engines on offer had been read and declined. Lenis has driven the desk scroller and the strips since the motion round, and the sentence is corrected in place; what was declined were the scroll-reveal libraries. A changelog that lets a wrong sentence stand because it is already written is the kind of log the colophon says it is not.

v7.13OCT 2026
What a recruiter meets before the site: the card a link turns into, the page it turns into next, and a phone that no longer boots five applications to show five thumbnails. Then Lighthouse was run, and three things it found were real.

A link to this site is pasted into a LinkedIn message, an email or a WhatsApp thread before anyone opens it, and what appears there is assembled by a crawler that never renders the page. Every page pointed that card at a figure from the page, a WebP with nothing on it to say whose it was, and LinkedIn's crawler does not reliably render WebP; the CV and About pages, the two links a person sends when looking for work, pointed at the portrait. Each page now has a card of its own, rendered from the page's title and a line written for the card, in the site's type and palette, with the product the page is about beside it, as a JPEG under the size WhatsApp drops a preview at.

Two things from the platform itself, neither of them a library. Every document page now carries speculation rules: the next page is fetched when a link is hovered on a desk or in view on a phone, and rendered when a pointer goes down, so a case file opens as if it were already there. The products, the artifacts, the PDF and the card are excluded, because they are heavy and are never the next page. The cross-document view transitions added two rounds ago do the rest. The scroll-reveal libraries on offer were read and declined, because the drawings here already answer the scroll. Lenis, the smooth-scroll engine, has driven the desk scroller and the strips since the motion round and stays where it is.

On a phone the landing page's five cards were five iframes, which is five React applications booting on a phone to show five thumbnails, about 2.6MB of them. They show the product stills now. And the first screen on a phone said nothing about whose site it was, because the kicker that names the candidate on a desk hid below 920 pixels; it stays now, cut to the slot-able title, since the rail's name line sits directly above it.

Lighthouse was run on every page, and its accessibility audit found three things the site's own contrast suites had not asked about. The dimmed text used for the chrome, the status line, the nav links and the chips, sat at 3.52 to 1 against the paper, which is AA for large text and not for 11-pixel labels; every skin's dim ink was moved toward its body ink by computation until it clears 4.5 against the darkest surface it is printed on. The primary button's near-white text sat at 4.41 on the vermilion and 3.01 on the dark theme's orange; the button takes a computed shade of each accent now, darkened only as far as the text needs. And a link in the hero caption and one on the CV were distinguished from their sentence by colour alone, at 1.25 and 1.44 to 1 against it; the prose-link rule that underlines references inside the case files now covers them, and the CV's contact lines grew from 23.8 to 25 pixels so each is a target of its own. Accessibility went from 93, 88 and 97 on the three pages audited first to 100 on all ten.

The performance audit is the honest remainder. On a simulated slow phone against the uncompressed local server the landing page scores in the seventies: three stylesheets block the first paint, the display face is 121KB, and the field's shaders compile on the main thread. The deployed site is compressed and served from the edge, which takes most of the stylesheet cost away, and the shader cost is a software renderer's; neither number is a reason to strip the comments out of the stylesheets or to drop the drawings. It is measured now, which it was not, and the budget suite holds the bytes.

v7.12OCT 2026
The review was acted on. One title a search can find, one primary action, a still of every product for the phone, a changelog that opens on its newest entry, and a budget for what a page weighs.

The title first. "Hands-on Lead across AI, Agents and Workflows" is the role, and nobody types it into a search box. The CV header, the first screen of the landing page, the bio line and the structured data now lead with "Senior Product Designer" and keep the role after it, and the profile ends with the sentence a recruiter wants to find: what kind of role, in what kind of company. Two bullets under the current role described who sat nearby rather than what was done, and they are gone. The vendor name came out of the skills line, because an AI agent is a skill and a product is not. Each earlier role carries one title instead of two. And the contact block gives the long form of the first name, so a recruiter who has it from LinkedIn or an inbox knows it is the same person.

The landing page offered four actions in its first screen and the page below it was the answer to all four. Two now: the first case file and the CV. The line under them said the site was the evidence rather than the pitch, which is a thing to be rather than to say; it now states what he is and what he is looking for. The research thread leads with its numbers. "Shipped waves" became "shipped releases" everywhere, because a wave is a word from inside the programme and a release is a word from everywhere.

On the dossier, the "Rec" badge and the meter that read 8 / 8 implied a recording and a score, and there was neither. Both are gone. "So I stopped asking", which only worked with the found text above it, is "So I wrote my own", which works on its own. The logo strip is captioned "Clients and platforms" rather than "Shipped for and on".

The five products are built for a desk, and on a phone each case file had been offering a sentence and a button in their place. Each launch block now opens with a still of the running product, photographed from the build at 1280 by 800, so a phone reader sees the thing before being told it is elsewhere. The section labels on the first case file say what each section is: the memory, AI in the role, the live product, the pipeline. The internal names they replaced were right and meant nothing to a stranger.

This changelog opened with all forty-six entries expanded, which is twenty thousand pixels of reading before the page ends. The newest opens; the rest fold. And a new check in the battery opens the landing page and the first case file at both sizes, lets the network go quiet, and adds up what came over the wire: 0.71MB and twenty-one requests for the landing page, no product booted until the reader moves. Each number is held to a budget set a quarter above what was measured, so the day a change quietly doubles a page, the battery goes red rather than the reader's data plan.

v7.11OCT 2026
Every page read the way a recruiter reads it, in the order they arrive. The downloaded CV sent its case-file links to 127.0.0.1, the first screen of the site never said whose it was, and three files shared a number.

The CV first, because it is the page a recruiter keeps. It had gone to three sheets again, and not from the content: the contact block is a right-aligned column on screen and became five lines down the left of the paper, and the proof row had started spelling each case-file address out after its label, three broken lines of URL in a column a quarter of the page wide. On paper the addresses now sit on one line with the status under them, and the proof row keeps its label, since the address is already printed whole under the role it belongs to. The tenure label can no longer be left alone at the foot of a page with its title on the next. And the file behind the Download button is built from a local server, which a PDF remembers: every case-file link in it pointed at 127.0.0.1:8903. The build resolves them to the public host first and the check reads every link back out of the file. It also found that on a phone the header's drawing was 0px wide, a span with nothing but absolutely positioned children inside a flex column set to flex-start, so a reader saw 250px of empty ground captioned "Five roles".

The landing page's first screen said "Design that proves itself" and nothing about whose, because the name and title live in the left rail and the rail is closed by default on a desk. A line above the headline now says who; on a phone the rail's name line already leads, so it hides. The page ends on contact and the CV rather than stopping after the shelf. Three numbers were wrong in ways that only show when you hold two pages side by side: About, CV and Colophon were files 005, 006 and 007 in every navigator and on their own chips, while JBS had become 005; the strip's artifact badges said 005 to 007 for the same reason; and About's meter said seven of seven openable after two products were added. They are 006 to 008, a·1 to a·3, and eight of eight.

On a phone every case file and the colophon opened on their drawing with the title a screen below it, and the colophon's kicker was printed over the bottom rows of its grid. The headers put the title first now and the drawing after the lede, with the caption under the drawing. The employer is named on case file 001 as it is on the CV; the programme and the platform at the end of it stay unnamed. Every sign-off offers the CV and About offers a contact card. Every page was preloading a typeface that left in v6.0.

Two things came in behind the review. The availability line reads "Open to global roles" everywhere it appears: status bars, the ID card, the CV header and the contact card. And on a phone every hero is now driven by the scroll. The plates, which draw the hero of every case file, the CV and the colophon and every section figure, had still been resolving on a 1.4 second clock the moment they entered the screen, and the landing hero had been exempt from the scroll as the one field on screen at open, which made it the one drawing a phone reader sees first that still ran on a timer. A plate now takes its state from how far it has risen up the screen, the same curve the fields use, and comes apart again when scrolled back; a finger on one still assembling finishes it, so nothing the reader is invited to hold refuses the hand. The climb is bent as well, because every build here is front-loaded and on a straight line half the scroll had drawn nine tenths of the picture. The heroes carry a longer climb, the landing field and the seven plates alike, so it opens part-formed under the headline and the first three hundred pixels of scroll finish it.

The scroll check had been flaking on a loaded box because it sampled a fixed time after the resolve, and a parallax chase at sixty frames of lerp can still be moving then. The field marks itself idle when its loop stops, the check waits for the mark, and a planted never-idle clock is reported by name. One more thing was learned and written down rather than fixed: after a programmatic scroll, the headless compositor sometimes serves a stale, empty frame of the whole page while the DOM and an element screenshot are intact. It is the renderer, not the site, and a wheel tick clears it.

v7.10OCT 2026
The CV was printed and then read back with a PDF parser, the way a shortlisting system reads it. It came out in the wrong order, and the candidate's name was two thirds of the way down the file.

Everything before this had been checked by looking at the page. That tells you nothing about this, because a PDF's text stream follows the paint order, not the document order, and CSS written for a rich screen moves things out of the normal flow constantly. Read back, the file opened on the word PROFILE. The name arrived after the entire experience section. Every bullet on the CV had been emitted together in one block at the end, so each role read as a title followed immediately by the next title, with no evidence between them. The section labels came out as P R O F I L E and E X P E R I E N C E, which is one of the specific failures Greenhouse names.

Four separate causes, none of them visible on the page. A grid on the document put the name after the experience section. The name and contact blocks are position:relative with a z-index so they sit above the drawing behind the header, and a positioned box paints after every in-flow box, so they were emitted last. Every bullet was position:relative so its accent dash could hang off the left, which did the same thing to all forty of them at once. And the letter-spacing that made the section labels look considered was being emitted letter by letter.

In print the CV is now a single column in normal flow, the dashes are real list markers rather than absolutely positioned pseudo-elements, and tracking is held low enough to survive extraction. Read back now it goes name, profile, the four figures, experience, each role with its own evidence under it, skills, education. Which is what it always looked like.

The research behind the rest of it is ordinary and worth saying plainly: a UK CV for a senior role is two A4 pages with a short profile at the top, recruiters scan the top band and then down the left margin, and parsers want one column, standard section names and no tables or text boxes. The sheet is set to that. What it is not set to is a template: the type, the rules and the vermilion are the site's own.

There is a check for all of it now, in tools/, outside the deployed directory. It prints the CV with background graphics on and off, reads both back, and asserts the order, the file size, the page count, that the email and LinkedIn address extract as text, and that no line has its letters spaced apart. It was confirmed by putting the original bug back and watching it fail.

v7.9OCT 2026
Getting the CV onto two pages had been done by taking space out of it, which is not the same as designing it. It is set properly now: a date rail, the house vermilion, and a measure you can actually read.

The version before this one hit two pages by shaving line height, padding and margin until the sheet gave in. It fit, and it read like a form. The fix was never whitespace: it was that the layout was wrong. Two breakpoints were the whole problem, and both of them are the same mistake. An A4 page is about 688px wide at 96dpi, so print was falling under the 860px where the header stacks for phones and under the 700px where the date column collapses. The printed CV had been taking the narrow-phone layout the entire time.

With the rail restored the sheet has a spine: dates down the left in spaced mono, roles and evidence to the right. Skills and education sit side by side rather than stacking two short lists down a long page, which alone gave back about ninety vertical points. All of that bought room, and the room went back into the document: section spacing, line height and the gaps between bullets are all more generous than before the squeeze, and it still lands inside two pages with about a hundred and fifty points to spare.

The ink was wrong too. The print block had been declaring its own accent, a blue belonging to nothing, so printed links came out blue while the bullet dashes beside them stayed vermilion. Both are the house #d6400f now, and the accent does structural work: a rule under the header, the section labels, the rules over the four proof figures and the figures themselves, set in Bricolage rather than body text.

One typographic correction worth naming. The profile ran the full width of the page, about ninety-five characters a line, which is half again what anyone reads comfortably. It is held to seventy-four now. The proof strip under it still spans the full measure, so the page keeps a wide element and a narrow one rather than one column of everything.

None of this is background art. Browsers print with background graphics switched off by default, so a sheet that leans on filled panels arrives blank. Every mark here is type, rule or ink colour, all of which print either way.

v7.8OCT 2026
The CV lost a third of its first page to a gap, printed a blank third sheet, weighed 4.5MB, and could tell a machine the wrong number. All four were the same kind of fault: nobody had read the document the way a machine does.

Printing the CV produced three sheets for two pages of writing. An A4 page is about 688px wide, which is under the 860px where the header stacks for phones, so print was taking the narrow layout: the contact block sat full width under the name with two thirds of its band empty. Worse, no role was allowed to break across a page, so the first one, 548px of it, could not fit the 400px left at the foot of page one and moved to page two whole, leaving that much of page one blank. Roles break now, a heading still travels with the lines under it, no single bullet splits, and the contact sits beside the name where it costs the taller of the two rather than the sum. Two pages, and the first one is full.

The third sheet was worse than it looked: it carried no text at all. Two pages of content were overflowing their second page by nine pixels and taking a blank sheet with them. The spacing is set to land inside two pages now, with room to spare so a different browser cannot tip it back.

A stray closing brace in stage.css, left behind when the grain jitter came out, had been quietly deleting the rule that follows it: @media print{ .grain{display:none} }. A brace with nothing open is a parse error, and the browser recovers by discarding the next rule. So every printed page on this site, for as long as that brace has been there, carried a full-viewport noise tile: a grey wash over the text, and a CV that weighed 4.5MB instead of 0.21MB. That is the difference between a file an application form accepts and one it rejects.

Then the number that was not itself. The figures on this site count up from zero when they scroll into view, rewriting the element's text on every frame for 900ms. Look at the page and you see a flourish. Read the page, as a shortlisting tool does, and for most of a second the CV says 58% on its way to 80, and 68% on its way to 94. Measured at 300ms, that is exactly what came out. The CV does not animate at all now, because it is a document of record, and everywhere else any counter still in flight is snapped to its true value before the page is printed.

Last, the CV now carries a machine-readable copy of itself as schema.org/Person: the name, the title, the two cities, both degrees and their awarding universities, what the work is about, and where to write. It states nothing the page does not already state in words. The one thing still missing is dates, which cannot be invented.

v7.7OCT 2026
The two client boards were hand-written single files pretending to be applications. They are applications now: React, an interactive canvas, and a component kit shared between them.

Both products shipped last version as one HTML file each, with the charts drawn by hand into SVG strings. That is fine for a picture and dishonest for something a case file calls a running product. They are rebuilt as real applications: React 19, React Flow for the canvas, Recharts for every chart, and a shadcn component kit, Radix underneath with class-variance-authority for the variants, shared by both and re-skinned through CSS variables so one kit serves a clinical blue and a sustainability green without a fork.

The canvas is the part that earns the rebuild. On Novo Nordisk it is the semantic layer itself: five validated source systems and an FX table laid out as draggable tables, each with its fields, its row count and its GxP stamp, joined into v_group_sales by animated edges labelled with the join condition. The fields that carry a join light up. It is the screen the case file argues about, rather than a drawing of it. On JBS it is the lot's path, and it moves: pull a destination's export approval and that node goes dashed at zero per cent, its edge thins to nothing, and a thick line opens to the domestic market carrying the redirected share, with the spread turning negative beside it. The argument of that file is that an approval is a price, and the canvas now demonstrates it rather than asserting it.

Nothing is fetched at runtime. Both bundles are built with esbuild and vendored into the site, because the sweep suite fails the build on any external request, and a portfolio that needs a CDN to render is a portfolio that breaks when the CDN does. The cost is honest and worth stating: each bundle is about 275KB over the wire, most of it Recharts, loaded lazily inside the case file's frame rather than on the landing page.

Four legibility bugs came out of looking at the canvases rather than at the code. React Flow draws an animated edge as a marching dash, and on the JBS board a dash is what a shut route looks like, so a live edge and a dead one were telling the same story to anyone reading a still frame or running with reduced motion: only the spine, which is never shut, is allowed to move now, and only for a reader who has not asked for stillness. React Flow also draws an edge label in the same layer as the lines, so a later edge paints straight over an earlier edge's label; the redirect edge was cutting a destination's share in half and a join condition was being crossed by its neighbour. Labels now sit in a layer above every line, anchored beside the table they leave rather than at the midpoint, where edges converging on one target had been landing on each other. The note that explains each canvas folds away, because on the Novo model it was sitting on top of a table.

The links suite caught something that would have shipped broken. Both shells referenced their bundle as ./app.js, which resolves correctly at /products/novo/ and resolves to /products/app.js at /products/novo, where the site actually serves them. A relative path that depends on a trailing slash is not a path, it is a coin toss; both now use absolute ones. A phone gets the house treatment rather than a layout that cannot work: the banner says what the application is and sends the reader to the case file.

v7.6OCT 2026
Villa Plus comes off the shelf and two Astrato client engagements go on it, written as reconstructions rather than as the work itself, because the work itself is under NDA.

Three years on Astrato is already case file 002, but it is told from inside the product: the join canvas, the research, the AI assistant. What it never showed was the work the platform was actually bought for. Two of those engagements are now files of their own. Novo Nordisk is a reporting layer for a company whose sales rose 32% and fell 4% in the same quarter, both correctly, because reported and adjusted figures on two currency bases were circulating without labels. JBS is a spread board for a company that turns over BRL 417bn and keeps about 2.3% of it, where the margin is set in three systems on three clocks and one carcass becomes dozens of cuts sold into markets that do not share a price.

Both are built on a rule that had to be settled before anything was drawn. The engagements were real and the delivered artefacts are confidential, so nothing on either page is presented as a measured project outcome. There is no adoption rate, no time saved and no margin gained, because that evidence cannot be shown. What the pages do carry is public: Novo Nordisk's own reported figures, JBS's own reported figures, and the design positions, which are mine and arguable either way. Each file says all of this in its source notes rather than in a disclaimer nobody reads, and the two palettes are informed by each client's identity rather than copied from it, with no logo or trade dress anywhere. Neither company publishes hex values for its current brand.

Both products are rebuilt and running inside their files, as the other four are. The Novo cockpit has one control that matters: switch the basis and every figure restates, including the two that cross zero, and the tiles that changed sign say so. The JBS board shows a spread that knows how finished it is, and if you withdraw a plant's export approval for a destination, you watch a third of the lot redirect to the domestic market at a lower index and a thin profit turn into a loss. That is the argument of the file, made operable rather than asserted.

Villa Plus is retired as a case file, not as history. The page, the booking demo and the deck are gone, with every navigator row, index card, sitemap entry and command-palette entry that pointed at them. The Sole Designer role stays on the CV, the client logo stays in the About strip, the eleven-month bar stays in the tenure plate and the changelog below keeps every word it ever said about the work, because a log that edits its own past is not a log.

Two things went wrong doing it and both are worth recording. A cleanup pattern meant to remove one orphaned mobile card matched from the first card to the last and deleted three good ones as well, which the diff caught and nothing else would have. And a version-bump script, told to replace a version string everywhere, obligingly renamed the newest changelog entry so that the old entry claimed to be the new one. Both were the same mistake: a pattern aimed at one thing, loosed across a file.

The counts went stale too, which on this site matters more than it would elsewhere. The front door said seven files and four running products, the 404 offered four case files and six artifacts, the About page counted seven of something. There are five case files, five running products, five artifacts and eight files in the navigator, and all of those now say so. The figure suite grew a check at the same time: a label drawn inside a filled bar is not sitting on the section background, it is sitting on the bar, often in the same ink, so every label is now measured against whatever shape is actually behind it. That found three unreadable labels on the new JBS plates within a minute of being written.

v7.5OCT 2026
Two case files drew the detail before they drew the premise, six figure numbers were used twice, and an entire drawing vocabulary had never once been checked for whether it was visible.

Read cold, the NHS and Astrato files had the same fault, and it was not a shortage of pictures. Both had diagrams for the mechanism and none for the premise, so a first-time reader met the privacy boundary before the hour that the service exists to fill, and the redesigned join canvas before any reason to care that a tangled one costs money. Two plates now open those arguments: FIG. 001 on Safe Space draws a fortnight as fourteen days, thirteen of them empty, against the one hour a clinician gets to account for all of it; FIG. 002 on Astrato follows a drawing problem along five stations to the warehouse meter it ends up on, because an analyst who cannot read a model does not file a bug, they quietly build a second one.

Four words were doing work they had not earned. The Safe Space page opened its first sentence on CAMHS and the Astrato page on a Snowflake warehouse and a join, none of them expanded, and the GDS Service Standard appeared as GDS #2, which reads as a version number unless you already know it numbers a standard. Each is now said plainly once, where it is first used, and the warehouse gloss carries its meter so the figure that follows has something to land on.

Drawing the premise is also how I found that the page disagreed with itself about how often any of this happened. The headline and the problem strap said an hour a week; the triangle plate said the clinician gets fifty minutes a fortnight, and so did the ledger. The delivered artifact settles it, saying an hour a fortnight three times and counting the unseen remainder as three hundred and thirty-five hours, which is a fortnight to the hour. The case file had drifted from the deck it was written from in two places and nothing caught it, because every check here reads structure and none of them read agreement. The headline now says what the evidence says, and a suite holds each case file against the artifact it came from on the claims that have already gone wrong once.

The figure numbers were worse than untidy. Across the four case files six numbers were used twice, one page had FIG. 001 three times, and two different plates were both called the discovery programme, because diagrams and canvas plates are numbered in separate families and had been renumbered apart. On a site whose whole argument is that a number carries its source, a figure number that repeats is the cheapest available way to lose the reader. They now run in document order, and a suite fails the build if two share a number or a title.

The last of it was invisible, in the literal sense. The diagram vocabulary is a set of CSS classes, so a figure that names one wrong still parses, still lays out, and still passes every check that reads the DOM: it just paints nothing. A return line on the new Astrato plate was given spine-return, which sets only a dash pattern and takes its stroke from spine, so it drew a line with no colour and I had been squinting at the screenshot wondering why the figure felt unfinished. Chasing that turned up more: SVG text uses fill rather than color, so the contrast suite had never measured a single label in any figure on the site. Eight of them were on the token reserved for incidental text and sat between 3.2 and 4.0 against their background, including the one carrying 860.6k queries served live. Two more set a font and no fill at all, which falls back to black and would have been invisible the first time anyone used them on a dark ground. A new suite now measures every label against what is actually painted behind it, in both themes, and injects a figure using the whole vocabulary into a normal section and an inverted one so the next plate inherits values that already pass.

v7.4OCT 2026
A shared link to the one section people would share landed underneath the bar, and the heaviest file on the site was buying detail nothing ever showed.

Every section on a case file carries a scroll offset so that arriving by link does not put it under the sticky bar. The offset was written against .sec, and the block that runs the live product is .launch, so it was the single section in the navigator that arrived wrong: 52 pixels of clearance where its neighbours get 169, which on a phone put the top of the launch bar behind the chrome. It is the most linkable thing on the page, because it is the part worth sending someone. The rule is written against being a destination now rather than against a class name, and a suite, deeplink, opens all fifty-two section links on both widths and fails any that does not land clear. The existing anchors suite could not have caught it: that one checks where section headings land, and this block has no heading.

And the last JPEG. Every other picture here is WebP; the portrait was 286KB, the heaviest single file on the site, and what it feeds is a one-bit dither that samples it down to a few hundred pixels and throws away every tone in between. The detail that weight was buying never reached the screen. At 102KB the rendered dither is indistinguishable, and the About page drops from 1,009KB to 826KB. The JPEG stays in the tree because the social card points at it: a card that will not unfurl on LinkedIn is a worse failure than a larger file nobody visiting the site downloads.

v7.3OCT 2026
The printed CV opened with a caption for a drawing that is not on the paper, ending in an instruction to hold it.

This site has a button that says Print / save as PDF, and for a lot of readers the PDF is the thing that outlives the visit. Nothing had ever looked at what came out of it. Almost everything was right: the chrome goes, the grounds revert to paper, the case-file links print as full addresses so a reader holding the page can type them. But print removes the drawings and was leaving their captions behind, so the CV opened with Four roles, drawn to length against each other. Hold one. set above nothing at all. Eight more pages had the same thing, and the About page printed the words Source.exe as the title bar of a window with no window in it.

Two rules, both general. Nothing that invites a pointer survives onto paper, which is checkable because every run a hand along them and pull one out on this site is already marked as one. And a caption may not outlive its figure: if print takes the drawing away, the words describing it go too. A suite, printed, renders every page at A4 less its margins and fails anything left pointing at something that is not there.

The fix for the window title had to be written into the stylesheet that owns the window rather than the one that owns the page. Both set the same property on the same selector at the same specificity, and the dossier sheet loads second, so the same line written in the other file was simply overruled. It is noted in both places, because a rule that exists in the wrong file looks like a rule that does not work.

v7.2OCT 2026
The loudest button on every case file sent a phone into a desk product with no way out, and a mistyped address was a dead end.

Four products are rebuilt and running on this site, and Use the product is the primary action in the bar of every case file. On a phone that lands in an analytics workbook or a clinical dashboard at 390 pixels, with its panels drawn on top of each other and its toolbar text overlapping itself. The product's own way back lives in that toolbar, so there was no way out either. The case files already warn a phone reader before they tap; the product pages said nothing once they had. Each of the four now opens with a line in this site's voice rather than the product's: what it is, that it is the real interface at the size it was designed for rather than a shrunken one, and a link to the file that explains it. The products themselves are untouched. Shrinking a delivered product to fit a phone would be a different claim about the work than the true one.

There was no 404. A mistyped address, or a link to a page that has since moved, landed on the host's own error screen: someone else's branding, no way back, and nothing to say the site was still there. There is one now, and it is a file in the workspace like any other: it says the path is not here, and then lists everything that is, all four case files, all four products and all six artifacts, each one a tap away. Its headline is set smaller than every other page's on purpose, because on this one page the list underneath is the point and the full size pushed every recovery link below the fold.

Two things that came out of building it. The list of files renders inside a document here, and the rule that underlines references written inside a paragraph was matching list items too, drawing one line under all three lines of each card; a block a reader clicks as a whole is not prose with a reference in it, so it is excluded now. And a check that should have existed from the start: nojs loads every page with scripts disabled and fails any that stops reading. It passes today, but the reveal-on-scroll class is added by JavaScript and hidden by CSS, so the day someone moves that class into the HTML the whole site goes blank for anyone behind a proxy that strips scripts. That is worth a suite even while it is green.

v7.1OCT 2026
The same door offered twice, five times over, four pixels of sideways scroll on a small phone, and eight pages that unfurled as a grey rectangle.

Three of the findings in the previous pass were the same shape: a destination offered twice within a screen or two. All three were found by eye, which is not a method, so this one is a suite. For every link on a page, if the same destination appears more than once and two of those appearances fall within a viewport of each other, twice says so. It found five more. Each case file offered its deck three times: once in the sticky bar, once on the live embed with the thing running inside it, and once again in the footer three hundred pixels below that embed. The About page offered Copy email and LinkedIn as a pair, then the identical pair again in the sign-off, with eight lines of source notes in between. The footers are the sign-off now and nothing else.

The suite exempts the frame, because a top bar and a breadcrumb repeating a link is navigation doing its job, and it exempts captions, because a caption naming where a figure's number comes from is a citation rather than a second offer. The landing hero says 3,444 points, one per token in the system, case file 001 and a button below it says Open case file 001; collapsing those would take the citation off a figure whose whole argument is that its numbers are checkable.

A second suite for a width nothing had been looked at: narrow loads every page at 320 CSS pixels, the smallest phone still in real use, and fails any that scrolls sideways. One did. The comparison table on case file 004 held its first column on one line, which is right down to about 390 and wrong below it: three columns and their padding came to 324 in a 320 window, and the whole page slid under the thumb. A label on two lines is the better trade.

And the part of a first impression that cannot be checked by looking at the site, because it is assembled from tags nothing on the page renders: the card that unfurls when a link is pasted into Slack, LinkedIn or a message. Eight of fourteen pages had no og:image at all, among them the CV and the About page, which are precisely the two links a person sends when they are looking for work. Those unfurled as a bare title on a grey rectangle. Four more had a picture but no twitter:card, so they collapsed to a thumbnail. Every page this site owns now names itself, describes itself and points at a picture that is really there, with alt text on it, and a third suite, social, checks that the file on the end of each of those URLs exists on disk rather than being a path someone typed.

Also corrected: the shelf plate's own note claimed the four spines take a third of the width. They take 17% at 1354, because a ceiling on how wide a weight unit may grow overrules the third on anything wider than a phone, and that ceiling is the right rule: nine units at a true third would be a 178-pixel spine on a 198-pixel drawing, which is a slab, and slabs are what that plate was rewritten to stop drawing.

v7.0OCT 2026
Read cold, on a phone, as someone who had never seen it: seven captions ran off the edge of their own drawings and the one fact this site exists to deliver was hidden.

Every check here reads the document. The plates do not put their labels in the document: they paint them into a bitmap, and a bitmap has no line box, no overflow and no complaint, so a caption written one pixel too long simply stops existing and looks exactly like a caption that was meant to end there. Seven of them were doing that on a phone. The shelf that closes this site's landing page lost the last three words of FOUR DELIVERED ARTIFACTS, AS HANDED OVER; the readout on the CV's own plate lost 291 pixels of a sentence about usability testing. Captions now measure the room they have, shrink a step, wrap, and only cut as a last resort. A new suite, ink, wraps fillText before the page's scripts run, measures every string where it actually lands, maps it through whatever transform is in force, and fails anything that leaves the canvas. It runs a hand across each plate first, because several swap their caption for a longer one under a pointer and the first string a plate draws is rarely the longest it can.

Three of the grounds that invert the palette redefined --line and forgot --line-strong, which is the token a button draws its outline from. So the contact buttons on the dark shelf were painting a dark ink at 24% alpha onto a near-black ground: a border darker than the thing behind it, which is to say none. They read as indented text, which is the one thing a button must not do. A second suite, edges, composites every border over what is actually behind it and fails any that cannot be told apart from it. Its floor of 1.12:1 is measured, not chosen: the faintest line this site draws on purpose sits at 1.15, and the broken ones were between 1.00 and 1.09. It also found a border nobody had written, where the demo chips on case file 001 were inheriting a hairline from the site's own .chip.

Then the reading itself. ⌘K sat in the top bar of every page on a touch screen, naming a key the reader does not have, and it was the only search affordance there; it is a magnifying glass now. Open to UK roles was hidden below 920px, which is to say hidden from almost everyone who opens this link, since a portfolio sent to a recruiter is read on a phone. It is the single fact this site exists to deliver and it appeared nowhere else on the page. The bar had the room all along.

And three things said twice. The navigator's bio line, which is chrome in the left rail on a desk, became the opening paragraph on a phone and introduced the same name, title and two cities as the panel one screen below it. Three live artifacts chips sat directly above the shelf section that lists the same three with a line each saying what is in them, plus the three client decks. The CV offered Print / PDF in the bar and Print / save as PDF four hundred pixels later. The phone keeps one of each. Contact used to sit in the middle of the landing page, so the page offered an email address and then carried on for another section; a reader who takes a contact block as the end of a page is reading it correctly, so it is the end now.

v6.9OCT 2026
Every slide in all three client decks was stretched to four times its height on a phone, and the extra was most of the scroll.

The width and height attributes on an <img> are not only a hint for reserving space before the file arrives. They are presentational hints that map to the CSS width and height properties. Every rule on this site that sized a picture set width:100% and never mentioned height, so the width hint was overridden and the height hint was left standing as a literal pixel value. A slide exported at 1500 by 869, laid out 354 wide on a phone, kept its 869 pixels of height, and object-fit defaults to fill, so it was squeezed to under a quarter of its width. Every letter on it became a vertical smear. Thirty-eight slides, three decks, and the evidence this site rests on.

The fix is height:auto on the base img rule, which is one line and was the whole bug. It takes about twenty-seven thousand pixels out of the three decks, because that height was never anything but the distortion: Safe Space falls from forty-one phone screens to twenty-four, Astrato from twenty-five to seventeen, Villa Plus from twenty-six to nineteen. Nothing was cropped and no slide was shrunk to buy it back.

Two of those slides also declared a shape their file does not have, which is why they were the worst of them, and fifteen more pictures, including both screen recordings, declared no dimensions at all and so reserved no space, growing the page under the reader's thumb as each one loaded. All fifty-three that have a pixel size now state the real width and height of the file they point at, read out of the files rather than retyped. The five remaining are the client logos, which are SVG and have no pixel size to state, and which the stylesheet gives a fixed height anyway.

Two new suites, making twenty-seven. shape compares every picture's rendered box against the dimensions of the image inside it, at both widths, and fails any that is not the shape it claims; put the old rule back and it fails ninety-six of the hundred and sixteen it looks at. dims asks the question shape cannot, because a browser can only be measured after the answer has stopped mattering: before the bytes arrive, does the box reserve the right room? It reads the sizes out of the image files themselves rather than trusting a typed number. No existing suite could have caught any of this. clip and boxes check that things stay inside their containers, which these did; a11y checks the alt text, which was correct; figures checks the numbers in the captions. None of them asked the only question that matters about a photograph. The entries below this one were also in the wrong order, newest second, which is fixed.

v6.8OCT 2026
Two of the longest things here were long for no reason anybody chose.

On a phone the landing screen met every case as a card, and then met all seven again as a track running off the right edge: the same files twice, 360px of pure repeat. A track you push sideways is a pointer affordance and the kind of thing a thumb scrolls straight past, and the cards underneath it were built for that width and run the real product in each one. The cards win on a phone; the track keeps the desk.

The colophon was worse and more embarrassing, because it is the page about how carefully this site is made. Thirty-one changelog entries came to 18,980px, which is 62% of the page and, at phone width, twenty-two screens of one section. Every entry already opened on a sentence saying what that version was about, so that sentence is the summary now and the rest sits behind it: you scan thirty-one headlines and open the one you want. They are open in the markup, so a desk reader and anyone with JavaScript off sees exactly what they saw before, and an entry a reader opens by hand stays open when the phone turns. The colophon went from thirty-six screens to under eighteen.

What is still long is the three client decks, at twenty-five to forty-one screens, and that is not an accident of layout: better than half of each page is the slides themselves, twenty of them on Safe Space at roughly a screen each. A deck is a slideshow, and a crop of a slide at phone width is already at the limit of readable. Shrinking them to save scrolling would make the evidence harder to read in order to make the page shorter, which is the wrong trade to make on somebody's behalf, so it is written down here rather than quietly done.

v6.7OCT 2026
Every drawing on this site invited a hand, and on a phone not one of them answered.

The argument this whole site makes is that its drawings are models rather than pictures, and each one is captioned to say so: run a hand along them, pull one out. On a touch screen all twenty-four were dead, for three separate reasons, and the suite that exists to catch exactly this passed throughout because it asks with a mouse.

The first is the one worth keeping. pointermove had a branch for dragging and a branch for hovering, which is the right shape for a mouse: it has a moving state and a moving-while-pressed state. A finger has only the second. Every touch move arrived with dragging true, took the drag branch, found no move and no scrub on a plate that defines only hover, which is most of them, changed nothing and returned. A finger's position is the hover; it falls through to it now. The second: .casefield is pointer-events:none until .plate-live turns it on, and that class was only added where (hover:hover) matched, so the hero plate on all four case files was not merely uninvited on a phone, it was unreachable. The third: neither plate wrapper set a touch-action, so the browser claimed the drag for scrolling and cancelled the pointer stream before a move was delivered. The one interactive thing that did work on a phone was the before and after slider, which is also the only place touch-action had ever been set.

A twenty-fifth suite, touch, now drags a finger across all twenty-four plates on every page that has one and fails any that does not answer. It found one more on its first run, which turned out to be the suite's fault rather than the site's: bench hit-tests against its own bars, and a single sweep across the waist can pass between everything, so it sweeps at three heights now. The invitations are shown to touch readers again, having been hidden on the honest grounds that they were not true.

v6.6OCT 2026
The check this site is proudest of had one number to look for.

v6.2 built assets/figures.js so that a figure corrected in one place could not be left standing in six others, and the suite's own header calls that the regression that matters. It works by reading each figure's supersedes field and hunting the retired value across every page. Only one figure in the whole canon ever declared one. The token count declared that it replaced 3,491 and was policed accordingly; the component library, the figure the entire section was written about, declared nothing, so 216, 220 and 214 were never being looked for anywhere, and neither was the 93 the rule book was published at before two retired rules were counted properly. The page said the numbers were governed. Three of the four were not.

So one of them was still here. The shelf of delivered artifacts draws its spines on a canvas, and the first spine was labelled 9 pages · a 216-component explorer, painted onto the landing screen, two lines from a list that correctly said 231. It had survived the canon, the suite and every battery run since, because the suite reads rendered text and text drawn into a bitmap is not text to anything reading the DOM. The number this site wrote a whole section about having got wrong was on its front page, in the one place nothing was looking.

Three fixes, in increasing order of how much they matter. The label says 231. The canon declares what it replaced, and the suite accepts a list rather than a single value, because a library published as three different numbers needs to disown three. And a fourth check reads the string literals in assets/*.js, comments stripped, which is exactly the text the site utters and leaves hash seeds and coordinates alone. One page is supposed to print retired figures, and rewriting it to avoid naming them would delete the only honest record of the mistake, so the exemption is an attribute on the two blocks whose job it is and one sentence on case file 001, marked in the HTML where a reader can see it rather than as a page name hidden inside the test.

Both new checks were then proved rather than assumed: the retired figure was planted back, once in a canvas label and once in ordinary prose outside the exempt blocks, and each check failed on it before being restored. A check that has never been seen to fail is a check nobody has tested. One latent version of the same fault went too: plate.js defaulted a missing data-nodes to 216, so the next plate that forgot to say what it counted would have quietly drawn the retired figure. It refuses now, and says so in the console.

v6.5OCT 2026
Everything on this site had been looked at on a desk.

Walking the three rebuilt decks at 390 found a fault that had been there since the workspace was built. --viewhead is a constant, 40px, and three things are positioned off it: the breadcrumb bar's own height, the section navigator's sticky top, and every section's scroll margin. Below 700px the bar is allowed to wrap, because the crumbs need their own row and the actions wrap under them, and it comes out at 101px while the constant stays 40. So the navigator stuck sixty-one pixels too high and spent the entire page hidden behind the bar, which on a phone is the only navigation there is, the sidenav having been hidden at that width on purpose. Anchors landed with their headings under the chrome for the same reason. Neither height can be hard coded, because the bar wraps around its own buttons and the navigator around its own section names and both differ per page, so the stack measures itself now and publishes what it found; the constants stay as fallbacks, so with no JavaScript this is exactly what it was. The anchors suite had not caught any of it because it only ever ran at 1440, which is a check for one width rather than a check. It runs at 390 too now, 112 jumps across seven pages.

Worse, and from the same habit: the three deck pages had never been through the accessibility suite at all. They were rebuilt onto the workspace shell and never added to the list of pages that use it, so the newest pages on the site were the only ones with no check on them. Running them found fifteen drawn plates with no text alternative. Each carries a full description in its aria-label, which serves a screen reader and does nothing at all for a sighted reader at 200% zoom, where an 1100-wide drawing is the one thing on the page that cannot reflow. WCAG 1.4.10 exempts content that genuinely needs two dimensions, but only where it is actually available another way. The generator emits the disclosure now, printing the same sentence it already wrote for the label rather than a second one that could drift from it, and the fifteen already in the pages were backfilled from their own labels.

One more slide went. Slide 08 was the four research questions discovery closed on, set as text in a two-by-two grid and exported, under a heading on this site saying that one of them has no clean answer, which the picture did not show, or say which, or say what answered the other three. That is the entire content of the figure, so it is drawn: three questions joined to the thing that answered them, and the third, better communication across the Triangle of Care without compromising anybody's trust, with its connector drawn and then cut, because there are forty-six points between what a teenager will permit and what a parent wants and no feature closes that. The product chose a side and said so. Also fixed while drawing it: .lab.hot and .fig.hot were being set in the markup and styled by nothing, so a row could be marked as the point of its own figure and come out looking like every other row.

v6.4OCT 2026
Rebuilding the decks put the evidence in the building, and then left it there.

Each of these cases turns on a single finding, and in two of the four the case file never said what it was. Safe Space is an argument about consent, and the measurement that settles it, the same question asked of both sides, was only ever on the deck: 64% of teenagers are comfortable with a clinician reading their entries, 34% with a parent seeing their activity, and 80% of parents want exactly that. Two of the three relationships in the Triangle of Care are uncontested and one is not, by forty-six points, inside the same family about the same screen, and that gap is the reason the product has the shape it has. It is drawn on the case file now rather than described, as a separate figure from the triangle in the brief, because the brief's triangle is who is involved and this is who disagrees. The records pass got its number back too: 65% of serious incidents in the preceding year had warning signs a tracking tool could have caught, which is the sentence that justifies the project existing. Villa Plus had the same shape of hole in a commercial register. The product team already knew that a sudden price change on the flight page cost 12% of conversion, and read the right way round that stops being a problem and becomes a budget: the surprise was already being paid for, so explaining it was funded before it shipped. That is the sentence that got the work approved and it was nowhere on the page describing the work.

Drawing the first of those exposed a mistake in where the drawing vocabulary lives. The chart primitives, the lane and the bar and the weighted edge, were written into deck.css under a comment saying they live there because only the decks need them, which was true for about a week. A case file that states a finding has to be able to draw one, and the case files do not load that stylesheet, so the lane and the bar both fell back to the SVG default fill and rendered as one black rectangle: three bars of 64, 34 and 80 per cent, all exactly the same length, each one covering its own lane. It measured correctly, it validated, and it was a lie you could see from across the room. The primitives moved to stage.css beside the rest of the plate idiom, and deck.css keeps only what is genuinely about being a deck.

The last one is the kind of fault a site acquires by being mostly chrome. site.css opens with a{color:inherit;text-decoration:none}, which is correct for a page whose topbar items, navigator rows, cards and buttons all carry their own affordance. In running prose it means a link inherits everything from the sentence around it and becomes invisible. Fifteen had accumulated, and they were not incidental ones: they were every cross reference between a case file and its deck, which is the one trip across this site the whole structure exists to support. An unclassed link in a paragraph, a list item, a table cell or a caption now takes the accent and a pale underline held off the baseline, and a link carrying a class is left alone on the grounds that it was styled on purpose. A twenty-fourth suite, inline, walks all twenty-eight pages and fails on any link in running text that matches the colour of the text around it with no underline, no border and no ground of its own.

v6.3OCT 2026
Three pages were still arguing for a version of this work that had been superseded, in a typeface this site stopped using.

The client deep dives at /artifacts/astrato, /artifacts/safe-space and /artifacts/villa-plus were the 2025 presentation sites, untouched: Instrument Serif, a palette of their own, no navigator, no theme, no status bar. Every case file carried a button to them labelled "live case study", so the best-argued pages on the site ended with an exit into the weakest. All three are rebuilt on the site's own stylesheets with the workspace chrome, and they are rows in the navigator now rather than a way out. The division of labour is stated on each: the case file argues, the deck shows the evidence. Each got a thesis instead of a summary, because "forty features, two pods, one system" is a throughput claim and the interesting claim is that the forty behave like one product. Fifty-four slides were cropped and re-encoded from the original Figma exports through a reviewable manifest rather than by hand, which took the largest from 2,089KB to 40KB, but the weight was the smaller reason. Then fourteen of them were thrown away and drawn again, because roughly two thirds of a deck is never a picture: it is a heading, three bullets and a coloured corner, and a screenshot of a paragraph is the least informative thing a figure can be. The ones carrying an argument are now plates in the same idiom as the case files, generated from one script so they cannot drift apart: the Triangle of Care with its edges weighted by the survey that measured them, both surveys on one scale so the gap between what teenagers will allow and what parents want is visible rather than described, the three-month programme as it was shown before it ran, the sharing boundary with its gate and its three struck refusals, the group total built in four attributed steps, and the ticket VK-4532 read twice, once as engineering and once as design, with the fourth constraint drawn severed and marked not taken. The ones that were genuinely pictures, a product, an attention heatmap, a before and after of a data model, are still the original export, because a drawing of a screenshot is a worse claim rather than a better one. Most of these slides are two columns, an argument and a photograph of the people it came from, and those people are real teenagers in a mental-health service, real colleagues, and real customers boarding a plane; none of them agreed to appear in a portfolio. No photograph of a person appears on the Safe Space deck at all, and the page says so and says why: a case study about consent that publishes faces to prove it did the work has not understood its own argument. Evidence that had been sitting in those decks for a year and had never reached the site is now on the case files too, which is where the gap was most obvious: the Villa Plus outcome section carried no business numbers whatsoever before this, and the launch report has conversion up 12% for groups of five to nine and 18% for ten or more, drop-off from flight to payment down 30%, price-related support queries down 25% and booking NPS up fifteen points. Safe Space gained its beta report, 94% of twenty-one people at one clinic saying it should continue. One figure was corrected, and the correction is the useful part: the discovery deck's own slide is headed "Conducting Interviews (12 users)" and this site has always said nineteen. Both are true and neither said what it was counting. Nineteen is sessions, twelve is people, a teenager interviewed twice is one person and two interviews, and the canon now carries the pair and records that the breakdown behind the nineteen survives only in this portfolio's own earlier text, which makes it the weakest figure here. Two small things were caught by the suites on the way, both from the same mistake: copying one page's navigator over all of them deleted the landing page's only h1, which lives in the navigator's name block and nowhere else, and stripped the data-pane hooks that drive its preview panes. The accessibility suite found the first within a minute. The label-overlap suite was pointed at the new drawings and failed one of them on its first run, a question running through a station number, which is the whole argument for generating thirteen plates from one script and then measuring all twenty-six. The fix was to stop copying and insert three rows into the navigator each page already had.

v6.2OCT 2026
The site's central claim is coherence, and its own information system was less rigorous than the design system it was describing.

The component library appeared as 216 on the landing screen, 216 three times on case file 001, 220 further down that same file, and 214 inside a product demo under the words "one source of truth". assets/figures.js is the answer: every figure in one place, each one carrying its definition, its date, and for anything countable from the repository the command that counts it, with a suite that fails the build if a page disagrees. The component count is 231 under a stated definition, the rule book runs to 91 rather than 93, and the token count was restated at 3,444 under a definition the page now prints, because the number this site had published for a year had no recorded derivation and the two could not be reconciled. The suite caught this entry stating the retired figure, which is the check doing its job on the page that introduced it. The governance behind the work arrived with it: the decision-authority matrix, eighteen classes of change resolved to one required approver each, and four decisions from the log with what each cost. Thirteen case-file diagrams were rebuilt from default flowcharts into the station idiom, and a new suite measures every label in every plate against every other, which found overlaps in seven of them.

v6.1OCT 2026
Every hero stood on its own ground.

The contour field under the token sphere on the landing screen could not be reused anywhere, because it was built inside that object, sampled from the object's own noise at the object's own frequency, and could not exist without it. assets/terrain.js lifts it out as a standalone ground with its own frequency per page, so the case files, the CV and the colophon each stand on terrain drawn from their own content rather than on blank paper.

v6.0OCT 2026
One coherent dialect turned out not to be the same thing as a point of view.

The clear-out in v5.1 left a site that measured perfectly and photographed like a tax form: cream, ink, grey wireframe and one electric blue, every value within about fifteen points of every other, so there was no figure, no ground, and nothing for an eye to land on first. Four moves fixed it, and all four are applied to what was already here rather than added beside it. Value: .invert re-points the surface tokens for a whole block, so every component inside comes out light on dark without knowing it moved, and the landing hero is one. The accent is heat now, because vermilion is a pigment colour that makes the cream read as a decision instead of as off-white, and because nobody picks #2c3bee, it is what you get when you do not pick. Crop: the hero left .overview, which capped it at 1120px and padded it, leaving a strip of empty desk beside the loudest thing on the site; it is a full-width band and the form is cut by the right edge, because an object that ends inside its box has been placed and an object the frame cuts has been composed. The four case files got the same treatment, and their diagrams now run off the sheet. Overlap: the headline sits on the drawing. Grain: one fixed turbulence tile over everything, stepped rather than tweened, and it is doing more for how this site feels than any other forty lines in the project. Typographically, Archivo went and Bricolage Grotesque arrived, subset to 124KB with weight, width and optical size all live. The hero also stopped being uppercase: capitals flatten every letter to the same rectangle, and everything that makes this face worth having over any other heavy grotesque lives in the lowercase. Motion became one law rather than a pile of transitions, Lenis driving the page, with the display type reading its velocity and narrowing into the movement. The four case tiles became seven files on a track you push, with momentum, running off both edges. About was rebuilt as an observation panel, because nobody reads nine hundred words about a stranger; everything in it is rendered one bit through an ordered dither, so a photograph and a generated cloud arrive as the same material. Three things worth recording. A hover rule was lifting seven objects two pixels and giving each a drop shadow, six of which had just had their cards removed on purpose, so it was quietly putting them back. A new contrast suite reported a perfectly legible cream caption at 1.26:1, because color-mix() returns color(srgb ...) normalised nought to one and the parser was reading it as nought to 255; the parser was wrong, not the caption. And rebuilding About deleted the page\'s only h1 along with the old header, which the accessibility suite caught; the heading is the subject\'s name on the identification label, which is what it should have been marked up as all along.

v5.1OCT 2026
The site was speaking three languages at once, and the loudest one was not actually audible.

An audit across every page found the display voice silently overridden everywhere it was used: .bigtype is a bare class at (0,1,0), and .pane h2 and .cvhead .id h1 outrank it, so the one shouting element of the whole art direction was rendering at 24px on the landing screen, 40px on About and the colophon, and 40px on the CV. It only looked as though it worked because text-transform is not part of the font shorthand that was beating it. Fixed by listing the selectors rather than reaching for !important, so the next rule that outranks them is findable: the headline is 118px now, which is the size it was always meant to be. The rest was a clear-out of an earlier dialect. Instrument Serif is gone, the fourth family that only ever set italics, and with it two font files; emphasis carries weight instead. The hand-drawn pen layer is gone: six circles and underlines from rough-notation, 10.8KB of vendored library, sitting a couple of hundred pixels above a set of precision leader lines and making two incompatible claims about what kind of object this page is. The leader lines point better, and they were always the evolved version of the same idea. The margin notes stay, because what they say is the most honest writing on the site, but they have stopped dressing as handwriting: no italic serif, no one-and-a-half-degree tilt, no drawn arrow. They are annotations now, in the same mono everything else is labelled in, squared to the grid. Also retired: a frosted translucent pill floating over the drawing, and a 99px pill in the topbar of all eight pages that the earlier de-pilling pass missed because JavaScript injects it. One thing broke on the way and is worth recording: stripping the pen's attributes left bare <span> wrappers whose only purpose had been to give the pen something to measure, and inside the summary band a bare span inherits display:block, so "3,444" dropped onto a line of its own on four case files.

v5.0OCT 2026
The navigator was open on every page whether you wanted a file list or not, and hovering it rewrote the view.

Two things, and the second was the worse one: moving the pointer across the file list swapped the whole open pane, so the view changed without anyone asking for it. That is a preview masquerading as navigation, and it is now a click, which is what the code comment beside it had claimed all along. The panel itself starts collapsed and gives its 276px back to the open file, which the drawing on the landing screen notices: the toggle sits at the left of the topbar, the command palette and / both open it, and the choice is remembered per browser behind a try/catch. Collapsing uses visibility rather than display so the panel leaves the tab order and the accessibility tree on every browser this site supports, where inert does not exist until well past the floor; and it only collapses above 920px, because below it the shell is already one column and that panel is carrying the name and the bio at the top of the page. Two measurements worth keeping. A zero-width column still measured one pixel wide, which was its own right border. And the tile suite called a working anchor broken: it probed a fixed thirty pixels down from each tile, and once the tiles got wider that point landed underneath the sticky breadcrumb bar, so the browser answered "the header". A real click proved the anchor was fine, so the probe now scrolls each tile into view and stays below the chrome.

v4.9OCT 2026
The drawings were objects parked in a document, which is what an afterthought looks like.

An audit across the site said so plainly: one page had a display headline and the rest had ordinary ones, the CV had no part of the language on it at all, and a folio rail had been written into the stylesheet and used precisely nowhere. What the reference drawings actually have is not better pictures, it is a frame that is always there, so every part of the page reads as sitting on one measured surface. So the site got a chassis. A scale runs down the right edge of every open file, and its ticks are the document's own sections placed where they really fall, with the one you are inside marked and a cursor at the reading position: it is an indicator rather than a control, because the section nav already navigates and a second set of 34px targets would be a worse one. Registration marks sit at the corners of the sheet. Forty-four sections now close on a folio rail that names what comes next, so a section ends rather than stopping. The navigator's group headings take the bracket notation. About and this page took the display voice; the CV deliberately did not, because it is printed and read by an applicant tracking system, and a name set in 100px caps is a poster rather than a document. And the hero object now stands in ground rather than in void: the contour lines behind it are not a texture picked to go with it, they are the same noise function at the same frequency from the same seed, sampled on the z = 0 plane instead of on the sphere, which is one field drawn twice. Contours come from d3-contour, marching squares done properly including the saddle points, which added 5.4KB to the vendored bundle. Two faults worth keeping: the scale was first positioned absolutely inside the scrolling box, so it was laid out against the scroll content, stood as tall as the whole document and scrolled away with it, which is an instrument frame that leaves the frame; and the reading cursor was drawn in the hot vermilion, which would have put a second hot mark on every page in the site and broken rule eight everywhere at once, so it wears the chrome accent the status bar's reading bar already used.

v4.8OCT 2026
A flat lattice is a diagram, and a diagram is not an image.

The plates were correct and they had no presence: hairlines on paper, every value the same value, nothing with a near side and a far side. So the two pages that carry the most weight got an object instead. It is built from the same counts: 3,444 points on the landing screen, one for every token in the system, and 216 on case file 001, one for every component in the library. Each point is joined to its neighbours, which on this kind of lattice are not the points either side of it in the array. Measured over 3,444 points, step one is a chord 1.46 long reaching right across the form, while steps 34, 55 and 89 come out at 0.074, 0.064 and 0.077 against an ideal spacing of 0.060: those are the neighbours, and joining them is what turns a cloud into a surface whose curve you can read. The steps are derived from the count rather than typed, so the 216-point form picks 8, 13 and 21 on its own, and the same follows for the edge length past which an edge is a pole artefact rather than a neighbour. Depth does the shading: the far side of the form is paler because it is further away, which is the tonal range the flat plate never had. It resolves once on opening and then holds, because house rule three says motion only when a hand causes it, and after that the only thing that moves it is the pointer. Built on ogl, a minimal WebGL library, tree-shaken to the six classes this needs: 48KB, 14KB over the wire, vendored with everything else, still no third-party request. Two faults found in the building. ogl writes width and height onto the canvas as inline pixels, which beats any width:100% a stylesheet has, so a canvas measured against itself reports whatever it was last told and the first measurement, taken at the 300x150 default, pinned it there; the box is a wrapper the stylesheet owns now. And two of this site\'s own suites were passing without looking: the arrow check read a class an IntersectionObserver sets, synchronously, in the same pass that scrolled the note into view, which worked only while the note sat high on the page; and the hot-mark check counted canvas.plate, so the moment the landing page stopped having one it reported zero marks and called that a pass. Both now measure the thing they claim to.

v4.7OCT 2026
The drawings had to stop being decoration and start being the measurement.

What makes a technical plate hold your eye is not the leader lines, it is that the picture is the number: you can count it. So each case file now carries one, built from the counts that file already states, and no two are alike because no two counts are. 001 draws 93 numbered slots, 91 holding a live rule and two left as open squares, because the rule book retired two and never reissued their numbers [Corrected in v6.2: the rule book runs to 91, not 93, and the two retired are rules 10 and 70, superseded by rules 82 to 84. The drawing shows 91 slots with 89 live now. This entry is left standing because it records what shipped at the time, which is the same reason the rule book keeps a retired rule’s body in the corpus.], and the sequence carries its own history. 002 draws 29 people in two blocks, 9 and 20, with nothing joining them, and the one marked cell is the designer who was counted in both. 003 draws 92 people in three blocks sized 19, 70 and 3: the interviews, the surveys, and the three workshops, which are the smallest block and the one that moved the design. 004 draws a single row of fifteen, one booking, with one person marked, the one who answers for all four households when the total moves. Four principles came out of the reference work and all four are enforceable: scale is huge or tiny with nothing in between; lines connect rather than divide, so the leaders point at things instead of fencing them; density is contrast, so a plate caps its lattice pitch and a small count becomes a small tight object with void around it rather than four dots stretched over a thousand pixels; and nothing decorative may look like data, so the inked cells that give a 216-node plate its tone are switched off below 48 nodes, where two black squares would read as a distinction the booking has not got. Two routing faults turned up on the way: a leader to a label sitting below the drawing was still being routed sideways, straight through the words it came from, so it leaves vertically now and takes its sideways run late, across the empty paper; and anchor coordinates were being measured against the whole figure rather than the plate, which put three of the five anchors outside their own lattice, so they are measured against the plate now and the three were recomputed from the layout rather than re-eyeballed.

v4.6OCT 2026
The site was a well-behaved template, and behaving is not the same as being looked at.

Every value on it was derived: each figure came from a token, each component was the same component, and nothing was ever placed. That is what makes a system good and exactly what makes a page feel machine-made. So the chrome became a technical drawing. The landing screen is now a plate: 216 points, one for each component in the library, scattered across the sheet and resolving into a lattice once, on open, which is the job the whole site is evidence for. Square anchors sit on the drawing and orthogonal leader lines run out to the claims, each ending at a case file. The lattice is cut around the headline and around every label, the way a drawing stops its line work at the title block rather than running under it, measured from the live type so it follows a rewrap instead of being coordinates somebody typed. The forty-four numbered sections across the case files, About and this page now carry their number as plate furniture: the numeral, its rule, and the caption set right. The two cities the role is in keep live time in the breadcrumb row. And the bio moved into a titled window, which is the one box added back on purpose: the border is the thing being drawn, so the boxing budget now admits it by name and says why. Three findings came out of building it, all mine: a label pinned to the drawing's right edge was laid out from the left and collapsed from 196px to 40px; the lattice took the smaller of its two pitches and linked every column and no row, so the first plate was six ruled lines; and the vermilion measured 4.03:1 on cream, which is fine for a mark and fails for the 9.5px word set in it, so it split into a mark value and a text value and the contrast suite now reads both on all eight skins.

v4.5OCT 2026
This page said the rules were checkable, so they get checked.

Rule one named "Astrato violet" and "Villa indigo": the palettes v4.0 replaced with crimson and terracotta, which the v4.0 entry three paragraphs below says correctly. The one page whose whole premise is that the site does not contradict itself, contradicting itself. The rule quotes the four hex values now, and a suite reads --accent off each case file and compares, along with the other rules it can reach: that nothing on any page animates unprompted, that spacing really is 24 and 12, and that switching theme changes no markup on a component. Every product screen was driven too, looking for the thing this site was first accused of: a page that leads nowhere. There isn't one.

v4.4OCT 2026
On a phone this landing screen had no hero.

The pane system is a pointer affordance, so below 920px it was switched off, and the headline, the lede, the proof line, the buttons and the artifact shelf went with it: a visitor arriving from a link got a name, one line of bio, and then case cards. Every phone and every portrait tablet, which is most first visits. The pane system still goes; the hero inside it stays. The four case cards used to embed an artifact page at phone width, so what you saw was that document's own topbar, cut off, above the top of a headline belonging to something else. They run the product now, scaled whole, the way the desktop tiles do, and lazily: four artifact sites used to load eagerly on a phone and now none do. The topbar had the same hidden-scrollbar defect as the section nav, cutting "Colophon" to "C" with nothing to say the rest was there; on a phone the navigator rows are hidden too, which makes it the only navigation on the page, so it takes a second row rather than losing anything. Measured after: about 200ms to load, thirteen requests, 297KB, and the four frames that used to load whether you scrolled to them or not now wait until you do.

v4.3OCT 2026
The keyboard controls this page has advertised since v3.2 did not work, and were in the way of everything else.

The navigator's handler was bound to the document with no scope, so it owned Enter for the whole site: whatever you had focused, pressing Enter navigated to the current file. Tab to "Copy email", press Enter, and you arrived at case file 001. A keyboard-only visitor could not operate this site at all. Enter now belongs to whatever has focus, and the single-character shortcuts (j, k, t, /) only fire when no control does, which is what a character-key shortcut is supposed to do. The rest of the pass: a skip link, because the shell repeats a topbar and sixteen navigator rows before the content of every page and tabbing through them was the only way in; a focus ring on the file filter, which had outline:none and nothing in its place; heading levels that went h2 to h5 in three case files; a section nav that scrolled sideways with its scrollbar hidden, so at 200% zoom its last items were invisible and unreachable; and the wordmark, breadcrumbs, role links and CV evidence links, all under the 24px minimum on a phone. Found by measuring rather than by claiming, and there is a suite for each of them now.

v4.2OCT 2026
A hand on the page.

Everything else here is a system: nothing is placed, everything is derived, and that is exactly what made it read as a template. So there are now six marks and six margin notes. The marks are drawn by rough-notation, vendored like everything else, seeded from the text they circle so the wobble is identical on every visit rather than regenerated each load; a hand that redraws itself differently every time is a generator. The notes are in the serif, tilted a degree, and they say the things a case study will not: whose fault the Villa Plus booking was, which feature I had already built when the teenagers killed it, that the design system was never the hard part. They float, so they cannot collide with the prose; they are the first thing dropped when the column narrows and they are left out of print entirely. Also in this version: every em dash on the site is gone, and the role at the top is current.

v4.1OCT 2026
The landing screen shows the work instead of describing it.

Four case files, four products, and until now the front door argued for them in prose: a headline, a lede and four blocks of type. Each tile now runs its own product at thumbnail size: the real application, booted one after another so four of them starting at once never janks the page, scaled to 18% and taken out of the tab order because the heading beside it is what a screen reader should read. The sixteen delivered artifacts (the design-system site, the UX Files, the prototyping class, the three client decks) were reachable only from the third group of a navigator rail, below its fold; they have a shelf on the landing screen now. Which also means the overview finally scrolls, so something tells you more is there.

v4.0SEP 2026
An application you can drive.

⌘K opens a command palette over every page: all twenty-seven files, the sections of whatever file is open, and the actions the status bar advertises, fuzzy-matched so “vila” finds Villa Plus. The fifteen artifact pages, full deliverables that used to dissolve the workspace the moment you opened one, now carry its status bar, with the path and the way back to the case file that owns them. Navigating between files uses cross-document view transitions, so the chrome holds still and only the file changes. The status bar gained a reading position, the way an editor has one. Each case file's palette now comes from the deliverable it presents rather than from a hue picked nearby: Astrato is the deck's crimson, Villa Plus its cream and terracotta, Safe Space NHS blue on warm paper. All of it measured for AA in both themes, which turned up one failing value in a skin nobody had touched. And the landing screen, which was 45% empty and did not scroll, now opens with the four case files.

v3.9AUG 2026
The workspace wears the product.

Opening a case file now re-skins the entire application in that product's palette (surfaces, ink, accent and headline character), so the chrome around the embedded app belongs to the same world as the app; the OI·DS file in dark mode is near-black and teal because the portal is. Each product grew into a real one: working screens behind every navigation item, not one screen with decoration. Every case file gained an end-to-end flow map and a table of what was broken, what changed and what it moved. Real iconography throughout: 98 Lucide icons and 18 Simple Icons brand marks, vendored so nothing is fetched at runtime.

v3.8AUG 2026
The products moved in.

Every case file now runs the software it describes: the Safe Space clinician dashboard, the Astrato workbook builder, the Villa Plus group booking engine and the OI·DS portal, rebuilt as four self-contained applications under /products and embedded in their files. Each keeps its own brand behind an iframe boundary, boots when it scrolls into view, expands to fill the window, and opens at its own URL. The navigator gained a Live products group; the reading stopped being the only thing to do here.

v3.7AUG 2026
Denser, and four colours braver.

The whole interface tightened: smaller chrome, tighter type, half the whitespace. Each case file now carries its own accent: OI teal, Astrato violet, NHS blue, Villa amber, painted across a tinted header band so no two files look alike. Ledes cut to a sentence. Still one accent per view; there are just more views.

v3.6AUG 2026
The page answers the hand.

The overview now opens with a statement instead of a list; every document got an eyebrow. Sections reveal as the reader reaches them, cards lift under the cursor, and the status bar tracks the section being read. Motion still only happens when a hand causes it; the hand just has more to cause.

v3.5AUG 2026
Scenes, not essays.

Every case file now opens with its story in three beats (problem, move, proof), and every section leads with a claim headline and a visual: a diagram, a working demo, a number said loudly. The prose that survived is a caption; the prose that duplicated a visual is gone. Recruiters read headlines; now the headlines carry the story.

v3.4AUG 2026
The palette woke up.

Cream paper, ink and one electric blue under wide Archivo display type; dark mode became the alternate instead of the default. The components never changed; the whole restyle was a token swap, which was the point of having tokens.

v3.3AUG 2026
One application.

The navigator, search and keyboard controls now persist on every page; documents open inside the workspace in their own pane, under a view header, above a status bar. Earlier versions kept the app shell on the homepage and dropped you onto ordinary web pages the moment you clicked. That is the exact seam this version removes.

v3.2AUG 2026
Everything moved in.

The design system story, its presentations, the component library, the UX Files deck, the class and all three case-study sites are now served from this domain under /artifacts and embedded live in the case files. No screenshots of the work remain anywhere on this site.

v3.1AUG 2026
The work went live.

Each case file now carries a working rebuild of its signature mechanic: drag the dashboard split, flip the join canvas, change a booking and watch the price explain itself, log a week and choose what a clinician sees. Labelled as rebuilds; the genuine captures stay where authenticity is the point. A printable CV joined the nav.

v3AUG 2026
Rebuilt as a product.

Case files with the research attached, working search, keyboard navigation, light and dark. The previous version kept being read as template work, and the honest fix was to show the work rather than decorate it.

v2JUL 2026
The scrolly rebuild.

One long page, device mockups, a command palette. Shipped, learned from, retired.

v1THE WEBFLOW ERA

Still exists, as a keepsake.

07Accessibility

Built to WCAG 2.1 AA, and what that does not yet prove

The standard. This site and everything running inside it, the five products, the three phone apps and the notes system before COVID, are built to the Web Content Accessibility Guidelines 2.1 at level AA. Its status, in the W3C's own wording, is partially conformant: the checks below pass, but some content does not fully conform, and the checks are not the whole standard.

How it is assessed. By me, against the build, before every release: nothing ships with a check failing. Since v7.40 both axe-core suites also run on every pull request. The first run of the two axe-core suites, on 18 October 2026, failed 28 of the 36 product screens and 43 of the 54 page views. Each failure was fixed rather than waived, except the one figure named under the limits below.

What is checked before every release, and its last result
CheckWhat it coversLast run
axe-core 4.14, WCAG 2.1 A and AA rulesEvery page, at desk in the light setting and on a phone in the dark, the five case decks included: 33 pages, 66 viewsAll pass
axe-core, the same rulesThe five products, the three phone apps and the old notes system, at desk and phone in both settings, 36 views; and the 49 states the case files link into, 98 viewsAll pass
Keyboard and structureA skip link on every page with a navigator, shortcuts that never fire inside a control, a visible focus ring, headings in order, nothing lost at 200% zoom, targets of at least 24 px on a phonePass
ContrastEvery case file's skin, in both settings, at 4.5:1 for textPass
Forced coloursWindows contrast themes: every boundary and state still drawnPass
Reflow and text sizeNo sideways scroll at 320 px, and no text under 11 px on a phone, on every page except the three rebuilt decksPass
Reduced motionWith reduced motion set, every drawing arrives whole and stillPass
ChartsEvery chart in the products: its marks at 3:1 against the card, or every mark’s value in printPass
Touch targetsEvery control in the three phone apps at least 44 by 44 pixelsPass
RecordingsEvery recording plays only when pressed, with captions on by default and a transcript in the same words, since a silent screen recording needs its text alternativePass
Without scriptsThe case files and pages still read with JavaScript off, the three rebuilt decks aside; the products need itPass

What has not been done. No one has used this site with a screen reader (VoiceOver, NVDA or JAWS), by voice control or by switch access, and it has had no external audit and no sessions with disabled users. Automated rules find only part of what WCAG asks. The checks run in Chromium, the engine of Chrome and Edge; Safari and Firefox are not under test.

Known limits.

  • The before half of the before and after page in case file 001's deck draws the old interface's faults on purpose, low-contrast text among them. It carries a text description, and it is left out of the contrast audit by name.
  • The drawings answer a pointer or a finger, not a keyboard. What each one shows is also in its caption and its text description.
  • The Storybook under case file 001 is the repository's own build and is not graded here.

Built with HTML, CSS, JavaScript and WAI-ARIA.

If something here does not work for you, send a message on LinkedIn and say which page; it will be fixed or answered. This statement was written on 18 October 2026 and last revised for v7.43, on 20 October 2026, the day the checks last ran.

08Privacy

The CV counts its readers, and nothing else here does

What is counted. Only on the CV, at withcontexts.com/cv: that it was opened; which of its sections were read, a section counting as read once half of it, or half the screen, has been in view for three seconds; which section a followed link sat in and what kind of place it led to, such as a case file or LinkedIn; and whether the CV was downloaded, printed, copied as text or saved as a contact. Each is counted once a visit. No other page counts anything.

How. With Vercel Web Analytics, run by Vercel, the company that already hosts and serves every page here, from this domain. It sets no cookie and keeps nothing on your device. Vercel recognises a visit by a hash it makes from the request and resets every day, so a visit cannot be followed from one day to the next or from this site to another. With each count it receives the page address, the site you came from, and your country, browser, operating system and kind of device. What I see is totals in Vercel’s dashboard, never a person. Vercel’s own account of it.

Why there is no consent banner. UK law on storage and access technologies, as the Data (Use and Access) Act 2025 amended it, lets a site measure how it is used, only to improve it, without asking first, as long as it explains the measuring clearly and gives an easy way to object. This section is the explanation, and the button below is the way to object. The legal basis for the little personal data involved is a legitimate interest: knowing whether the CV is read, and which parts.

Not counted at all is anyone whose browser sends Global Privacy Control or Do Not Track, and anyone who presses the button: the page then never asks for the counting script. That choice is kept in your browser, as one setting named ctx.nocount, so it holds next time; it identifies no one. Press the button again to be counted again.

With scripts off, nothing is counted.

Questions, or a request about what was counted, go to me on LinkedIn. This site is mine, Shad Abbaslou’s, and Vercel processes the counts on its behalf. This statement was written on 20 October 2026, for v7.44.

09Known issues

Honest about the edges

Ten packages inside the perimeter, three CDNs outside it, every wire cut. Hold a package for its version and licence.
  • Every page now makes zero external requests, artifacts included. The ten packages the artifact sites animate and chart with are vendored under /assets/vendor with their licences and their versions written down; the typefaces are self-hosted. Nothing here phones a CDN.
  • The CV's dates are tenures ("3+ years", "a year") rather than month and year ranges, and there is no line saying where he holds the right to work. Both are deliberate omissions until the real facts are confirmed; nothing on that page is estimated.
  • This page will drift out of date the moment I ship something new.

Source notes

  • Token names and values are copied from /assets/site.css, the same stylesheet this page loads.
  • The rule-book figures, 91 numbered slots with 89 live and two retired, are from case file 001, the OI design system. Rule numbers running to 91 is the one part of that checkable here: it is the highest rule number cited anywhere in the DS-Brain corpus.
  • Changelog months are when each version of this site shipped.