Skip to content

Curated page (/on/:slug) UI/UX: an MVP layout that reads as a curated article: what it must show, reference patterns (Wikipedia, Britannica, Merriam-Webster), wireframes, and how arrangement is decided (fixed template now, curated arrangement later; under #193) #309

Open

Description

@holden

Design issue, 4 November 2026, under #193. Posted on the owner's words in chat after reading /on/nepotism, /on/love and /on/war on the public host today: "we need a new layout for the curated page … this is not clear at all … this is very different from the source record pages, this is the curated version … use examples like Wikipedia, Britannica … maybe the design itself should eventually be curated … this needs to be an MVP design". Scope: the public curated page /on/:slug only. Out of scope: the source-records view (/on/:slug/materials), the curator profile pages (#299), the panel's consensus (#300), the runtime, any instruction or model. No live step follows from this text; nothing here changes what a persona may do (it never writes definitions, quotations, claims or entities; it chooses from the records a page already holds and gives a reason under 100 characters).

Revision 1, 4 November 2026, after an independent read-only audit of the brief (B+, 87/100: "approve the direction and move it to static mockups; resolve the layout and content rules before implementation"), pasted by the owner, and the owner's words: "iOS will be more important than desktop so it needs to work for both and probably the MVP plan is better as the custom layout is even less useful for iOS". Four resolutions, all in the text below: (1) one canonical document order on every screen size, the lead first and the dated news item directly after it, the view switch on both sizes (§4, §5); (2) every published selection renders; the runtime's own caps bound new versions, and the mock tests the longest section (§4 C); (3) the fallback states are checked against the schema on v2 read-only today: no schema change is needed, and each field has a named fallback (§4 H); (4) the success measure is comprehension, three questions answered on the 375 px mock without opening a disclosure, before any height or Lighthouse number (§7 D2, §8). Phone first: the 375 px full entry is the primary deliverable; the desktop is the same document order in two columns; nothing is desktop-only (§5, §7). Option A (fixed template) is confirmed; Option B stays deferred, and on a phone it would amount to order alone (§6). The audit could not verify the cited revision in its own checkout; the serving checkout and GitHub main are both at 4a0b997 (verified by this session).

1. The problem, as the page is built today

Read from the code at 4a0b997 (WordLive, Opening, WholeEntry, CurationReceiptLive) and from the published rows (nepotism version 5 = version record 39, 3 November; love 55; war 58). The owner's reaction is the measurement; D0 below collects the screenshots.

  1. The curated page is the source page with an opening on top. WordLive renders the same headword, rail, definitions column, shelves and related words for both views; "Curated article" adds Opening.section above the definitions and "Source records" removes it. The toggle moves one block. A reader cannot tell what was chosen from what is simply held.

  2. The curator is invisible. No byline. The persona is named only inside each item's note (Inspired by Voltaire · voltaire-whole-entry-v6 · qwen3.5-9b-whole-voltaire-v6, a technical label) and on the receipt page. No date, no one line on what this editor looks for, no link to the curator's own page (Curator pages: one public page per AI personality (dossier sources, model, instruction, audit trail, cost), a directory, wireframes and an MVP (under #193; implements #203's profile pages) #299 will provide one).

  3. The reasons are hidden. The stance, the one thing that makes a curation a curation ("Bierce satire highlights absurdity of power abuse"), sits inside a <details> named "Why this is here". By default the page shows items without the editor's voice.

  4. A stack of tiles, not an article. Highlights are grouped by kind with caps (WholeEntry limits: definitions 1, examples 2, quotes 2, images 1, films 1, music 1, books 1, poems 1, news 1), laid one to three columns wide, with no headings a reader recognises, no reading order and no statement of what the page is about beyond the lead. Nepotism's nine published items read as nine cards.

  5. Time is invisible. A news item expires after 23 hours; the content date is in a disclosure; the page never says "as of". A reader cannot tell what is current from what is permanent.

  6. Abstention is a dead end. With nothing published the page says "No curated choices are currently published for this entry" and shows the source page. An abstention is editorial information (today every arm abstained on greed and bestiality, Personas META: from one curator to a weighted panel — the experiments in stages, the dossier pipeline, consensus with weights, humans outside the gate and a later model bench (under #193) #305 c6635651950) and should read as one.

  7. Reasons are cut at 100 characters, often mid-word (the Stage 1 scorer's note). Whatever the layout shows, it shows that. The cap is a runtime contract matter (Personas META: from one curator to a weighted panel — the experiments in stages, the dossier pipeline, consensus with weights, humans outside the gate and a later model bench (under #193) #305), not a layout one, but the layout must not make a truncated reason look like a finished sentence.

  8. Four of the nine "published" pages show nothing at all (D0, c6637539136): their versions were published under configuration version 8, the active version is 9 since 3 November 15:18 UTC, and the read-time withhold (configuration_changed) hides the whole version behind "No curated choices are currently published". Nepotism, the page the owner read, is one of them. The state table in §4 H now names this state.

2. Who the page is for, and the five jobs, in order

A reader who typed the word into a search engine or came from another word.

  1. Get the best definition at once: the lead in its source's own words, with what kind of text it is (satire, sourced definition).
  2. See what an editor with a point of view thinks is worth seeing on this word, and why, one glance per item.
  3. See what is current apart from what is permanent: the news item, dated, with its "as of".
  4. Trust it: who curated, when, from what, with a visible path to everything the page holds and to the exact record of each choice.
  5. Move on: related words; the same word by another curator (Living curation: three to five personas reach a consensus on each visited page, visit-driven, two layers, per-kind staleness later, current events and living people bounded — design and MVP (under #193; after #298, with #299) #300, later); the curator's page (Curator pages: one public page per AI personality (dossier sources, model, instruction, audit trail, cost), a directory, wireframes and an MVP (under #193; implements #203's profile pages) #299).

Because the persona writes no prose, the page has no lead paragraph in the encyclopaedia sense. Its voice is selection plus a short reason. The layout has to make selection and reason do what prose does on Wikipedia: tell the reader what matters first and why.

3. Reference patterns

Researched 4 November 2026 (two read-only passes over the sites' own pages and style manuals; URLs at the end of each item). Facts, paraphrased; what we take from each is in §3.6.

3.1 Wikipedia: a house-fixed skeleton around an editorial middle

  • Article order is fixed by the Manual of Style: hatnotes → infobox → lead (no heading; defines the topic, says why it matters, summarises the key points; on mobile the first paragraph moves above the infobox) → table of contents → body sections under level-2 headings (order by topic) → appendices in a fixed order (See also, Notes/References, Further reading, External links) → navboxes and categories. The reader learns the skeleton once; only the middle varies. Provenance is not on the page: it is the History tab.
  • The Main Page is the clearest "curated layout" on the web: a fixed two-column slot structure (Today's featured article and Did you know on the left; In the news, On this day and the picture of the day on the right), each slot transcluding a date-named subpage that human coordinators schedule from queues. Every slot has a fixed footer (Archive, Nominate…), a "(pictured)" mark on the one illustrated item, and In the news has a staleness rule (older than the oldest item still in the box). The editors choose content into slots; the slots never move.
  • https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Layout · https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Lead_section · https://en.wikipedia.org/w/index.php?title=Main_Page&action=raw · https://en.wikipedia.org/wiki/Wikipedia:In_the_news

3.2 Britannica: the trust row, and dated news above the lead

  • Order: breadcrumb → lead image with caption → title → one-line descriptor ("French philosopher and author") → byline row: author name and "Britannica Editors", with tooltips "Written by [name, credentials]" and "Fact-checked by Britannica Editors" → "Last updated [date] • History" (link to the article history) → summary and table of contents → Top questions → on topics in the news, a line "News • [headline] • Nov. 3, 2026 (AP)" directly above the first paragraph → sections. The side panel lists Quotes, References & Edit History, Quick Facts, Related Topics and dated "On the Web" links.
  • No "curated by" wording anywhere; editorial provenance is exactly Written by, Fact-checked by, Last updated, History.
  • https://www.britannica.com/biography/Voltaire · https://www.britannica.com/technology/artificial-intelligence

3.3 Merriam-Webster and Dictionary.com: automatic selection labelled on the block, every example dated

  • Merriam-Webster entry: headword block (syllables, pronunciation, audio) → one block per part of speech with numbered senses → "Examples of X in a Sentence" (editorial) → "Recent Examples on the Web", whose header says examples are automatically compiled from online sources to show current usage and, expanded, that opinions in them are not the editors'; each example is the sentence then "— Author, Publication, 8 Sep. 2026" → Word History with "First Known Use: 1533" → Cite this entry ("Accessed 4 Nov. 2026") → Kids, Medical and Legal definitions as their own headed blocks → "Last Updated: 10 Sep 2026 - Updated example sentences".
  • Word of the Day: "Word of the Day: November 4, 2026" → word → "What It Means" → examples → "[Word] in Context" with a dated attributed quotation → "Did You Know?".
  • Dictionary.com: example sentences "From [Publication] ● [date]" with the publication's logo and an opinions disclaimer; a credit line per source dictionary; no updated-on date.
  • https://www.merriam-webster.com/dictionary/cynic · https://www.merriam-webster.com/word-of-the-day · https://www.dictionary.com/browse/cynic

3.4 Wiktionary and the OED: dates lead the citations, revision state on top

  • Wiktionary fixes the section order per language (etymology → pronunciation → part of speech with senses → usage notes → synonyms … → references); under a sense, example sentences come before quotations, and a quotation's citation line starts with the bold year, then author, italic title, publisher, page, in chronological order.
  • OED: a top bar "Revised 2023 (entry history)" → headword → tabs (Factsheet, Etymology, Meaning & use, Pronunciation, Forms, Frequency); each sense is headed by its date range ("1533–", "1607–1859 †Obsolete"), then the definition, then quotations led by the year and the source; frequency is marked "computed programmatically".
  • https://en.wiktionary.org/wiki/Wiktionary:Entry_layout · https://en.wiktionary.org/wiki/Wiktionary:Quotations · https://www.oed.com/dictionary/cynic_n

3.5 Sites that say why an item is shown

3.6 What we take, and what we do not

Take From Becomes on /on/:slug
A house-fixed skeleton: lead first, fixed appendices last, editorial middle Wikipedia MOS §4 A–G in a fixed order; sections with a reader's heading each
Content chosen into slots that never move; a "(pictured)" style mark Wikipedia Main Page Option A in §6; the register chip (Satire, Sourced definition)
The trust row: who wrote it, who checked it, last updated, history link Britannica The byline line: curated by, date, AI-selected, not human-reviewed (or reviewed by), How this page was curated →
A dated news line above the lead, source named Britannica In the news with as of, source and date (§4 F)
"Automatically compiled … to show current usage" said on the block; "— Author, Publication, date" on every example; "Last updated" on the entry Merriam-Webster The news block's own label; source and date on every item; the provenance footer
Year-first citations; revision state at the top OED, Wiktionary Dates on every item; version and published-at in the masthead
A short "who selected this" label with the mechanics one step away Google, NYT, Apple News The reason on the surface; model, instruction and exact record in the disclosure and the receipt
Do not take Why
A prose lead or summary The persona writes none, by rule
A table of contents One screen of five short sections
Burying the "why" behind a menu On this page the why is the editorial content
Infobox-style fact tables The source-records view already lists the facts; this page is the selection

4. What must be on the page, in this order

One document order, on every screen size. It is the reading order and the keyboard order. On a phone it is the visual order top to bottom. On a desktop the same document is placed in two columns: the column carries A to D in that order; the rail beside it carries E and F. Nothing changes place between sizes, and nothing is desktop-only.

  • A. Masthead. The eyebrow "On nepotism"; the headword (h1), pronunciation and part of speech; the byline line Curated by ◉ Voltaire (inspired) · date published · version · status chip AI-selected, not human-reviewed (or Reviewed by … when a review exists) · How this page was curated → (the receipt, which exists). The persona mark and name link to the curator page (Curator pages: one public page per AI personality (dossier sources, model, instruction, audit trail, cost), a directory, wireframes and an MVP (under #193; implements #203's profile pages) #299) when it exists, otherwise to the receipt. The view switch sits in the masthead on both sizes, worded as what it is: This editor's selection / Everything this page holds (/materials).
  • B. The lead. As today: the source's words quoted large, the register chip (Satire, Sourced definition), source, author, work, year, required credits. Changed: the reason is visible by default as one line under the attribution, labelled Why this leads. The disclosure keeps what is one step away today (meaning, exact record, basis, receipt link).
  • C. In the news, directly after the lead, only when the version holds a news item: the headline, its source and date, the reason, and the block's own label as of HH:MM UTC, [day] from the publication time (the Merriam-Webster pattern: the block says how it was compiled and when). Past the shelf's expiry the existing read-time withhold rule applies and the block says A headline chosen on [day] is no longer current; nothing was put in its place. Never a silent stale headline.
  • D. The permanent sections, fixed order, fixed labels, each shown only when it has an item: Definitions · Quotations · Examples (exemplars, claims) · In culture (artworks, films, music, books, poems). Each section has a reader's heading, not a kind name. Every published item renders. New versions are bounded by the runtime's own caps (WholeEntry: definitions 1, examples 2, quotes 2, images, films, music, books, poems and news one each), so In culture holds at most five; versions published before those caps render whole. The 375 px mock tests the longest case (nepotism version 5: five works). Items keep today's verbatim rule and credits and gain the visible reason line (item anatomy below).
  • E. The editor's take (the rail on a desktop; after D on a phone). One line on what this editor looks for, from the dossier's reviewed public summary (priv/curation/agents/instructions/*.md, the text Curator pages: directory, profile and version pages (#299 M1–M7) #304's Curators.summarized() reads, so Curator pages: one public page per AI personality (dossier sources, model, instruction, audit trail, cost), a directory, wireframes and an MVP (under #193; implements #203's profile pages) #299 and this page agree). The counts the composition already knows: records considered, chosen, withheld. What was withheld and why, each with its stored reason, as today's withheld block but placed, not hidden. The link Everything this page holds →.
  • F. Related words, last in the rail and last on a phone, as today's way_out.
  • G. Provenance footer. Version · published at · the persona's instruction version · model · configuration version · receipt link · other published versions. The technical label moves here from the item notes.
  • H. States, each checked against the schema on v2 (read-only, 4 November 2026); no schema change is needed.
State Shown Field Fallback when missing
Published the page above editorial_compositions.current_published_version_id, editorial_composition_versions.inserted_at, editorial_composition_publications.committed_at none needed
Review status Reviewed by … or AI-selected, not human-reviewed editorial_composition_publications.authority_kind, editorial_composition_reviews (the receipt reads both) authority_kind = single_editor with no review row → the AI chip
Abstained (assessed, nothing published) masthead; Voltaire has not published a selection for greed · last assessed at … · the stored abstain reason · the holdings count · the link to everything the page holds curation_refresh_states.last_outcome = abstained, last_completed_at; the reason from inference_attempts.result->>'abstain_reason' on the attempt whose request_key is proposal:<composition>:<configuration version>:<generation> no reason text → gave no reason; a reason over 100 characters is impossible (contract)
Refused (assessed, output rejected by the contract) as abstained, with the editor's output did not meet the rules and no reason last_outcome = refused, refusal_reasons on the attempt none needed
Never assessed masthead; No curator has assessed this entry yet · holdings count · the link no curation_refresh_states row for the composition, or last_completed_at null none needed
Withheld whole version (configuration changed, scope changed, approval withdrawn, composition retired) masthead; the sentence in the D1 labels table, row 20 (c6637566629): "A selection published on {date} is not shown: {reason}. Nothing was put in its place." · the holdings count · the link to everything the page holds · the receipt link the existing read-time withhold and its reason clauses (Opening.withheld_reason/1): editorial_composition_versions.configuration_version_id behind the active curation_configuration_versions row (D0 found four of the nine published pages in this state: truth 45, nepotism 39, greed 40, patience 43; #309 c6637539136) none needed; a real page, never the bare "No curated choices" sentence
Withheld item in E, as today the existing read-time withhold (#255 §2.3) with its reason as today
Expired news C's wording above the shelf citation's expiry via editorial_composition_items.shelf_citation_id and the existing withhold as today
Dates on items year or date on every item ContentDate.text/1 (already in the disclosure), the record's year, the headline's date undated
Previous versions footer editorial_composition_publications (the receipt's version list) none needed
Several curators (#300) a strip under the byline, Also curated by … not yet; out of scope here beyond the slot the strip is absent

Each item, the same anatomy everywhere:

┌ SECTION LABEL (fixed vocabulary) ──────────────────────────────────┐
│ ▸ The record in its source's own words, or its title                │  verbatim, never rewritten
│   Source · author · year or date · licence credit when required     │  facts from the record
│   — "the editor's reason"                                           │  visible by default; ≤100 chars; model or rule
│   Why this is here ▾   meaning · exact record · basis · receipt     │  one step away, as today
└─────────────────────────────────────────────────────────────────────┘

5. Wireframes

Phone first. Illustrative: the items, counts and notes are nepotism version 5's as published (a Bierce lead, a WordNet sense, two Wiktionary quotations, five works; version 5 holds no news item, so C is drawn from a version that does); titles, the holdings count and the related words are placeholders until D2 reads them from the rows.

Phone (375 px), the full entry, the document order:

┌─────────────────────────────┐
│ wordhoard              ☰    │
├─────────────────────────────┤
│ On nepotism                 │
│ This editor's selection ·   │
│ Everything this page holds  │
│                             │
│ nepotism                    │
│ /ˈnɛpətɪzəm/ · noun         │
│ ◉ Curated by Voltaire       │
│   (inspired) · 3 Nov 2026 · │
│   version 5                 │
│ AI-selected, not human-     │
│ reviewed                    │
│ How this page was curated → │
├─────────────────────────────┤
│ LEAD · Satire               │
│ “ Appointing your grand-    │
│   mother to office for the  │
│   good of the party. ”      │
│ Ambrose Bierce · The        │
│ Devil's Dictionary · 1906   │
│ Why this leads — Bierce     │
│ satire highlights absurdity │
│ of power abuse.             │
│ Why this leads ▾            │
├─────────────────────────────┤
│ IN THE NEWS · as of 03:08   │
│ UTC, 3 Nov                  │
│ ▸ Headline — Source · 2 Nov │
│   — reason                  │
├─────────────────────────────┤
│ DEFINITIONS                 │
│ ▸ favoritism shown to       │
│   relatives or close        │
│   friends by those in power │
│   — WordNet                 │
│   — "WordNet defines job    │
│   favoritism clearly."      │
├─────────────────────────────┤
│ QUOTATIONS                  │
│ ▸ “ … ” — Wiktionary        │
│   — "Retail quote           │
│   illustrates brand         │
│   favoritism."              │
│ ▸ “ … ” — Wiktionary        │
│   — "Political quote shows  │
│   corruption via allies."   │
├─────────────────────────────┤
│ IN CULTURE                  │
│ ▸ … · film                  │
│   — "Film title directly    │
│   references nepo babies."  │
│ ▸ … · album                 │
│   — "Album title explicitly │
│   names the topic."         │
│ ▸ … · book                  │
│   — "Academic text on       │
│   ethnic nepotism politics."│
│ ▸ … · article               │
│   — "Article discusses      │
│   workplace nepotism        │
│   prevention."              │
│ ▸ … · image                 │
│   — "Visual representation  │
│   of letter n concept."     │
├─────────────────────────────┤
│ THE EDITOR'S TAKE           │
│ Reads for the sharpest      │
│ sourced line and the record │
│ that tests it.              │
│ Considered 79 · chose 9 ·   │
│ withheld 0                  │
│ Everything this page holds →│
├─────────────────────────────┤
│ RELATED WORDS               │
│ cronyism · favouritism ·    │
│ patronage                   │
├─────────────────────────────┤
│ Version 5 · published 3 Nov │
│ 2026 03:08 UTC · Inspired   │
│ by Voltaire · instruction   │
│ v6 · qwen3.5 9B · config 9  │
│ How this page was curated → │
│ Other versions: 4, 3 →      │
└─────────────────────────────┘

Desktop (1280 px), the same document in two columns; the column is A to D, the rail is E and F:

┌──────────────────────────────────────────────────────────────────────────────────────────┐
│ wordhoard                                        Search ▭               Register  Log in │
├──────────────────────────────────────────────────────────────────────────────────────────┤
│ On nepotism                              This editor's selection · Everything this holds │
│                                                                                          │
│ nepotism   /ˈnɛpətɪzəm/ · noun                                                           │
│ Curated by ◉ Voltaire (inspired) · 3 Nov 2026 · version 5 · AI-selected, not human-      │
│ reviewed · How this page was curated →                                                   │
├────────────────────────────────┬─────────────────────────────────────────────────────────┤
│ THE EDITOR'S TAKE              │ LEAD · Satire                                           │
│ Reads for the sharpest sourced │ “ Appointing your grandmother to office for the good of │
│ line and the record that tests │   the party. ”                                          │
│ it.                            │ Ambrose Bierce · The Devil's Dictionary · 1906          │
│                                │ Why this leads — Bierce satire highlights absurdity of  │
│ Considered 79 records ·        │ power abuse.                        Why this leads ▾    │
│ chose 9 · withheld 0           │                                                         │
│ Everything this page holds →   │ IN THE NEWS · as of 03:08 UTC, 3 Nov                    │
│                                │ ▸ Headline — Source · 2 Nov — reason                    │
│ RELATED WORDS                  │                                                         │
│ cronyism · favouritism ·       │ DEFINITIONS                                             │
│ patronage                      │ ▸ favoritism shown to relatives or close friends by     │
│                                │   those in power — WordNet                              │
│                                │   — "WordNet defines job favoritism clearly."           │
│                                │                                                         │
│                                │ QUOTATIONS                                              │
│                                │ ▸ “ … ” — Wiktionary, retail                            │
│                                │   — "Retail quote illustrates brand favoritism."        │
│                                │ ▸ “ … ” — Wiktionary, politics                          │
│                                │   — "Political quote shows corruption via allies."      │
│                                │                                                         │
│                                │ IN CULTURE                                              │
│                                │ ▸ … · film     — "Film title directly references nepo…" │
│                                │ ▸ … · album    — "Album title explicitly names the topic"│
│                                │ ▸ … · book     — "Academic text on ethnic nepotism…"     │
│                                │ ▸ … · article  — "Article discusses workplace nepotism…" │
│                                │ ▸ … · image    — "Visual representation of letter n …"   │
├────────────────────────────────┴─────────────────────────────────────────────────────────┤
│ Version 5 · published 3 Nov 2026 03:08 UTC · Inspired by Voltaire · instruction v6 ·     │
│ qwen3.5 9B · configuration 9 · How this page was curated → · Other versions: 4, 3 →      │
└──────────────────────────────────────────────────────────────────────────────────────────┘

Abstained (greed, after today's batch), 375 px:

┌─────────────────────────────┐
│ On greed                    │
│ This editor's selection ·   │
│ Everything this page holds  │
│                             │
│ greed   /ɡriːd/ · noun      │
│ ◉ Voltaire has not          │
│   published a selection     │
│   for greed.                │
│ Last assessed 4 Nov 2026    │
│ 15:58 UTC · abstained:      │
│ "<stored reason>"           │
│ This page holds 3 senses,   │
│ 12 quotations, 4 works,     │
│ 2 headlines.                │
│ Everything this page holds →│
├─────────────────────────────┤
│ RELATED WORDS               │
│ avarice · covetousness      │
└─────────────────────────────┘

6. How arrangement is decided: fixed template now, curated arrangement later

The owner's question: should the design itself be curated, a lite system like Wikipedia's markup, or should the page "magically" arrange the curated elements? Three options, with a recommendation.

Option A, fixed template (the MVP). The page has named slots (masthead, lead, the five sections in a fixed order, the editor's take, related, provenance) and the existing roles and kinds fill them deterministically. The curator decides what; the template decides where. No new data, no new schema; every published version renders the same way, so a reader learns the page once. This is what Wikipedia's layout conventions do for article structure and what Merriam-Webster does for its example blocks: the editorial act is selection, the structure is fixed by the house.

Option B, curated arrangement v1 (next, after a curator passes the publishing gate). The curator (model, or a person on the curation screen) proposes, beside its choices, a small declarative arrangement: an ordered list of sections from a fixed vocabulary, each naming the version's own item ids, with optional omission of a section. In the spirit of a MediaWiki template with named parameters, Portable Text blocks or a Shopify JSON template: structure as data, validated against a schema, hashed into the version and shown on the receipt, rendered by the same components as Option A. Sketch:

arrangement: curated-article-v1
sections:
  - slot: lead          items: [c1]
  - slot: news          items: [c21]       as_of: 2026-11-04T15:54Z
  - slot: definitions   items: [c5]
  - slot: quotations    items: [c3, c4]
  - slot: culture       items: [c12, c14]
  - slot: omit          slots: [poems]

Constraints that keep it "lite": slots from a fixed vocabulary; the lead first and provenance last always; items only from the version's own items, each at most once; caps per slot as today; no free text, the only words are the item reasons that already exist; schema-validated at commit (an invalid arrangement is refused like an invalid selection, #303's contract pattern); arrangement_hash today digests the items, v1 digests items plus arrangement; a human override on the curation screen records origin: owner and shows on the receipt. What it buys: a persona can say "lead with the satire, then the news, skip the art" and that choice is reviewable and scorable like any other.

Option C, automatic arrangement. Heuristics or a model decide the layout per page. Not recommended: it is unreviewable, it breaks the consistency a reader relies on, and the quality work so far (#298, #305) shows that the model's reasons, not its lists, are the weak point. Adding a second unmeasured output would not help.

Recommendation (confirmed in Revision 1, phone first): A now, built as slots so B is a data change and not a redesign; on a phone the page is one column, so a curated arrangement would amount to section order alone, which is a further reason to defer it; B as its own issue after Stage 3 (#305) and alongside the panel (#300), where several curators on one page is exactly when arrangement starts to carry meaning.

What the surveyed systems have in common, which is Option B's design (researched 4 November 2026): a closed vocabulary of typed blocks or slots; author-side data only, no styling; validation at save time; a version or revision record; rendering owned by the host.

7. MVP plan

Phone first: every deliverable is reviewed at 375 px before 1280 px. iOS Safari is the reference browser (safe-area insets, no viewport-height traps, native <details>, tap targets of at least 44 px, no hover-only affordance, type that does not trigger zoom on focus).

  • D0. Baseline. Screenshots of /on/nepotism, /on/love, /on/war and an abstained page at 375 and 1280 px, light and dark, from the demo server or after the day's batches (never a visit to /on/* on 4007 or the public host while a batch runs). Attached here.
  • D1. Information architecture agreed (§4 A–H), with the wording of every fixed label (section headings, byline, status chip, switch, the news block's label, the state sentences) in one table in this issue. The D1 table (c6637566629) is the single source of every label's wording; where this body and D1 differ, D1 wins.
  • D2. Static mock on the app's tokens in docs/sketches/curated-page/ (the Word page implementation: inventory and compare whole-page mockups, then build the selected compact design #131 pattern), the 375 px full entry first (nepotism version 5, the longest In culture section, plus a version with a news item), then the abstained state, then the desktop; light and dark. Reviewed here before any LiveView change.
  • D2b. Comprehension check on the 375 px mock, the original complaint measured: at least three readers (the owner and two others) each answer, without opening any disclosure, (1) who selected the lead, (2) why it leads, (3) where all the source records are. Target 3 of 3 for every reader; results recorded here. The mock does not pass to D3 until it does.
  • D3. Implement the curated layout as its own page composition in WordLive (the :on action stops rendering the source column, rail, shelves) with Opening components reused and extended: visible reason line, section headings, byline and switch in the masthead, In the news after the lead, editor's take, dates, provenance footer, the H states. /materials unchanged. No change to the runtime, the contract or any table.
  • D4. States as in §4 H: abstained, refused, never assessed, withheld, expired news, several versions.
  • D5. Accessibility and phone: document order = reading order; real h1/h2; disclosures keep state; contrast on the status chip; prefers-reduced-motion; iOS Safari checked on a device, not only in a simulator.
  • D6. Measure on the three pages: the D2b questions repeated on the built page; height at 375 px against today (Word page height and shelf templates: fold the prose, one template per content type, the world above the fold — measured on /define/love, phased #111's method); time to the lead; no horizontal scroll; Lighthouse accessibility not below today's.
  • D7. Deploy by fast-forward with no restart (no config/*.exs, no mix.lock change), between batches, on the owner's yes; before and after screenshots attached.

8. Acceptance

  • On the 375 px page, without opening anything, a reader can say who curated it and when, which item leads and why, every chosen item with its source, date and the editor's reason, which items are current and as of when, and how to reach everything the page holds and the receipt (D2b, then D6: 3 of 3 questions for every reader).
  • The document order is the same on every screen size; nothing is desktop-only; the view switch is reachable on both.
  • Every published selection renders; the longest section in the data today renders whole.
  • The curated page and the source-records view are visibly different pages, not the same page with one block toggled.
  • An abstained, refused or never-assessed page is still a page (§4 H), with the stated fallbacks.
  • The persona's text on the page is only its stored reasons; nothing is rewritten or generated for the layout.
  • D0, D2b and D6 screenshots and results posted here; the owner's word closes this issue.

9. Not in this issue, and relations

Activity

  1. holden commented on Nov 4, 2026

    @holden
    MemberAuthor

    Revision 1, 4 November 2026: the audit's four findings resolved, phone first

    The body above is revised in place (the revision note at the top says what changed). In short:

    1. One document order on every screen size: masthead (with the view switch on both sizes) → lead → In the news directly after the lead, with its as of → Definitions → Quotations → Examples → In culture → the editor's take → related words → provenance. The desktop is the same document in two columns (the column A–D, the rail E–F); the phone is the same order top to bottom. §4 and §5 redrawn, the 375 px full entry first.
    2. Every published selection renders. New versions are bounded by the runtime's own caps (In culture at most five); older versions render whole; the 375 px mock tests nepotism version 5's five works. §4 D.
    3. Fallback states checked against the schema on v2 read-only today: no schema change. Abstained = curation_refresh_states.last_outcome with last_completed_at and the reason from the attempt named by request_key; never assessed = no refresh row; refused, withheld, expired news, review status, dates and previous versions each have a field and a named fallback. §4 H, one table.
    4. The success measure is comprehension: on the 375 px mock, at least three readers answer who selected the lead, why it leads and where the source records are, without opening a disclosure, 3 of 3 each, before any height or Lighthouse number. §7 D2b, §8.

    Owner's words: "iOS will be more important than desktop so it needs to work for both and probably the MVP plan is better as the custom layout is even less useful for iOS." So: iOS Safari is the reference browser, nothing is desktop-only, Option A (fixed template) is confirmed, Option B stays deferred (on a phone it would be section order alone).

    The audit's note that the cited revision was not in its checkout: the serving checkout and GitHub main are both at 4a0b997.

  2. holden commented on Nov 4, 2026

    @holden
    MemberAuthor

    D0 baseline, 4 November 2026: the curated page as it is today

    Condition. Served by main 4a0b997 (the worktree on branch claude/309-curated-page) on the 4017 demo server, against devils_dictionary_test_ux1: a private copy of v2 taken in a read-only transaction at 17:27:48 UTC (pg_dump, restored 17:29:22, ANALYZE 17:29:28). Public reading, as through the tunnel; the serving checkout's shelf retention (config.exs + dev.exs; the test env's two-hour suite windows would have withheld love's and war's quotations); no refresh visit (source_records_preview_read_only); no Oban queue; every HTTP call stubbed. No request reached /on/* or /define/* on 4007 or the public host. Every pilot composition's refresh_after had already passed (15:37 to 17:22 UTC), so a visit there would have admitted a run even with the gateway paused (inference_services 1 paused since 16:23:53 UTC; 0 attempts admitted or dispatched at 17:26 UTC).

    Page Composition Current published version What the page shows today Height at 375 px Height at 1280 px Lead starts (375 / 1280)
    nepotism 6 5, record 39, config. version 8, 9 items withheld as a whole (configuration_changed); "No curated choices are currently published for this entry" 4,115 2,892 none
    love 1 9, record 55, config. version 9, 5 items the lead and 4 highlights 7,062 3,906 793 / 552
    war 2 9, record 58, config. version 9, 5 items the lead and 4 highlights 6,981 4,274 793 / 552
    greed 7 4, record 40, config. version 8, 6 items withheld as a whole (configuration_changed); same sentence; last assessed 09:37:36 UTC, abstained (attempt 111) 4,156 2,910 none
    bestiality 10 none, never published same sentence; last assessed 09:43:02 UTC, abstained (attempt 118) 4,188 2,939 none

    CSS pixels, every <details> closed, measured after fonts loaded. No horizontal scroll on any page at either width. Love and war carry 14 disclosures each.

    Findings that change the brief (each from the rows, read-only):

    1. Four of the nine published pages show no curated selection today. Truth (record 45), nepotism (39), greed (40) and patience (43) were published under configuration version 8. Configuration 1 has been on version 9 since activation 9 (3 November, 15:18:07 UTC, "Curation agents: close out v6, retest v7, then controlled model and personality comparisons on identical packets (under #193) #298 B2"), and Standing.configuration/1 withholds a version whose configuration version is no longer current. So since then /on/nepotism on the live host has read as the source page with the empty sentence. Withheld as a whole is today's most common curated-page state, and §4 H has no row for it: it falls through to the sentence that applies when nothing was ever published. D1 proposes its wording (configuration changed, scope changed, approval withdrawn, composition retired: the reasons Published.current/1 returns).
    2. Greed is not the abstained state. It has a published version that is withheld as a whole, and its latest assessment abstained. The page that was assessed and has nothing published is bestiality (composition 10). D0 has both; the D2 abstained mock uses bestiality's rows, and greed is drawn as "withheld as a whole".
    3. Nepotism version 5 already has a news item. Its position 8, "Article discusses workplace nepotism prevention.", is a news shelf item (observed 3 November, 03:02:49 UTC), not an In culture work. So version 5 reads: In the news 1 · Definitions 1 · Quotations 2 · In culture 4 (image, film, music, book). The longest In culture section in the data is truth version 5 (record 45, 10 items): image, film, music, book and poem, plus a Johnson definition and a news item. D2 mocks nepotism version 5 as asked and adds truth version 5 as the longest case.
    4. Every stored abstain reason is exactly 100 characters (attempts 111, 113, 118, 121), so each was cut at the cap. The page will mark such a reason as cut rather than present it as a finished sentence (D1).
    5. Today's default layout is reference_article, not the float layout §1 describes. That float layout is ?layout=current. The default shows "Selected reading"; "Selected by Inspired by Voltaire, an AI curator · published 4 November 2026"; "Another definition", "In language" and, in the rail, "A visual reference"; each work tile is labelled "Selected from provider metadata"; and each item has two closed disclosures ("Dates, evidence & exact record", "Why this is here"). The diagnosis stands: the reasons are hidden, the curator is a label, and the source page continues underneath.

    Screenshots (raw files at aa47ce0):

    The 375 px first screens:

    /on/nepotism at 375 px, first screen, light

    /on/love at 375 px, first screen, light

    /on/war at 375 px, first screen, light

    /on/bestiality at 375 px, first screen, light

    Next: D1, the labels table, for the owner to confirm.

  3. holden commented on Nov 4, 2026

    @holden
    MemberAuthor

    D1 labels, 4 November 2026: every fixed label on /on/:slug, for the owner to confirm

    Confirmed by the owner, as amended, 4 November 2026 at 22:38 UTC ("Confirm as amended"). The two amendments from the D2b pre-check (c6637829437) are made in rows 3, 7, 9 and 15 below and marked amended.

    Amended 5 November 2026, 01:29 UTC, as the audit session's recommended defaults (owner may override): rows 2, 10b, 17c, 18 and 22, each marked default. See c6647027467 for the open points they settle.

    Each fixed word on the curated page, in document order. {…} is filled from the rows named in §4 H; nothing in this table is generated, and the editor's own words on the page are only its stored reasons. Dates are written 3 November 2026, times 03:08 UTC.

    # Where Label Filled from, and when it shows
    1 Masthead, eyebrow On {word} as today
    2 Masthead, view switch (both sizes) This editor's selection · Everything this page holds replaces "Curated article / Source records"; the second is /materials (default: the same two labels on /on/:slug/materials, a label change only; /words keeps its own)
    3 Masthead, byline the mark AI · Selected by an AI editor inspired by {Voltaire} · {published date} · version {n} (amended: the mark is AI, never the persona's initial) the persona name from Profiles ("Inspired by Voltaire"), linked to the curator page when #299 is live, otherwise to the receipt
    4 Masthead, status chip AI-selected · not reviewed by a person authority_kind = single_editor and no accepted review (every current version)
    4a Reviewed by {reviewer} · {date} an accepted editorial_composition_reviews row for this version
    4b Selected by a person authority_kind = operator (no human actor's name on a public page, #299 M5)
    5 Masthead, link How this page was curated → the receipt, /on/{slug}/receipt/{version}
    6 Lead, label Leading definition · register chip Satire / Sourced definition the chip as today
    7 Lead, visible reason the mark AI · Why it leads “{stored reason}” (amended: the AI mark) the item's note, shown by default
    8 Any reason at the cap “{stored reason}” · cut at 100 characters a stored reason of exactly 100 characters that does not end in ., !, ? or …; the mark sits outside the quotation marks, in the muted style, and the text is never altered; why exactly 100 means the model was stopped at the cap: c6644017340
    9 Each item, disclosure About this choice (amended: was "Record and evidence") today's "Why this leads" / "Why this is here" and "Dates, evidence & exact record", merged into one disclosure per item: meaning, kind of text, content date, basis, exact record, receipt
    10 Section In the news only when the version holds a news item, directly after the lead
    10a News, the block's own label Headlines change. Found {observed date, time}; shown until {expiry date}. the shelf citation's observed_at and expires_at (nepotism version 5: found 3 November 2026, 03:02 UTC; shown until 10 November 2026)
    10b News, expired A headline chosen on {date} is no longer current; nothing was put in its place. the existing read-time withhold (retention_expired) on a news item (default: not built. The withheld entry carries only retention_expired, not the item's kind, so the page cannot tell a headline from another shelf item; it shows the row 17d line "Withheld: the selected observation's retention window has expired. Nothing was put in its place.")
    11 Section Definitions definitions (another sourced definition)
    12 Section Quotations quotes (sense quotations and quotation shelves)
    13 Section Examples examples (exemplars, linked claims)
    14 Section In culture images, films, music, books, poems, in that order
    14a In culture, the kind on each item Image · Film · Music · Book · Poem the shelf kind or catalog kind
    15 Each item, visible reason the mark AI · Why it's here “{stored reason}” (amended: the AI mark) the item's note, shown by default
    16 Each item, date {year} or {date} · undated when there is none ContentDate, the record's year, the headline's date
    17 Section, the editor's take The editor after In culture on a phone; the rail on a desktop
    17a {one sentence per persona, below} fixed here until #304's summaries merge; the code reads the reviewed summary file when one exists
    17b {the dossier's disclosure, verbatim} e.g. “An AI selection lens inspired by Voltaire; not his voice or an assertion of his opinions about modern events.” the persona's dossier (personas/voltaire/v8/profile.json, disclosure)
    17c This page holds entries from {4 dictionaries}, {43 senses}, their quotations, and what discovery found for {word}. The editor chose {k}{, and {w} are withheld}. (default: the wording the D2b readers saw and passed; was "This page holds {n} records.") the page's own counts (the source-records view's), the version's items, the read-time withheld list
    17d Withheld items, listed in the editor's take Withheld: {reason}. Nothing was put in its place. as today (Opening.withheld_reason/1)
    17e Everything this page holds → /materials
    18 Section Related words · All related words → (default: the first eight chips of the groups in their order, and the link to /materials#related when there are more; the full way out, with the source stack, stays on /materials)
    19 Footer heading About this version
    19a Footer line Version {n} · published {date, time} · instruction {voltaire-whole-entry-v6} · model {qwen3.5-9b-whole-voltaire-v6} · configuration version {8} · How this page was curated → · Earlier versions: {4, 3, 2, 1} the technical label moves here from the item notes
    20 State: withheld as a whole (new row for §4 H, D0 finding 1) A selection published on {date} is not shown: {reason}. Nothing was put in its place. Published.current/1 → {:withheld, reasons}; reason clauses as the page already words them: "its curation configuration has changed since it was published", "the words it was made for have changed", "its approval was withdrawn", "its composition was retired"
    21 State: abstained, nothing shown No selection is published for {word}. The AI editor inspired by {Voltaire} last assessed it on {date, time} and chose not to select: “{stored reason}” curation_refresh_states.last_outcome = abstained, last_completed_at; the reason from the attempt named by request_key; no reason → … and gave no reason.
    22 State: refused No selection is published for {word}. The AI editor inspired by {Voltaire} last assessed it on {date, time}; its answer did not meet the rules, so nothing was published. last_outcome = refused (default: not built, no data path today: curation_refresh_states.last_outcome has no refused value. Build it when it can be refused.)
    23 State: never assessed No selection is published for {word}. No editor has assessed it yet. no refresh row for the composition, or last_completed_at null; also a page with no composition
    24 Every state This page holds {3 definitions, 12 quotations, 4 works, 2 headlines}. Everything this page holds → the page's own counts

    The one sentence per persona (17a), written from each dossier's selection field in the page's own voice, never the persona's:

    Persona Sentence
    Voltaire (inspired) Looks for sourced material that tests a confident claim against its consequences.
    Hitchens (inspired) Looks for sourced material whose own evidence tests whether the word fits a real case.
    Bierce (inspired) Looks for sourced material that sets a professed principle beside the interest behind it.
    Generic editor Chooses the clearest sourced record for each meaning, with no persona lens.

    Three changes from the issue's own wording, with the reasons:

    • Byline (3). The issue has "Curated by ◉ Voltaire (inspired)". D2b's first question is "who selected the lead", and that wording invites the answer "Voltaire". "Selected by an AI editor inspired by Voltaire" gives the true answer in one line and matches the dossier's disclosure ("not his voice").
    • One disclosure per item (9). Today each item has two closed disclosures, so love and war carry 14 each. With the reason visible, one is enough.
    • The news label (10a) uses the headline's own observation and expiry times, not the version's publication time. "As of" means when the headline was seen, and the expiry tells a reader how long it stays.

    State 20 is new. D0 found that four of the nine published pages are withheld as a whole today and fall through to "No curated choices are currently published for this entry".

    D2 (the static mock) starts now on these labels; a change you name here is a text edit in the mock.

  4. added 2 commits that reference this issue on Nov 4, 2026
  5. holden commented on Nov 4, 2026

    @holden
    MemberAuthor

    D2 static mock, 4 November 2026: the curated page as its own article, phone first

    Where. docs/sketches/curated-page/ at bddf431 on claude/309-curated-page, following the #131 pattern: static HTML on the app's own tokens (tailwind.css imports assets/css/app.css), ?theme=dark for the dark page, with content.json captured by capture.exs from the private read-only copy of v2 (17:27:48 UTC) through the page's own reader (PublishedReader.arrangement/3). Every word is a D1 label (c6637566629), a record the site holds itself (Bierce, Johnson, WordNet, Wiktionary, quoted with their required credits), or the editor's stored reason as stored. Provider payloads are [bracketed] placeholders: every shelf item's title, creator, image and credit are held for seven days under its provider's terms (Unsplash, CineGraph, Spotify, Open Library, PoetryDB, Wikiquote, Bing News), so none is copied into the repository. The stored abstain reasons are model text, so the sketch shows each one's length and attempt id; the built page will show the text.

    Sketch What it tests
    nepotism.html the full entry: version 5 (record 39), nine items. Lead, then In the news (its position 8 is a news item, D0 finding 3), Definitions 1, Quotations 2, In culture 4 (image, film, music, book), the editor, related words, about this version
    truth.html the longest case: version 5 (record 45), ten items, In culture with five works
    love.html version 9 (record 55), what the live page holds today, beside D0's love
    bestiality-abstained.html abstained: assessed, nothing ever published (attempt 118)
    greed-withheld.html withheld as a whole (D1 row 20): version 4 (record 40), the state of truth, nepotism, greed and patience today

    Screenshots, 375 px first (2x), then 1280 px, light and dark:

    nepotism sketch, 375 px, screen 1 screen 2 abstained, first screen withheld as a whole, first screen

    Layout decisions (each against §4 and §5):

    • One document at every width. The phone order is masthead (view switch first), lead, In the news, Definitions, Quotations, Examples, In culture, the editor, related words, about this version. At lg the same document becomes two columns: the column holds the lead through In culture, and the rail sits on the right, not the left as §5 drew it. The rail comes after the column in the document, so a right rail keeps visual order and reading and focus order the same (WCAG 1.3.2, 2.4.3).
    • The view switch is a two-part segmented control, each half a 44 px target on a phone. Every reason is visible, beside the AI mark, under the record it explains. One disclosure per item, closed by default (nepotism has 9 disclosures; live love and war have 14).
    • The editor's take counts only what the page already counts ("entries from 4 dictionaries, 2 senses, their quotations, and what discovery found … The editor chose 9"). The wireframe's "Considered 79" exists only in the attempt's packet_summary (counts.offered is 81 for nepotism's attempt 57), and Curator pages: one public page per AI personality (dossier sources, model, instruction, audit trail, cost), a directory, wireframes and an MVP (under #193; implements #203's profile pages) #299 M5 keeps packet_summary off public pages.

    Heights (CSS px, <main> only, because the live page's site footer is 2,636 px at 375 and 1,796 at 1280 and stays):

    375 px 1280 px Lead starts (375 / 1280)
    love today (D0), 5 items, 14 disclosures 4,301 1,985 793 / 552
    love sketch, the same 5 items, reasons visible, 5 disclosures 3,872 2,322 553 / 525
    war today (D0), 5 items 4,220 2,353 793 / 552
    nepotism sketch, 9 items 5,208 3,446 553 / 525
    truth sketch, 10 items 5,673 3,699 553 / 525

    The sketch's lead positions exclude its own 90 px (375) and 42 px (1280) sketch banner. At 375 the lead now starts on the first screen (812 px); today it starts at 793, under the fold once the first line is counted. At 1280 the sketch is taller than today's page because the reasons are now on the page and not inside disclosures. #111's method on the built page (D6) replaces these numbers.

    D2b pre-check, not the gate. Two fresh subagents were given only the seven 375 px screens of nepotism.html at c587a31 and the three questions, with no other context: reader A (Sonnet) and reader B (Haiku). Both answered 3 of 3: (1) an AI editor inspired by Voltaire, not Voltaire and not a person; (2) its reason, "Bierce satire highlights absurdity of power abuse"; (3) "Everything this page holds", the switch's second half and the link in the editor's section. Each also named something that slowed it down, and both points are changed at bddf431:

    • B first read the "V" mark beside each reason as Voltaire's own words. The mark is now AI, beside the byline and every reason, never the persona's initial. (Changes D1 row 7, row 15 and the byline's mark.)
    • A could not tell whether "Record and evidence" held the source records. The per-item disclosure is now About this choice. (Changes D1 row 9.)

    These are pre-checks on an earlier head by models; the gate (D2b) is the owner and two readers the owner names, on this head.

    Not changed by the mock (from the rows, for #305): love's stored reasons cite packet ids ("meaning m0", "s1", "s16"), and every stored abstain reason is exactly 100 characters. The page shows what is stored.

  6. holden commented on Nov 4, 2026

    @holden
    MemberAuthor

    D1 confirmed, 4 November 2026: the labels table stands as amended

    The owner's words, in the executor's chat at 22:38 UTC: "Confirm as amended."

    What was confirmed. The D1 table (c6637566629) with the two amendments that the D2b pre-check found (c6637829437), now made in the table and marked amended:

    • Rows 3, 7 and 15. The mark beside the byline and beside every visible reason is AI, never the persona's initial. A pre-check reader took "V" to mean Voltaire's own words.
    • Row 9. The one disclosure per item is About this choice, not "Record and evidence". A pre-check reader could not tell whether "Record and evidence" held the source records.

    The mock at bddf431 already uses these words, so D2 needs no change. As agreed with the audit session, the D1 table is the single source of every label's wording; where the body's §4 H differs, D1 wins.

    Next: D2b, the comprehension check on the 375 px mock at bddf431 (screens 1–7 in c6637829437). The owner and two readers the owner names answer three questions without opening a disclosure: who selected the lead, why it leads, and where all the source records are. Each reader must get 3 of 3. D3 does not start until it passes.

  7. holden commented on Nov 4, 2026

    @holden
    MemberAuthor

    Audit note, 4 November 2026, 22:50 UTC: the "cut at 100 characters" evidence, the receipt destination, the cleanup entry

    Read-only, from the serving code at 4a0b997 and v2 on 5434, answering an external audit of this issue (22:36 UTC) that asked for evidence behind D0 finding 4 and D1 row 8 and could not find the cleanup entry. Nothing here changes a label; D1 (c6637566629, confirmed as amended at 22:38 UTC) stays the single source of wording.

    1. "Cut at 100 characters" is a generation-time stop, never a storage truncation.

    • The output schema the runtime sends to the model as its format (contract.ex:53 → ollama.ex:56) carries maxLength: 100 on abstain_reason and on every choice reason (section_output.ex:73, :91). Grammar-constrained decoding closes the string at the 100th character; the model cannot emit a 101st.
    • Nothing is cut on the way to storage: a decoded reason over 100 characters is refused as reason_too_long (section_output.ex:156, :160), so no stored reason was ever longer than the stored text.
    • Attempts 111, 113, 118 and 121: each reason is exactly 100 characters; done_reason is stop for all four (the JSON finished; num_predict 1024 did not cut it); the last characters are t, ', o and a space, none a terminal mark.
    • Across every attempt in v2: 39 of 51 stored abstain reasons are exactly 100 characters, the other 12 are 28 to 63 characters, none is 64 to 99, none is over 100. Choice reasons: 6 of 479 are exactly 100, the rest shorter. The hole from 64 to 99 and the spike at 100 are the signature of a hard stop.

    So D1 row 8's rule (exactly 100 characters, no terminal mark) identifies a reason the schema stopped mid-sentence, and "cut at 100 characters" describes what happened to the text; the page never alters it. If a more cautious label is wanted, "stopped at the 100-character limit" says the same with the mechanism; that is the owner's call under D1.

    2. The receipt destination, for D3. Every href="#" in the sketch (18 in greed-withheld.html: the nav, the switch, related words and the footer alike) is a static placeholder, as in the #131 sketches. On the built page the footer's affordance goes to the existing receipt route /on/:slug/receipt/:version (CurationReceiptLive, router.ex:77).

    3. Cleanup when #309 closes, now on the record (it was only in the audit session's private inventory). On the owner's yes, by exact name: database devils_dictionary_test_ux1 on 5434 (9,660 MB; the private copy of v2 taken read-only at 17:27:48 UTC); folder /Volumes/LLM Models/dictionary/private/309-demo/ (v2-dump 1.9 GB, chrome-profile 165 MB, chrome.log, copy-v2.sh, copy-v2.log); after the PR merge, worktree .claude/worktrees/309-curated-page and branch claude/309-curated-page. The 4017 demo server (pid 43895) and the headless Chrome (pid 43900) are still running for the session's own captures and stop with it.

  8. holden commented on Nov 5, 2026

    @holden
    MemberAuthor

    Audit of the D2 mock against this issue, 5 November 2026, 01:10 UTC

    Read-only, from the branch at bddf431 (71 files, all under docs/; no PR yet), the five sketches' HTML, the posted screenshots and the issue record. On the owner's words: "audit it against the design issue and give it a grade".

    Why the work is paused. By design: D2b is this issue's gate ("the owner and two others each answer 3 of 3 … without opening any disclosure"). Two model readers passed on bddf431 (reported in the session at 22:44 UTC, not yet recorded here: that is a gap to close with one comment). The owner's own three answers are what the session waits for, in its chat. Nothing failed.

    §1's eight problems, in the mock: 1 own article with the switch "This editor's selection / Everything this page holds": fixed. 2 curator invisible: fixed (the AI mark, "Selected by an AI editor inspired by Voltaire", the chip "AI-selected · not reviewed by a person", date, version, "How this page was curated"). 3 reasons hidden: fixed ("Why it leads" under the lead, "Why it's here" on every item, records behind "About this choice"). 4 tiles: fixed (h2 sections in one document order: Leading definition, In the news, Definitions, Quotations, In culture, The editor, Related words, About this version). 5 time invisible: fixed ("Headlines change. Found 3 November 2026, 03:02 UTC; shown until …"). 6 abstention a dead end: fixed (bestiality's "No selection is published" page; greed's "A selection published on 3 November 2026 is not shown … Nothing was put in its place"). 7 cut reasons: marked ("cut at 100 characters", evidence c6644017340). 8 four pages showing nothing: represented by greed; the republish is a live step, not layout. 8 of 8 addressed.

    §8 acceptance, at mock stage: the 375 px reader test, the one document order at both widths, the longest section whole (truth, five works), the visibly different pages, the stored-reasons-only rule: shown. Pending by plan: the refused, never-assessed and several-versions states (D4), device Safari (D5), the built-page measurements (D6), and D2b's posted result.

    Findings to carry into D3 (none changes a label): (a) both readers first took "Voltaire" for the selector because it is the only underlined word in the byline; the whole phrase becomes the link. (b) Every link in the sketch is a # placeholder, as expected; the receipt goes to /on/:slug/receipt/:version. (c) The news block says "shown until 10 November 2026" for an item found on 3 November: verify against the retention that applies to news in the serving configuration before the built page prints a date. (d) The cut mark reads the cap per version once D7's 200-character instructions can publish (WholeEntry.reason_cap/1).

    Grade. Design, as a phone-first MVP answer to the complaint: A− (every §1 problem answered on real data, honest states, labels confirmed, two readers at 3 of 3; held back only by the byline link and the unverified news date). Progress on the issue: B (D0, D1, D2 done with evidence; D2b half-recorded; nothing built; the gate waits on the owner).

    Can it be merged? The branch is documentation only (sketches and screenshots, the #131 pattern), so merging it is safe at any time and changes nothing on the site; it would keep the D3 PR small. The page itself is D3, not yet started; it goes live at D7 by fast-forward between batches, on the owner's yes, about three days of session work after D2b.

  9. added a commit that references this issue on Nov 5, 2026
  10. holden commented on Nov 5, 2026

    @holden
    MemberAuthor

    D2b readers, 4 November 2026: two fresh subagents on the bddf431 mock, 3 of 3 each

    Readers. The owner chose them in the executor's chat at 22:44 UTC: "Use two subagents". So the readers are models, not people. Each was a fresh general-purpose subagent that had seen none of this work. Each got only the seven 375 px screens of nepotism.html at bddf431 (blobs 07fa9a9 a8d30a9 457799b b9299fd 3005fa8 6eddd1e f98893d, linked in c6637829437) and the same prompt as the pre-check. They could not open a disclosure, and every one was closed in the screens.

    Reader C (Sonnet) Reader D (Haiku)
    1. Who selected the lead an AI editor inspired by Voltaire, not reviewed by a person (screen 1; repeated on screen 6) an AI editor inspired by Voltaire, not a person (screen 1; screens 6 and 7)
    2. Why it leads the visible reason under "Why it leads", quoted as stored (screen 2) the visible reason under "Why it leads" (screen 2)
    3. Where all the source records are "Everything this page holds": the switch's second half (screen 1) and the link in "The editor" (screen 6) the same two places (screens 1 and 6)
    Score 3 of 3 3 of 3

    What slowed them, and what D3 does about it:

    The gate. The owner's own three answers are not in yet. Relayed by the audit session at 01:05 UTC on 5 November, the owner said: "Ok yes merge and let's build the live version ASAP. We need this done in a worktree so I can audit the live design before we merge." On those words D3 starts now. D2b is not waived: the owner's answers, and a repeat of the two readers, move to D6 on the built page served at localhost:4017. D3 is not merged until they pass there.

  11. added 2 commits that reference this issue on Nov 5, 2026
  12. holden commented on Nov 5, 2026

    @holden
    MemberAuthor

    D3 built, 5 November 2026: the curated page as its own article, on the 4017 demo server

    Where. Branch claude/309-curated-page at 1a9903f (code cad1fdb), merged from main decb956. It is served only by my demo server: localhost:4017 on the Mac, pid 74325, against my private copy devils_dictionary_test_ux1 (v2 as of 4 November, 17:27:48 UTC). The serving rules are the same as D0: public reading, no refresh visit, no Oban queue, every HTTP call stubbed. Nothing reached 4007, the public host, the service, the guards or the budget. No PR and no deploy yet.

    Pages to open on the Mac (in a normal browser; localhost, not 127.0.0.1):

    Address What it shows today
    http://localhost:4017/on/love the full entry: version 9, a lead and four highlights (one Definitions, two Quotations, one In culture)
    http://localhost:4017/on/nepotism withheld as a whole (configuration_changed); last assessed 4 November, 11:22 UTC, abstained
    http://localhost:4017/on/greed withheld as a whole; last assessed 4 November, 09:37 UTC, abstained
    http://localhost:4017/on/bestiality abstained, nothing ever published
    http://localhost:4017/on/love/materials the source records, unchanged

    Nepotism's version 5 (the mock's nine items with a headline) cannot be shown as a full entry on the built page, because the data withholds it as a whole. The page shows the state it is really in. The nine-item arrangement with a news item is covered by the component test opening_article_test.exs, built from version 5's shape.

    Screenshots (raw at 1a9903f):

    What was built, against §4 and the D1 table (c6637566629, as amended):

    • CuratedArticle, a new page composition for :on. In document order:
      • the masthead: the switch "This editor's selection · Everything this page holds" (/materials), "On {word}" and the headword;
      • the byline, where the link is the whole phrase "an AI editor inspired by Voltaire" (D2b readers, audit finding 1) and goes to the receipt /on/:slug/receipt/:version. The status chip, "{date} · version {n}", and "How this page was curated →" follow;
      • the selection;
      • the editor's take, which on a desktop is the rail on the right: the persona sentence (17a), the dossier's disclosure (17b), the holdings sentence, any withheld items with their reasons, and "Everything this page holds →";
      • related words;
      • About this version: version, published date, instruction, model, configuration version, the receipt, the earlier versions as links, and the existing "How this was curated" record.
    • Opening.article/1. The lead, then In the news directly after it, then Definitions, Quotations, Examples and In culture (image, film, music, book, poem). It reuses Opening's own item components in an article mode; there is no second renderer.
      • Every item shows the AI mark, "Why it leads" / "Why it's here", and the stored reason verbatim on the page, and one disclosure, "About this choice": meaning, kind of text, stated reasons, content date, basis and the exact record.
      • The cut mark "· cut at {cap} characters" reads WholeEntry.reason_cap/1, the cap of the instruction the note's author names (audit finding 4). Every published reason today is at 100.
      • A headline carries "Headlines change. Found {date, time}; shown until {date}." Its "shown until" is the citation's real deadline: the earlier of its expiry and its source's retention from observation (ShelfCitations.deadline/2, the same computation the read-time withhold uses), not the stored expiry alone (audit finding 3).
    • States (PageState, read-only):
      • withheld as a whole (row 20): "A selection published on {date} is not shown." with the reason clauses, "Nothing was put in its place.", and the editor's last assessment under the current configuration;
      • abstained (row 21): who, when, and the stored reason with the cut mark, or "… and gave no reason.";
      • never assessed (row 23);
      • every state ends with the holdings sentence and the way to every record.
    • The curation screen's preview now uses the same renderer, so it is still "as the public page will show it once published".
    • Not changed: the runtime, the contract, any table, config/*.exs, mix.lock, /materials, /words/:id/:slug, and ?layout=current.

    Measured on 4017 (CSS px, every disclosure closed; D0's numbers are <main> on the same copy):

    <main> at 375 <main> at 1280 Lead starts (375 / 1280) Horizontal scroll
    love, D0 4,301 1,985 793 / 552 none
    love, D3 5,177 (the article without related words: 4,145) 2,661 690 / 662 none
    nepotism, D3 (withheld) 1,521 1,046 n/a none
    greed, D3 (withheld) 1,786 1,153 n/a none
    bestiality, D3 (abstained) 1,386 1,062 n/a none

    At 375 the selection itself is shorter than D0's article, and the lead now starts on the first screen. The extra height is "Related words" as today's way out (D1 row 18): 1,032 px on love, which today sits only on the source-records view. D6 repeats these numbers with #111's method.

    Tests (private partition _ux2): the web suite, whole_entry_test.exs and demo_inert_test.exs, 664 tests, are green after the updates. Forty-three existing tests had asserted the old reference_article ids, labels or nav, and each was updated to the new page's element for the same fact:

    • #curated-state replaces "#curated-empty";
    • #record-inventory-link replaces the rail cards' /materials links;
    • "About this choice" replaces "Why this is here";
    • -reason replaces a note's text inside the disclosure;
    • #curated-withheld-N and the #opening wrapper are kept.

    New tests:

    • opening_article_test.exs (6): nepotism version 5's shape, every item renders with its reason and exactly one disclosure (9 in all); document order lead → news → definitions → quotations → culture; the cut mark at 100; the headline's as-of line; no empty section; no AI mark or cut mark on a person's note.
    • curated_article_live_test.exs (6): one document order, masthead to version; every published item; each state (withheld as a whole, abstained, never assessed); and no desktop-only or phone-only content, meaning no breakpoint hidden/sr-only and no hidden paired with a breakpoint display anywhere in #curated-page.

    The full precommit has not run yet. It needs the 4017 server stopped, so it waits until the owner has looked at the running page.

    Open points for the owner's audit, each a choice I made and can change:

    1. The holdings sentence uses the mock's wording, the one the D2b readers saw: "This page holds entries from 4 dictionaries, 43 senses, their quotations, and what discovery found for love. The editor chose 5." D1 row 17c reads "This page holds {n} records." Say which.
    2. Related words is today's whole way-out block (all groups and the source stack). The mock showed eight chips. A short list with "All related words →" would take about 900 px off love at 375.
    3. The switch labels on /materials still read "Curated article / Source records", because /materials stays unchanged. The two views of one page therefore name the switch differently.
    4. Not built: D1 row 22 ("refused"), because curation_refresh_states.last_outcome has no refused value, so there is no data path to it. Row 10b (an expired headline), which today is listed under "Withheld:" in the editor's take with "the selected observation's retention window has expired" rather than in the news section.

    Next: D4 and D5 (states, accessibility, a device check) on this server, then D6 measurements, including the owner's own three D2b answers and the two subagent readers repeated on the built page. Then the PR with an independent exact-head review and a full precommit.

  13. added 3 commits that reference this issue on Nov 5, 2026
  14. holden commented on Nov 5, 2026

    @holden
    MemberAuthor

    D4–D6 on the built page, 5 November 2026: states, accessibility, measurements and the readers

    Head 6ddd106 on claude/309-curated-page (code at 8b469e6; since D3: b1b25c2 short related words and one switch, 8b469e6 tap targets and contrast). Served at localhost:4017 (pid 887). Today's page is served for comparison by a throwaway baseline worktree at main decb956 on localhost:4018 (pid 98359). Both read the same private copy devils_dictionary_test_ux1. Nothing reached 4007 or the public host.

    The audit session's recommended defaults, applied (each default, owner may override; recorded in the D1 table c6637566629 and marked):

    1. Holdings sentence: the mock's wording, the one the D2b readers passed. D1 row 17c is amended to it.
    2. Related words: the first eight chips, then "All related words →" to /materials#related. The full way out, with the source stack, stays on /materials.
    3. One switch for one page: /on/:slug/materials also reads "This editor's selection · Everything this page holds". It is a label change only; /words keeps its own labels.
    4. Not built: row 22 (refused), because there is no data path (last_outcome has no refused value). Row 10b (an expired headline in the news section's place), because the withheld entry carries only retention_expired, not the item's kind. It stays on the row 17d line.

    D4, states, each served and screenshotted (D3, c6647027467) and each with a LiveView test:

    • published: love, war;
    • withheld as a whole: nepotism, greed, with the reason clause and the last assessment under the current configuration, its stored reason and the cut mark;
    • abstained: bestiality, with who, when and the stored reason;
    • never assessed: a test only; no page in the copy is in this state;
    • a withheld item: in the editor's take, "Withheld: … Nothing was put in its place.", tested;
    • a withheld lead: in the lead's own place, tested.

    D5, accessibility, at 375 px on 4017:

    D6, measured (CSS px, <main>, every disclosure closed, the same method on both servers):

    Page, width <main> today → built Lead starts today → built Disclosures Horizontal scroll
    love, 375 4,301 → 4,526 793 → 706 (first screen) 14 → 7 none → none
    love, 1280 1,985 → 2,701 552 → 662 14 → 7 none → none
    war, 375 4,220 → 4,726 793 → 706 14 → 7 none → none
    war, 1280 2,353 → 2,745 552 → 634 14 → 7 none → none
    nepotism, 375 (withheld) 1,354 → 1,346 n/a 3 → 1 none → none
    greed, 375 (withheld) 1,395 → 1,395 n/a 1 → 0 none → none
    bestiality, 375 (abstained) 1,427 → 1,207 n/a 3 → 1 none → none

    At 375 the page is about 5% taller, because every reason is now on the page and not inside two disclosures per item. The lead moves onto the first screen, and the disclosures halve. At 1280 the masthead is taller (the byline sits above the lead) and the reasons are visible, so the lead starts 110 px lower. DOMContentLoaded is the same on both servers (love 176 / 181 ms).

    D2b on the built page: the two subagent readers, repeated. Two new subagents, reader E (Sonnet) and reader F (Haiku), got only the nine 375 px screens of the built /on/love at 6ddd106 (1 2 3 4 5 6 7 8 9 ) and the same prompt. Both answered 3 of 3:

    1. An AI editor inspired by Voltaire, not reviewed by a person (screen 1; screen 5 or 6 repeats the lens disclosure).
    2. The stored reason under "Why it leads" (screen 2).
    3. "Everything this page holds": the switch's second half and the link after the editor's section. Both said the footer's Sources list names providers, not records.

    What slowed them:

    Still open:

    • The owner's own three D2b answers, on the built page at localhost:4017/on/love.
    • The device check.
    • The full precommit. It needs 4017 stopped, which waits for the owner's word that they have finished looking.
    • The independent exact-head review. It is running now on 6ddd106.
    • The PR.
  15. added 6 commits that reference this issue on Nov 5, 2026
  16. holden commented on Nov 5, 2026

    @holden
    MemberAuthor

    D4/D5: tap targets in landscape, 5 Nov 2026

    The owner asked for this before the merge: every interactive element on /on/:slug is at least 44 px tall at 640 px and wider too, not only in portrait.

    Done on PR #315. The candidate final head is f952b48.

    • 8377c1b: the four targets review 4 named no longer shrink at 640 px and wider.
    • 00f47f1 and f952b48 fix what reviews 5 and 6 found besides:
      • the attribution line, the exact revisions and the headword's other words;
      • the byline link.
    • On the article, links that run in a line are 44 px boxes. Each required credit then takes a line of its own, and a long credit still wraps inside the column.

    Measured on the private copy (4017), with every disclosure open, on the nine curated pages and one with no selection, at 375, 640, 667, 812, 932 and 1280 px:

    • no a, summary or button in #curated-page is under 44 px;
    • nothing overflows.

    Reviews: reviews 5 and 6 each found one REQUIRED item, both fixed (c6651520815, c6651830040). Review 7 of f952b48 found nothing REQUIRED (c6652074215).

    Tests: test/devils_dictionary_web and test/devils_dictionary/curation, 1,367 tests, 0 failures.

    Not covered:

    • the site's shared header and footer, and the provenance drawer: outside this change;
    • a real iPhone: the simulator is not counted as the device check, so that check is the owner's, on the demo tunnel.
  17. added a commit that references this issue on Nov 6, 2026
  18. holden commented on Nov 6, 2026

    @holden
    MemberAuthor

    6 Nov 2026, 18:45 UTC: the owner's desktop audit, done in 8f2c901 (#315, now the PR head)

    The owner viewed the demo on a desktop about 2000 px wide and asked for two changes (relayed by the audit session at about 00:10 UTC): the view switch changed when tapped, and the page used too little of a wide screen.

    What changed:

    • One switch. CuratedArticle.view_switch/1 is drawn once above every view of an entry, in the same place. On /on/love and /on/love/materials it is the same box at every size and in both themes: 327×64 at 375 px, and 411.8×52 from 640 px. A tap changes only which half is filled, and both halves have one weight. /words uses the same control with its own labels.
    • Two columns from the masthead from 1024 px. The byline heads the right column, level with "On {word}", above the editor. Below 1024 px the document order is unchanged.
    • Wider from 1280 px. The curated article and its materials are 88rem (1,408 px) wide, and the account bar, navbar and footer widen with them. /words, ?layout=current, / and /artworks keep 1,280 px.
      • On love at 1920 px the lead starts at 529 px, where it was 709 at f952b48.
      • The grid's left column, gap and right column: 544 | 48 | 352 px at 1024, 736 | 80 | 384 at 1280, and 864 | 80 | 384 from 1440.
    • A page with no selection keeps its text at 44rem, as the article's prose is.

    Checks at 8f2c901:

    • Tap targets and overflow. Nothing under 44 px (the switch included) and nothing scrolls sideways, in 108 of 108 checks:
      • the nine curated pages, dog, and two /materials views;
      • at 375, 640, 667, 812, 932, 1024, 1280, 1440 and 1920 px, every disclosure open.
    • Independent exact-head review: nothing REQUIRED, with seven RECOMMENDED items as follow-ups (c6692387649). The reviewer measured 1,680 targets over 8 pages × 6 sizes × both themes, with live navigation by real clicks.
    • Full precommit: in _ux2, 19 doctests and 3,435 tests, 0 failures (18:32:05–18:39:58 UTC).
    • The demo behind the owner's tunnel serves 8f2c901 again, and LiveView connects through it.

    Not done:

    • A check on a real iPhone in iOS Safari. It is recorded as not done, not as a gate, per the owner's order of work.
    • The owner's own D2b answers.

    Next: the merge and the fast-forward deploy, each on the owner's own words.

  19. added a commit that references this issue on Nov 6, 2026
  20. holden commented on Nov 6, 2026

    @holden
    MemberAuthor

    Merge and deploy of PR #315, 6 November 2026, 18:42–18:43 UTC (audit session, on the owner's words)

    Owner's words, typed in the audit session's chat at ~17:38 UTC: "Yes deploy the merge and deploy then we will tidy up." The merge waited for the one-switch and width fix the owner asked for at ~00:10 UTC, which became the PR's final head.

    Gates at the final head, verified read-only before the merge:

    Merge, 18:42:27 UTC: merge commit b87f51b3e5d48a9a2388d3d56fd07e5c66fee506, parents decb956 (main) and 8f2c901 (the reviewed head); git diff 8f2c901 b87f51b is empty, so the merged tree is the reviewed tree.

    Deploy, 18:43:12 UTC, by fast-forward of the serving checkout (cbedce0 → b87f51b, 120 files: #314's docs and #315; 0 config, mix.lock or migration changes; checkout clean before and after; no restart):

    • First request GET / 200 at 18:43:13 UTC (1.8 s); GET /health 302; listener pid 1661 unchanged.
    • Recompiled by the running server into _build/published/dev at 18:43:13 UTC: CuratedArticle, WordLive, Kit, Layouts.
    • Stylesheet rebuilt by the running Tailwind watcher at 18:43:13 UTC: priv/static/assets/css/app.css carries the wide-page variant and the 88 rem rule.
    • Public host root GET / 200. No /on/* or /define/* page was opened on 4007 or the public host.

    Recorded as not done: the real-iPhone iOS Safari check (not a gate for this merge, on the owner's words); the owner's three D2b comprehension answers remain open.

    Not touched, waiting for the owner's yes by exact name after this deploy: demo servers 4017 and 4018, the second ngrok agent, worktrees 309-curated-page and 309-baseline, branch claude/309-curated-page, scratch databases devils_dictionary_test_ux1, _ux2, _rv309, _rv309b, and private/309-demo/.

  21. holden commented on Nov 6, 2026

    @holden
    MemberAuthor

    Tidy-up after the deploy, 6 November 2026, 23:09–23:11 UTC (audit session, on the owner's words "Yes, all of it" to the exact list)

    • Stopped: demo servers 4017 (pid 13452) and 4018 (pid 98359), the second ngrok agent (pid 26239) and the headless Chrome used for the measurements.
    • Removed: worktrees 309-curated-page and 309-baseline; branch claude/309-curated-page (merged as b87f51b) deleted locally and on origin.
    • Dropped: devils_dictionary_test_ux1 (9.7 GB), _ux2, _rv309, _rv309b, each with zero connections.
    • Deleted: private/309-demo/ (2.1 GB).
    • Untouched and re-verified: 4007 (pid 1661, / 200, /health 302), the public ngrok agent, devils_dictionary_v2 (14 GB, max attempt 241), the serving checkout (b87f51b, clean).

    Open on this issue: the owner's three D2b comprehension answers; the real-iPhone check (recorded as not done); the review's seven RECOMMENDED follow-ups, R2 first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions