` (4px inset edge in `--brand`), preceded by its label in the label column; `--callout-bg`, 1.15rem text, no border. ### 7.10 Framed registers and tables Table: `

[...]...

...
...

`. The wrapper scrolls horizontally and is focusable; `th` is the label voice with the only hairline in the design beneath it; `.sticky` keeps the header row at the top of its scroll box while the reader scrolls the table inside it, in a wrapper bounded to 75 % of the viewport height (section 7.31; in 1.4.1 and earlier the header stuck only to an unbounded wrapper, so it scrolled away with the page, contrary to this section's wording until 1.5); `td.id` and `.mono` are JetBrains Mono; `td.num` right-aligned; `td .sub` a muted second line; `.tag`, `.tag.accent`, `.tag.fill` are pill tags. Cells use `overflow-wrap: break-word` (on `td` and on `code` inside cells; `td.id code` stays on 1 line): in an auto-layout table a column keeps its typical width and the table scrolls inside its wrapper on narrow screens instead of crushing its columns, and in a fixed-layout table a long token wraps inside its own cell. `table.fixed` uses fixed layout with `colgroup` widths and a minimum width of 56rem, so 1 long cell cannot widen a column; its headers may wrap. (The mockups use `overflow-wrap: anywhere`, which crushes an auto-layout table's columns at 390 px; baseline 1.0.0 corrects it.) From 1.7.0 a `table.fixed` may size its columns in rem with `col.r6` to `col.r24` in place of the percentages, so that a wide table grows past the page and scrolls inside its wrapper; `td.nowrap` keeps a cell on 1 line; `td.na` marks an empty cell (section 7.34). A commit hash is written as `7 characters`. On paper every table prints whole, in both directions, and fits the page width (from 1.8.0; section 7.34, Print). Framed register (aiqt.ai): `

Register 1Title17 rows

+ table

`: a 1px frame with a caption strip (`--surface-sunken`, 4px `--brand` edge, count in JetBrains Mono at the right). Figures (reference pages): `

17frameworks

...

`, Newsreader 300 3rem numbers over a 3px `--brand` rule. ### 7.11 Code and prompt blocks with copy Markup: `

text

`. Two variants for a long text: `class="prompt-block"` with `tabindex="0"` caps the block at 36rem and scrolls inside it, for a prompt the reader copies rather than reads (the page keeps its shape); `class="prompt-flow"` (from 1.1.0) shows the whole text in the page flow with no cap and no inner scroll, for a portable text the reader reads in place, such as cleanlanguage.ai's instructions page. Both keep the same `pre id`, copy button and status contract. JetBrains Mono 0.95rem on `--code-bg`, wrapping (`pre-wrap`, `overflow-wrap: anywhere`); the full text is always in the page. `copy.js` reveals the button when the Clipboard API exists, copies the text without the button's label, shows "Copied" for 3 s and writes to `#copy-status`; without script the button stays hidden and the text is selectable. Inline `code` uses the same face at 0.9em. The download block (`.download`: file link `p.file`, `.lbl.size`, `code.sum` checksum, optionally a `pre` or a plain `p`) belongs with it. From 1.13.0 (D-097) the last element of a download block in a document ends flush with the block, so the space under the block is `--download-after` (default 1.6rem, 25.6 px) whatever that element is. Until 1.12.4 the 2 margins added up in the document grid: 43.2 px under a file line or a paragraph, 40 px under a size line or checksum. The last line ends flush only when it is the block's last element: a block whose last element is hidden keeps the margin of its visible last line, so its gap stays as in 1.12.4. The space under the file line, where more lines follow it, is `--download-line-gap`: its default and its ceiling are the paragraph gap in effect (`--para-gap`, 1.1rem unless the site lowers it), and its floor is 0; it merges with the size line's 0.3rem top margin. It applies wherever the paragraph rule sets the file line's margin, at any depth of a document: a block at the grid's level, in a `section` or `article` at any depth, or in a `details`. Inside a callout, a pair or another box that sets its own paragraph margin the file line keeps that margin, and the token has no effect there. Outside a document neither the token nor the flush last line applies. A site may lower either token in its `site.css`; `baseline.css` clamps each between 0 and its default with `max(0px, min())`, so a larger value has no effect and a negative value gives 0. For example, `.site-vendorreplies { --download-after: 1.1rem; }` makes the space under a file-only block 17.6 px. Setting it to `0px` makes the next block touch the file line. Each token takes a length, such as `0px`. A unitless number (a bare `0` included) or any other value that is not a length makes each margin declaration that reads the token invalid at computed-value time, so every margin that declaration sets takes its initial value, 0, in place of the clamped value: with `--para-gap`, the whole margin of each paragraph, list, definition list, quotation, grid-level `details` block and file line whose margin the token's rules set (their top and side margins are 0 already, so the bottom margin falls to 0); with `--download-line-gap`, the whole margin of the file line followed by more lines, where the paragraph rule sets it; with `--download-after`, the block's bottom margin only, because the block's 0.4rem top margin is a separate declaration and stays. Where a box's own paragraph rule sets the margin, the token is not read and nothing changes. Nothing grows. Measured on 2026-11-12 (Chromium 153.0.8010.12) with `0`, `2` and `foo` against `0px`: the same computed margins on every side, and `CSS.supports` rejects each of these declarations with the value substituted and accepts it with `0px`. ### 7.12 Selector (install pages) Markup: `

Claude

` followed by 1 `

` per assistant, each with its `h2`, a `

Last verified: ...

` line and its steps (`

` and `#` on load and on later hash changes. ### 7.13 Index lists Markup: `

Titlecount or type1 line

`: 2 columns (3 with `.three`, 1 with `.one`; 2 at 1000 px and below, 1 at 600 px and below), serif titles with a monospace figure at the right, an optional description line. Used for guide indexes, domains, types and the search results; `.chips` is the row of filter pills on the search page, and `.search` the form (`

` with a labelled `input type="search"` and a `data-search-status` line) that `search.js` filters by `data-search` text on each `li`. From 1.5.0 the list (`data-search-scope`) can run in results mode, show nothing until the reader types, and be filtered by chip groups (facets); section 7.29 gives the contract. Without script every row shows. ### 7.14 Scope paragraph Markup: `

Scope

...

` near the top of an inner page: the fuller statement of what the project covers and does not do, moved from the landing page's former lists; plain prose, no list. Present on secureconfig.ai (checklist, guides), opfiles.ai (standard), auditthis.ai (method), cleanlanguage.ai (standard, install), aiqt.ai (install) and grclibrary.ai (browse). ### 7.15 Next block Markup: `

[

1 line

]Text

`, closing every inner page above a 3px `--brand` rule; the licence page's Next leads home and, where the project has a public repository, names it. ### 7.16 Licence page Path `/license/` (`license/index.html`), heading "Licence" in the label and "Licence" as the navigation item; `h1` is the licence's name. Content, in order: the scope sentence with links to the licence file in the repository (where the project has a public repository) and the canonical licence text; "Parts under a different licence" where applicable; "What you may do", a complete plain-language summary of the licence's conditions and limits with the clause numbers read from the licence text and the sentence "The licence text governs; this is a summary, not legal advice."; the owner's note in a callout ("Jeff Posluns prefers to publish openly and releases each project under the licence that best fits it: open source licences for software, and public domain or Creative Commons licences for documentation and content."); the Next block. No file named `license.html` may exist beside the folder (it would shadow the folder on Cloudflare Pages). ### 7.17 404 page The document grid with the label "404", `h1` "That page is not here.", a lead sentence naming what the top bar links to, the logo-only rail and a Next block to the home page. The header and footer are the same as every page. ### 7.18 Before and after, diagrams, records Kept from the mockups where a site uses them: `.pair` (2 columns from 1001 px, `.before` on `--pair-before-bg`, `.after` on `--pair-after-bg`; from 1.11.0 `.pair-stack` keeps the 2 boxes one above the other at every width, each as tall as its content, `

` frames quoted text on the inner panel `--pair-panel-bg` in the page's text face, a code block in a box takes the same panel, a stacked before box holding a `.msg` takes the after box's surface, and on a tinted band a before box takes `--pair-before-bg-on-tint`); `.figure` with an inline SVG `.wide` and a `.stack` variant shown at 600 px and below, with a `figcaption`; `dl.record` (tracked `dt`, serif `dd`; `.cols` for a grid of pairs); `.srcview` (source beside view from 1001 px). ### 7.19 Footer Markup: ``. Behaviour: the bar is 1 flex row of tiles with no gaps, rounded corners (0.5rem) and the exact width of the content (the footer is `.wrap`, so its edges are the page gutter). Each tile carries a 0.4rem band at its top (0.55rem until 1.11.0): the project cards use `palettes.css`'s `.slice-N` gradients (card N's own hue, joined to its neighbours by the shared join colours), with the first card starting and the last card ending on its own hue; the 6 cards start with the current site and continue round the cycle, so the purple-to-red join falls mid-bar on 5 sites; the current site's card has `aria-current="page"`, a visually hidden "(this site)" and a 3 px gold line under the whole tile at every width (from 1.11.1; until 1.11.0 a 2 px line under the name while the names showed); the other 5 link to their sites in a new tab. The GitHub tile's band fades from the last card's hue (`--tail-from`, set per site) to `--band-grey` over its first 20 %; the LinkedIn, ORCID and signature tiles are solid grey. From 1.11.1 project logos are 1.9rem in 2.75rem tiles (2.75rem in 3.4rem until 1.11.0), names 0.85rem and the signature 1.25rem; the 3 marks are 1.5rem (2rem until 1.11.0) with `object-fit: contain`, unaltered, on the common tile surface, and visibly smaller than every project logo; GitHub's black Invertocat shows in light mode and its white one in dark mode (`img.only-light`, `img.only-dark`). Hover and the current cue are an inset gold line. Every target is at least 44 px tall; the bar is 50.4 px tall from 1.11.1. The seventh card (from 1.11.0): vendorreplies.ai's card, `li.slice.slice-vr`, comes after the 6 rotated cards on every site; on vendorreplies.ai the 6 cards keep their base order (SecureConfig first) and the seventh card is the current one. The last rainbow card's band ends on `--band-silver` (`:has(+ .slice-vr)`), the seventh card's band runs from silver through `--band-sheen` and `--band-silver-deep` back to silver, and the GitHub tile's band starts from silver; below 600 px it stays solid grey. A browser without `:has()` (before Chromium 105, Safari 15.4, Firefox 121) keeps the 1.10.0 colours with a plain silver seventh band. A site outside the footer (from 1.12.0, NodeKeeper, D-068) has no card in it, and no footer rule or markup changes for it in 1.12.0. On its own pages such a site shows the shared family footer as is (owner, 2026-11-08, attended, D-075): the 6 rainbow cards and vendorreplies.ai's, with the footer markup unchanged; as built, the 6 cards keep their base order (SecureConfig first), vendorreplies.ai's card is last and no card is marked current (no `aria-current`, no "(this site)"). Stages, by the footer's container width, from 1.11.1: above 1159 px (`(width > 1159px)`, the exact complement of the next stage, so that a fractional width falls in 1 stage) the names show (they need 1157 px with the short signature); GitHub, LinkedIn and ORCID sit together beside the signature at 1.35rem, 4.8 px apart, under 1 band that fades from silver (from `--tail-from` on a bar without the seventh card) to grey; the signature drops "A" and "Project" below 1240 px. At 1159 px and below (1.11.0: below 1500 px, with 7 names needing 1493 px at the 1.11.0 sizes) the names are visually hidden (still the accessible names), the 10 tiles share the width left by the signature 7 to 3 (until 1.10.0: full size from 1400 px, names at scaled sizes from 1040 to 1399 px, logos only below 1040 px with 9 tiles) and each logo fills its tile up to 2.75rem; the signature scales between 750 and 650 px, loses "A" and "Project" below 650 px and scales again below 450 px; below 600 px the project cards take the whole first line and the 3 marks and the signature form a second line under a solid grey band, logos and marks back at full size. Measured for 1.11.1 on all 7 sites from 660 to 2000 px in both schemes: no overflow and no clipped name; names from a 1233 px window (a 1280 px window with a 17 px scroll bar gives 1187 px); "A" and "Project" from a 1320 px window; in the logos-only stage the 10 tiles equal (91.3 px each at a 1200 px window); every footer link at least 44 px tall and 24 px wide. Measured for 1.11.0: names from a 1588 px window; at 390 px 2 lines. Without container queries (`@supports not (container-type: inline-size)`) the bar and the cards wrap instead of overflowing. ### 7.20 Disclosure page Path `/disclosure/`, heading "Disclosure". Content, in order: an opening sentence stating that the page sets out what the project claims, the limit of each claim, and the evidence; the entries, each an `h2` topic with 3 paragraphs led by `Claim:`, `Limitation:` and `Evidence:` (the evidence paragraph holds the links), in the format of AIQT's `DISCLOSURE.md` and written from the site's own sources; a closing paragraph under the label "Security" with 2 links: "To report a security vulnerability, see the vulnerability disclosure policy." (`https://posluns.ca/security/`) and the universal privacy policy (`https://posluns.ca/privacy/`), both with the new-tab hint; the Next block. The rail lists the entries. From 1.6.0, before the Security paragraph, a paragraph under the label "Your browser" states what the light and dark switch stores: "If you use the light and dark switch, your choice is kept in your browser's local storage under the name scheme, so the site opens in that scheme next time. It is not sent to this site, and nothing is stored until you press the switch." (`reference/disclosure.html`). A site checks its own Disclosure claims against this: a page that says the site stores nothing in the browser is inaccurate from 1.6.0. ### 7.21 Channel list page A document page whose sections are the channels or contexts a standard adapts to (cleanlanguage.ai's `/channels/`): the kicker, `h1`, the rail listing every channel, a meta line, a callout naming the source file, then per channel a section label (`Channel N`), an `h2` with the channel's id and 1 list of its rules (`ul`), with a paragraph before or after the list where the source has one; the Next block. No new CSS: it uses the document grid, the rail, the callout and the document list styles. ### 7.22 Checklist page A document page whose sections are groups of questions (cleanlanguage.ai's `/checklist/`): the kicker, `h1`, the rail listing the groups, a meta line, a source callout, then per group a section label (`Section N`), a numbered clause heading (`h2.clause` with its number) and the questions as a numbered clause list (`ol.clauses`, items `N.1`, `N.2` and so on), so that a question can be cited by number; the Next block. No new CSS: it reuses the numbered clauses of section 7.8. ### 7.23 Demo page A page that shows the result and gives the reader a prompt to try (cleanlanguage.ai's `/demo/`): the kicker, `h1`, a rail of its 3 parts, a meta line; "Watch it work": 1 before-and-after pair (section 7.18) under a block label naming the pattern, and a link to the full set of examples; "Try it on your own writing": the explanatory paragraphs, the prompt in a copy block (`pre.hascopy` with `copy.js`; a `.code-note` line says what to do without JavaScript) and the fallback for an assistant that cannot browse; "Make it your default": the install link in the Next block. No new CSS. ### 7.24 About this project (landing page) Markup, directly after the value paragraph's region: `

About this project

Disclosure Licence Privacy (opens in a new tab) Security (opens in a new tab)

`. 1 line in the label voice (Public Sans 500 0.8rem, tracked uppercase, `--text-muted`), the 4 links separated by middle dots. From 1.7.0 there is 1 ordinary space after each dot span and none before it, so the line breaks only after a dot and a dot never starts a line. The dot's right padding is `calc(0.5rem - 0.36em)`: it gives up the space's width (4.59 px at the line's 12.8 px, the space and its 0.12em tracking in Public Sans), so the gaps either side of the dot are equal; measured from the link's last glyph to the dot and from the dot to the next link's first glyph, 8.00 and 7.98 px at 1280 and 390 px (8.00 and 12.59 px before the trim). On a page still on the older markup, with no space, the gap after each dot is about 3.4 px, so a site moves to the new markup. Until 1.6.1 the links and dots touched, so the line could not break: at 300 to 360 px the page was 379 px wide (reported from aiqt.ai and opfiles.ai, reproduced by the template owner). Measured on `reference/landing.html` 1.7.0 in Chromium 153 at 300, 320, 340, 360 and 390 px, light and dark: no horizontal overflow, 2 lines, no line starting with a dot, no link split across lines (10 of 10 cases; at 1280 px, 1 line). For pages still on the older markup, `.region .about` carries `overflow-wrap: anywhere`, which splits a word only when nothing else fits: measured with the 1.6.1 page on the 1.7.0 stylesheet, the page no longer overflows at any of those widths, but the line breaks inside a word at 320 to 360 px and a dot starts the 2nd line at 300 px, so a site moves to the new markup. The template's overflow checks include 320 px. It is the place that links the Disclosure and Licence pages (the value paragraph's own licence link may stay); the inner pages and the footer do not link them. ### 7.25 Inline accent Markup: `28` around a number or key term in running text, a table cell included. It sets `color: var(--accent)` and lining numerals, with no change of size, weight or face, so each site shows its own text-safe accent (4.5:1 or more on every surface, per `contrast-report.txt`). The colour is emphasis only: the sentence must read the same without it, so no meaning depends on colour (WCAG 2.2, success criterion 1.4.1). Use it sparingly: a count or a key term, never a whole sentence. `--brand` is never used for text (section 6). From 1.11.2 the warm variant: `28` sets `color: var(--ink-warm)` and lining numerals, exactly as `span.accent` does. `--ink-warm` is a component token (section 6.4) defaulting to `var(--accent)`, so until a site overrides it in its `site-palette.css` the warm span shows the site's accent and every page renders as before; `tools/check_palette.py` holds the token at 4.5:1 as text on the 5 surfaces, the 2 row tints, `--band-tint-bg`, `--pair-after-bg` and `--box-bg`, and blocks on failure. The same constraints apply: emphasis only, sparingly, a count or a key term, never a whole sentence, and no meaning on colour. Any value that passes the gate is lawful, with 1 exception: `--brand`, or its value, is never used for text (section 6), whether or not it would pass the gate (it also misses the 4.5:1 text floor on 6 of the 7 sites in light mode on these grounds). A palette's accent or a value chosen for text is the expected override. ### 7.26 Compact figures Markup: `

` with the usual `.fig` children (`.num`, `.cap`), up to 6. The figures share the text column's width equally on 1 line, with 2.2rem numerals and tighter caption tracking; at 900 px and below they set in rows of 3. The rule above each figure stays `--brand` and the numerals `--accent`. Use the standard `.figures` row for 2 to 4 figures that need the larger numerals. ### 7.27 Figure beside text Markup: `

...

`: 1 figure and a short paragraph side by side, the paragraph aligned with the figure's top; stacked at 600 px and below. For a total and its parts, the parts stated in the paragraph. ### 7.28 Brand marker Markup: `labelled and evidenced`. A band of the site's `--brand` behind the lower part of the line (38 % strength where the browser supports `color-mix()`, otherwise a thin solid band); the text keeps `--text` and the paragraph's type. Underlining is not used, because links are underlined. Emphasis only, sparingly, as for 7.25. The class is `marker`, never `brand`, which is the top bar's wordmark. ### 7.29 Search and facets Section 7.13 gives the form and the list; this section gives the options of `search.js` from 1.5.0, each opt-in by markup. They are a separate section because they add a contract of their own (attributes, address parameters, status wording), and 7.13 stays the index-list component. Reference pages: `search.html` (results mode with facets) and `facets.html` (default mode with facets). - **Default mode, unchanged from 1.4.1.** An empty query shows every row and leaves the status empty; a query shows the rows whose `data-search` text (or, without it, the row's text) holds every term, and the status reads "N of M documents match.". On a page without facets this wording stays. A page on 1.4.1 markup behaves as before: measured on grclibrary.ai's mockup search page (36 rows) for 12 queries, the hidden rows, the row order and the status text are identical under the 1.4.1 and 1.5.0 scripts. - **Results mode.** `data-search-mode="results"` on the scope: with an empty query and no active facet no row shows, and the status shows a prompt, `data-search-prompt` on the scope or "Type to search the documents."; a query, or an active facet, shows only the matching rows. - **Title ranking.** On in results mode, and in default mode with `data-search-rank="title"` on the scope: among the matching rows, those whose title holds every term come first, and each group keeps page order. The title is the row's `data-title`, or else the text of its first `a` without any `.vh` text. Clearing the query restores page order. Ranking moves rows within their own list only. - **Facets.** A chip group is any element with `data-filter-group=""` (lowercase letters, digits and hyphens; never `q`), usually `

"`; `data-filter=""` is the group's All chip. Each row carries `data-`, a space-separated list of values (for example `data-fw="iso27001 csf"`). 1 value per group is active; a second click on the active chip, or a click on All, clears the group. A row shows when every active facet's value is among its tokens and it matches the query. Values compare in lowercase. The chosen chip carries `aria-pressed="true"` and the others `"false"` (All is pressed when its group is clear). Because `aria-pressed` belongs to buttons, the script gives a link chip `role="button"` and makes the space key activate it, as a toggle; a modified click (a new tab or window) is left to the browser, so the link still works, and without script every chip is a plain link to a real page. Rows are hidden with the `hidden` attribute. On a page with facets the status reads "Showing N of M documents.". - **The address.** On load, `?q=` fills the input and `?=` sets a facet (a value with no chip in that group is ignored). As the reader types or clicks, the script writes the state back with `history.replaceState`, removing a parameter whose value is empty and keeping every other parameter and the hash; no history entry is added. This applies in both modes: in default mode it changes no row and no status for a given query, and a page on 1.4.1 markup had no use for a `q` parameter, so it is not opt-in. - **Without script** every row shows, every chip is a plain link and the input does nothing, as in 1.4.1. - **Chip lists start at the text edge (from 1.8.0).** `ul.chips` has no list indent, also inside `.doc`, whose lists are indented 1.2rem; until 1.7.0 a chip list in a document started about 19 px right of the text edge. - **Chips that would show nothing (from 1.7.0, grclibrary.ai's request, owner, 2026-11-04).** Opt-in per group, on the group's element: `data-filter-empty="disable"` and, optionally, `data-filter-count="live"`; any other value counts as absent, and a page with neither on any group runs as in 1.6.1 (measured: the DOM and the address after the same 7 actions are identical under the 1.6.1 and 1.7.0 scripts on `search.html` and on `facets.html` with the attributes removed, 32 of 32 snapshots). The served HTML is unchanged; only the script sets the new attributes. - *Would-show count.* Recomputed on load, on every input and on every chip choice: for each chip of an opted-in group, the rows that hold every query term, the chosen value of every other group and the chip's value (the chip's own group's choice is ignored, because choosing replaces it); for All, without this group's condition. A row with several values in a group counts toward each. At load the script prepares each row's lowercased text and group tokens once; each update is 1 pass over the rows, finding which conditions a row fails: none, and it counts toward its values in every group and every All; only 1 group's, and it counts toward that group's values and All; the query, or 2 or more groups, and it counts nowhere. The DOM changes only where a chip's state or count changes. - *Unavailable chip.* With `data-filter-empty="disable"`, a chip whose count is 0 takes `aria-disabled="true"` (never the `disabled` attribute), loses it when the count rises, and stays in the tab order. All is never unavailable, nor is a chosen chip, even when the result is empty, so a click can still clear it; the script never drops a choice by itself. Activating an unavailable chip (a click, Enter on a link, Space through the chip's key handler) changes no choice, row or address, and the status reads " would show no documents with the current choices." until the next change; focus stays on the chip. A modified or middle click is left to the browser, as in 1.6.1. Each unavailable chip points through `aria-describedby` to 1 note per page, ``, created by the script; the note carries `hidden` so that it is never read as page text on its own, while a description is still computed from it. There is no live announcement per chip; the result stays in the status, "Showing N of M documents.". - *Look.* `.chips [aria-disabled="true"]`: a dashed border in place of the solid one, `cursor: not-allowed`, and no hover change, with no fading and no transition. From 1.9.1 an available chip reads in `--chip-fg` (`--text`) with a `--chip-border` (`--text-muted`) border, and an unavailable chip in `--chip-unavailable-fg` (`--text-muted`) with a dashed `--chip-unavailable-border` (`--rule-strong`), and an unavailable chip is greyed out: its word struck through (the count, `display: inline-block`, is not), `--chip-unavailable-fg` (`--text-muted`) on `--chip-unavailable-bg` (light `--rule`, dark `--bg`) with a dashed `--chip-unavailable-border` (light `--rule`, so no visible border; dark `--rule-strong`). Until 1.9.0 both states read in `--text-muted` with a `--rule-strong` border. The 1px dashed border in `--rule-strong` measures at least 3.05:1 on the page background on all 6 sites, in the 6 states of section 6.1 (device light or dark; no `data-scheme`, `light` or `dark`), so no 2px border is needed. - *Live counts.* With `data-filter-count="live"`, each chip's `.n` text becomes its would-show count (an unavailable chip reads 0, a second cue in text); without it `.n` keeps its served count. A page whose text says the counts never change must say otherwise. - *Results mode.* Counts ignore the rule that no row shows until the reader types or picks a chip, so on an idle results page a chip is unavailable only when no row holds its value; ranking does not affect counts. - *The address.* Read and written as in 1.5.0; a refused value is never written. A link that opens on an empty combination keeps its values: the chosen chips stay selected and available, the list is empty, and the status reads "Showing 0 of M documents.". - Reference page: `facets.html`, whose Domain group is opted in, Type group opted in with live counts, and Framework group left as in 1.6.1. Measured in Chromium 153 (headless, Playwright): 51 checks, 0 failing, 0 console errors (the request's checks 1 to 5; 26 page states compared chip by chip against counts computed independently from the rows; results mode; the look; tab order). Not tested: screen readers (NVDA, JAWS, VoiceOver), the request's check 6. Speed on a page of 3,000 rows with 3 groups of 20 chips, all opted in with live counts, headless Chromium on the build machine, the median of 14 typed updates: 1.8 ms for the script and 7.6 ms with style and layout; with the CPU throttled 4 times through the DevTools protocol, 10.5 ms and 40.4 ms (the same page without the attributes: 12.5 ms and 36.7 ms). These are headless measurements, not a phone. ### 7.30 Matrix with presets Markup: presets as links (recommended, so that each leads to a page that resolves without script) or buttons, anywhere on the page, each with `data-preset=" ..."` (the column keys it shows) and `data-preset-id=""` (its name in the address); the All preset has `data-preset=""` and shows every column. `

` above the table. The table: `

......

...
Domain	NameOrganization
Row	`id`count documents

`. 1 matrix per page. `matrix.js` shows the chosen preset's columns and hides the others with the `hidden` attribute on their `th` and `td`; the row-header column carries no `data-col` and always shows. The status names the preset and the columns shown ("View: Security programmes. Showing 4 of 8 columns."). The chosen preset carries `aria-pressed="true"` when it is a button (the others `"false"`) and `aria-current="true"` when it is a link (the others none): a preset choice is a choice of view among links, so a link keeps its link role and is marked as the current item of its set, as the install selector does (section 7.12); `aria-pressed` is not valid on a link. `?view=` chooses a preset on load (an unknown id is ignored, and the All preset is chosen); a choice is written back with `history.replaceState`, and All removes the parameter. A modified click is left to the browser. Without script every column shows and each preset is a plain link (grclibrary.ai points them at its per-preset static pages). The table has a single header row by design, so the script has no `colspan` handling: a matrix with grouped or spanning headers is out of contract. Cells hold short identifiers and count links only, never third-party control text. Reference page: `crosswalk.html`. From 1.7.0 the script has 2 more options, each opt-in by markup; a page without them behaves exactly as above (the 1.5 and 1.6 matrix checks, 54 of 54, pass unchanged on `crosswalk.html` 1.7.0). - **Column toggles.** `

1Title