Skip to content

Curated opening section: Bierce-first lead, sourced highlights and inspectable editorial choices #156

Closed as not planned

Description

@holden

Current implementation brief — 26 September 2026

UI delivery child of #193. Phase 0 sketches merged in #159; Phase 1 manual-fixture implementation is now in draft PR #202 (not a shipped public panel). Phases 2–3 remain pending. This issue now owns implementing the editorial opening section, first with manually selected eligible data, then the same component reads approved saved compositions from #196. It does not require a running model or #101's broad assessor.

Configuration compatibility note (#201; narrow integration only)

Continue the existing default-only UI scope; domain/personal panel pickers, accounts and multiple public views are not prerequisites. When #196 persistence connects, carry curation_configuration_id, resolved configuration-version ID and resolution reason/policy version alongside composition/version and actual profile provenance in the view model. The server resolves only the system global-default in MVP; the component must not infer a panel from URL spelling/namespace or accept an arbitrary configuration query parameter. Existing manual fixtures can use explicit default metadata without waiting for domain/personal features.

The five existing deceased-person-inspired profiles remain the default everywhere curation is enabled. Inspect actual selectors and concise reasons through the existing transparency disclosure; this is provenance, not a configuration chooser. Bierce-first belongs to the default's versioned editorial policy; mandatory source/rights/claim gates remain invariant. #194 owns one active default page binding, leaving future configuration alternatives possible without changing the current layout or routes. No implementation/ADR files are changed by this planning note.

History/method integration (#203/#204; preserve Phase 1 scope)

Draft PR #202 already supplies Opening/OpeningReader and a “How this was chosen” disclosure for development-only manual fixtures. Keep its honest “no model or persona panel took part / none recorded” states; do not manufacture history or add runtime/persistence to finish Phase 1. When approved persistence connects, provide links/identities for How this was curated, exact version/diff, actual profile-version pages and Editorial method, through destinations coordinated with #194 rather than a new namespace.

#203 owns the history/profile reader, equal-weight counts and reproducible ordering, including recommendation-versus-human-override display. #204 owns the sourced method essay and release-accurate implemented/planned status. This component consumes access-filtered summaries only; private failed/adverse nominations, raw prompts, hidden model reasoning and restricted source text do not become public in a disclosure. Keep source quotations and reported generated reasons visually distinct. This is a Phase 2/3 integration seam, not a domain/personal chooser or retrospective claim that fixture notes were human-approved.

Output contract

Above the existing Definitions/examples/discovery content, show a colorful, readable editorial section with:

  1. Sourced lead definition: applicable The Devil's Dictionary entry by Ambrose Bierce first, an explicit editorial priority that personas cannot override. Use exact source text/edition attribution and a link to its complete entry. Clip only at a valid textual boundary with a clear continuation affordance; never generate a “Bierce” line. Where no applicable entry exists, a human may select another eligible sourced definition or leave the lead empty; final automatic fallback order remains open.
  2. Zero to three highlights: eligible existing image/artwork, quotation, poem/passage or other supported item. Prefer useful variety, but do not require exactly three kinds, all social tiers or filler. Every selection carries an intended meaning; the composition may span the page's meanings. Highlighting a source is presentation, not an implicit illustrates assertion.
  3. Concise reasons and transparency: exact source/creator/edition/locator/rights credits, source match reason when relevant, and separately labelled human or generated editorial explanation (“Selected by …-inspired AI; reviewed by …”). A disclosure exposes permitted support/objection summaries, actual panel/profile/model versions, selection/review dates and evidence. Never present a panel vote as evidence, a generated note as a historical quotation, or a pending sensitive nomination as public dissent.

Recommended default layout: the existing band-in-main-column sketch, above Definitions; mobile places it directly after the headword. Final visual treatment among #159 variants remains selectable. At 375px, stack or adapt tiles for legible text/credits rather than forcing three cramped squares or promising everything fits one screen. At desktop, use the available column with balanced imagery and typography. Respect keyboard access, heading order, reduced motion, dark mode and source-mark requirements.

Data interface and phases

Phase 1 — manual contract/rendering: a typed view model contains composition_id/version when available, lead (durable object + exact source/sense revision + allowed text excerpt), highlights[] (role/position, durable item and exact revision/locator, intended meaning, credits/rights, source reason, attributed editorial reason, optional accepted assertion revision), and permitted review/dissent summary. Use explicitly reviewed fixtures/manual selections for this phase; don't invent model judgments. An optional recordless fixture adapter is fine for development, but production selection is the saved version in #196. No new provider or network call in this component.

Phase 2 — approved persistence: read #196's current eligible published version with the same view-model contract. Display-only selection does not require #189 votes or a new claim. If an item relies on illustrates, use the independently accepted current claim revision under #190. Persistent selections cannot point only to disposable discovery result IDs.

Phase 3 — visit refresh/transparency: connect #198 admission without blocking the reader. Pin ordinary reads to the initially displayed approved version; expose a refresh affordance/next-navigation update when a new version is published. No daily hash rotation, per-load random selection or arrival-order reshuffling. Withdrawal/rights expiry removes invalid content immediately; no automatic replacement that changes the approved arrangement.

Existing Definitions rows, opening behavior, source text, IDs, examples and discovery shelves remain intact. Source eligibility, credits, links and retention rules apply on the new surface too. Link to exact evidence/entry or existing shelf item where available; don't require a stale shelf result to exist in order to inspect a durable citation. The component consumes content-type/rights data, not provider-name branches (Bierce priority belongs in explicit lead-selection policy).

Corrections to the historical sketch proposal

Acceptance

  • love shows its applicable Bierce lead plus up to three actually available and eligible manually sourced highlights; no quoted fixture content is invented to match a sketch.
  • A no-Bierce case uses a manually selected sourced fallback or no lead; sparse/empty cases render no filler, no permanent loading skeleton and no empty three-slot promise.
  • Existing definitions and discovery content/behavior remain intact; this adds a first section without rewriting source content.
  • At 375 and 1280 in light/dark modes, credits/reasons are readable, controls keyboard-accessible and no horizontal page overflow occurs. Record page-height cost under 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.
  • Exact source text versus generated reasons are visibly distinct; applicable badges/marks/licenses survive the new surface; a disclosure shows lawful dissent and approval.
  • Approved saved composition renders with inference offline; pending/rejected/expired items are absent, and ordinary refresh never reshuffles an open page.
  • Run mix precommit and focused component/LiveView tests when implemented.

Open product choices: final sketch treatment; automatic lead fallback if no Bierce; inclusion policy for query-only/transient items. MVP can proceed with the defaults above: manual eligible fallback, durable verified highlights, no forced tier slots.

Historical design/sketch brief (preserved; superseded where it conflicts with the current implementation brief)

Design only. No code changes are asked for by this issue; it ends in a phased plan whose first phase is static sketches, the way #131 Phase 1 worked.

Purpose

The cards are right and stay as they are. What the page lacks is an entry: the first screen of /define/love is a headword, a stats tile, and a Definitions slab whose open row is WordNet's any object of warm affection or devotion. Bierce, the page's reason to exist, is a closed row with a + on it. The first picture is a screen and a half down on a desktop and further on a phone. Seventy-eight things from twelve sources are on the page, and the reader is asked to go and find them.

An encyclopedia entry does the opposite. It opens with one strong voice and a few well-chosen things, and then offers the apparatus. This issue proposes a band between the headword and the Definitions slab — call it the entry for now — that leads with the Devil's Dictionary where Bierce wrote one, and shows two or three things picked from the shelves the page already fetched: a picture, a line of verse, a track, a GIF. Nothing new is fetched, nothing is stored, nothing is rewritten. The band is a read-time composition over what the page already holds, chosen by codified rules that stand in for curation until curation exists (#96, #105, #97) and go away when it does.

Measured against main @ 6cb1ffa, the screenshots in docs/discovery/issue-144-phase3-* and issue-131-phase2-*, and the code cited below.

What the reader sees today, and why

The open row is WordNet by rule, and the rule is right. WordLive.default_open/1 opens the first non-aristocracy card, citing McCreary 2008: a dictionary that opens on its oldest source scores 3.96 against a sense-ordered dictionary's 7.04, and whatever is open is what gets read (#131, docs/discovery/issue-131-how-others-do-it.md). This issue does not reopen that. The definitions slab is a reference tool, and it should open on the reference.

But Bierce is not a reference; he is a quotation. His love entry is 484 characters, his nepotism entry is 77 (Appointing your grandmother to office for the good of the party.), and his logomachy is 385 including a quatrain. These are epigraphs. Filing them among the dictionaries and closing them is the one place the page treats an aristocracy source as if it were a middle-class one. The way to give Bierce the marquee without breaking the open-row rule is to give him a different slot: the lead of the entry band, quoted, above the slab, with his card in the slab untouched.

The world is below the fold by design and stays there. Culture.section/1 renders Out in the world after the definitions, one shelf per content type in the table's order (film · artwork · image · gif · text · news · music), search-only shelves demoted last (#126 D1). On love that is 78 items in six rails. The shelves are a good apparatus. They are not a good first look: every item is the same size, the reader has to scroll to learn there is a painting of Romeo and Juliet, a 1916 poem that uses the word, and four Spotify tracks called Love.

The pieces of an entry already exist as data on the page at render time. In WordPage: headword (lemma, pronunciations, forms, up to two etymologies on screen since #133 R5), cards with opening (a deterministic 220-character excerpt of the original, never a summary), related, and thing (concept, Wikidata description, image, chain, examples, Wikipedia lead). In WordLive: @cultures, one state per provider with status, tier, items, each item carrying preview_metadata (title, artist/author, image_url/thumbnail_url, source_url), match_details (evidence ∈ identity · attestation · query, and for PoetryDB the matched line itself, "lines" => [%{"number", "text"}]), and the licence fields the row requires. The band needs no new field.

Vocabulary

  • The entry — the band. The headword is its heading; it has none of its own.
  • The lead — one quoted voice at the top of the band. One source, one entry, whole or clipped at a clause with a link to the card.
  • A tile — one item from a shelf, shown at the band's size with its badge, its credit, and its one-sentence reason, linking down to its card on its shelf, not out.
  • A composition — %{lead: ref | nil, tiles: [ref]}, the thing the band renders. Today a rule produces it; later a curator's saved choice does. Same shape, same component.

The proposal

Layout

The band lives in the column beside the rail, above the Definitions slab. The rail stays what #131 Phase 2 made it (what the page knows the size of); the band is what a source decides the size of, which is the column's job. On a phone the band must read directly after the headword and before Sound, forms and origin and the source list, which is a grid-row placement like the one the related words already use, not a second copy.

Desktop, 1280. love.

wordhoard                                                                    ⌂ ☼ ☾
───────────────────────────────────────────────────────────────────────────────────
love                       ┃  ┌─────────────────────────────────────────────────┐
[ˈlɐv] [ˈlʌv] /ˈlʌv/ +9    ┃  │ 👑 Ambrose Bierce · The Devil's Dictionary, 1911 │
noun · verb · name         ┃  │                                                 │
strong, positive emotion   ┃  │  “A temporary insanity curable by marriage or   │
based on affection  Wikidata┃  │   by removal of the patient from the           │
                           ┃  │   influences under which he incurred the        │
┌──────┐ ┌──────┐          ┃  │   disorder.”                  Read the entry ↓  │
│  5   │ │  43  │          ┃  └─────────────────────────────────────────────────┘
│source│ │senses│          ┃
└──────┘ └──────┘          ┃  ┌───────────────┐ ┌───────────────┐ ┌───────────────┐
                           ┃  │ [painting]    │ │  ❝ Where love │ │ [gif, still]  │
Sound, forms and origin    ┃  │               │ │  throbs out   │ │               │
 from Middle English love, │ ┃  │               │ │  in blissful  │ │               │
 from Old English lufu …   ┃  │               │ │  sleep ❞      │ │               │
                           ┃  ├───────────────┤ ├───────────────┤ ├───────────────┤
Defined here by 5 sources  ┃  │📚 Cupid and   │ │📚 I Have a    │ │📱 Happy In    │
👑 Samuel Johnson noun·verb┃  │  Psyche, 1798 │ │  Rendezvous   │ │  Love GIF     │
👑 Ambrose Bierce     noun ┃  │  Gérard       │ │  With Death   │ │  GIPHY · Play │
📚 Open English WordNet    ┃  │  Catalog match│ │  Alan Seeger  │ │  Search match │
📚 Wiktionary (English)    ┃  │  on identity  │ │  at a line    │ │  for “love”   │
📚 Wikipedia         article┃  └───────────────┘ └───────────────┘ └───────────────┘
                           ┃   Artworks ↓          Texts ↓             GIFs ↓  [Powered by GIPHY]
───────────────────────────┃
Related words              ┃  Definitions                5 sources · 9 entries · one open
 similar  adore · cherish… ┃  ─────────────────────────────────────────────────────
 opposite hate · despise   ┃  👑 Samuel Johnson · 1755 · noun                    +
 …                         ┃  👑 Ambrose Bierce · 1911 · noun                    +
                           ┃  📚 Open English WordNet 2025 · noun · 6 senses     −
                           ┃     • any object of warm affection or devotion …

Phone, 375. The three tiles are a 3-up grid of squares, not a scrolling rail: everything in the band is visible, and horizontal scroll stays the shelves' gesture.

love
[ˈlɐv] [ˈlʌv] +9
noun · verb · name
strong, positive emotion based
on affection · Wikidata

┌────────────────────────────┐
│ 👑 Ambrose Bierce · 1911   │
│ “A temporary insanity      │
│  curable by marriage or by │
│  removal of the patient    │
│  from the influences under │
│  which he incurred the     │
│  disorder.”                │
│              Read the entry ↓
└────────────────────────────┘
┌────────┐┌────────┐┌────────┐
│[paint] ││❝Where  ││[gif]   │
│        ││love    ││        │
│        ││throbs… ││        │
├────────┤├────────┤├────────┤
│📚 Cupid ││📚 Seeger││📱 Happy│
│& Psyche││at a line││In Love │
└────────┘└────────┘└────────┘
 Artworks ↓ Texts ↓  GIFs ↓ [GIPHY]

5 sources · 43 senses
Sound, forms and origin …
Defined here by 5 sources …
Definitions …

The lead: one voice, by a ladder

The lead is filled by the first rung that has something, and the band never invents a rung:

Rung Source What is quoted When it applies
1 👑 Bierce The whole entry if it fits the closed budget (proposal: 320 characters, which takes nepotism, logomachy without its quatrain, and love clipped at the first full stop); otherwise the first sentence and Read the entry ↓ to #card-bierce Every word Bierce defined: love, war, nepotism, logomachy, dictionary
2 👑 Johnson Sense 1's first sentence, never the whole 4,746-character love noun Words Bierce did not define but Johnson did
3 📱 Urban Dictionary The one browser-fetched definition, once it arrives Words neither dead man met: rizz. Arrives after first paint, so the slot is empty until then and the band must not jump when it fills
4 the thing Wikidata's description — already the rail's quick definition, so the band repeats nothing and the rung means no lead —

Rung 3 is the owner's randomised to an Urban Dictionary suggestion made deterministic: there is only one Urban Dictionary entry per page (#136), so there is nothing to randomise. Rung 4 is listed to say the band does not lead with WordNet: a WordNet gloss above a WordNet card is the same text twice.

The lead is a quotation of the original, styled as one: large serif, quotation marks, the source's badge and year as the caption, tier colour as the rail uses it. It is not a card and has no +. Its text comes from card.opening extended to a sentence boundary, which is the one change WordPage.build/2 may need (a lead: beside opening:, decided in the query module as #71 §8a.4 asks, never in the template).

The tiles: three kinds, never two of one

Variety is the rule the owner asked for, and it is codified as one tile per kind, kinds in a fixed preference, at most three:

Kind Draws from Prefers The tile shows
a picture Artworks, Images, Films, GIFs identity evidence over attestation over query; then tier 👑 · 📚 · 📱; then the shelf's own first position the image, the type badge, the credit the row requires, the reason
a line Texts (PoetryDB's matched line; Open Library's snippet), News (the headline) attestation with a line locator first, because the matched line is the word in use; a headline second the quoted line or headline, title, author, the locator the reason already names
a thing the thing panel (concept image + description); later an exemplar (#105) — the concept's image and its Wikidata description
a sound Music identity (a P921 song, once #116's follow-up lands) over query cover art, title, artist, the Spotify mark on the band

Preference across kinds when more than three are available: picture · line · thing · sound, so a word with everything gets a painting, a poem and Romeo and Juliet, and the track goes fourth. That is a starting order for the sketches to test, not a finding — the owner may want the sound above the thing.

Within a kind, rotation. When the shelf holds several candidates that tie on evidence and tier — the four Spotify tracks called Love, the twelve GIFs — the pick is rem(hash(lemma <> date), n): stable for a day, different tomorrow. The owner asked for somewhat random; a pick that changes on every reload is a page that cannot be screenshotted, and one that never changes is a page that never rewards a return. A day is the compromise. It is also the one thing here that is not pure read-time composition (it reads the clock), and the sketch phase should check that a test can pin the date.

Search results are last and labelled, never hidden. Promise 1 of docs/discovery/README.md: a :query item is admitted only where its row admits it, and it says so. A tile's reason sentence is the item's MatchReason, so a Pexels photograph in the band reads Search result for “love”, ranked by the provider and not matched on an identifier. The question the owner owes is whether a :query-only picture may fill the picture slot at all when nothing better exists (on logomachy, Commons, Openverse and Unsplash are empty and Pexels has eleven photographs). The proposal is yes for GIFs, no for stock photographs: the owner named GIFs as a thing the entry should show, and GIFs are a search by construction; a stock photograph of nothing in particular under a Bierce epigraph is the page misnaming what it shows, which is what #116 D2's caveat exists to prevent.

Diversity across tiers, not only kinds

Variety across kinds is not enough. The page's argument (#66, the 2026-09-21 audit) is the descent through the classes — 👑 the dead, 📚 the institutions, 📱 the crowd — and a band that picks the best-tiered item in every slot would show the reader the aristocracy and the middle class every time and the plebs never. So the band has a second rule, applied after the kind rule and before rotation:

The band spans every tier the page has. The lead is the 👑 voice (rungs 1 and 2), or the 📱 voice when the word is younger than both dead men (rung 3). Among the tiles, when the shelves hold a candidate from a tier the band does not yet show, the lowest-preference tile is swapped for the best candidate of the missing tier, whatever its kind — so love shows Bierce 👑, a painting 📚, a poem line 📚 and a GIF 📱 rather than a third 📚 tile. Every tile carries its tier glyph beside its badge, the way the rail's source list does, so the descent is visible in the band and not only true of it.

What the registry can supply today, which the rule has to be honest about:

Tier Who is in it What a tile from it looks like
👑 Bierce, Johnson — and no discovery source at all (the audit's finding; Wikiquote was rejected as the :quote source) the lead only. A 👑 tile needs a :quote or :poem corpus with a dead author, which is the next source this rule makes worth adding
📚 the Artworks catalog (Met, Wikidata, Artsy), CineGraph, Commons, PoetryDB, Open Library, Spotify, the thing (Wikidata, Wikipedia) a painting, a film, a poem line, a book snippet, a track, the concept
📱 GIPHY, Pexels, Unsplash, Openverse, Bing News, the Guardian, Urban Dictionary a GIF (:query), a headline (attestation — the crowd's tier has real evidence here), a stock photograph (:query, excluded by decision 4), or the crowd's own definition

Two consequences. First, decision 4 and this rule pull against each other on a word whose only 📱 candidates are stock photographs: the proposal stands (no photograph), and the band shows two tiers rather than three, honestly. Second, a 📱 headline outranks a 📱 GIF on evidence (attestation over query) and the rule prefers it — which is right for war and wrong for love, where a GIF is the crowd's actual vernacular. The sketch phase should show both and the owner picks whether the crowd's slot prefers the evidence or the vernacular (decision 7).

What the band owes, because it is a surface

The band is a fourth place a source's item appears (card, shelf, rail stack, band), and every obligation the shelf carries, the band carries:

  • A :required row's credit sits beneath the tile, unclamped, never on hover, linked where the item names a URL (promise 4). An Images tile is therefore taller than an Artworks tile, and the sketch has to show that.
  • A source whose mark is a condition of use shows it once on the band when one of its items is there — the Spotify mark, GIPHY's Powered by, the Guardian's — in a byline under the tiles, the way Culture.mark/1 draws it on a shelf. One mark per surface (The word page names its sources 200 times: one badge per card, one mark per shelf, one stack in the rail #152).
  • Every tile carries its reason sentence and its source badge, and links to its own card on the shelf (#culture-shelf-<type>), never out. The band previews the page; the shelf is where a reader leaves it.
  • The component knows no provider by name (promise 9). It branches on the content-type row and on evidence, both data.
  • Nothing is stored. The band is computed from @page, @cultures and @browsers at render, the way page_sources/4 composes the rail's stack.

Timing: the band fills, it does not shuffle

Shelves arrive over PubSub after first paint (handle_info({:discovery_updated, …})), and the Urban Dictionary card arrives from the reader's browser. The lead from rungs 1–2 renders on the dead render. The tiles render three reserved slots; a slot fills when the first state its kind draws from reaches :ready, and once all states have settled nothing moves. A tile that arrived is not displaced by a better one arriving later — the rule runs once per settled state, not once per message — so the reader's screen does not rearrange under them. The sketch phase should decide whether an unfilled slot after settlement collapses (the band shows two tiles) or stays as an honest gap; the proposal is collapse.

The honest cases

Word Lead Tiles Note
love Bierce 👑, clipped at the first full stop Gérard's Cupid and Psyche 📚 (Artworks catalog, identity) · Seeger's matched line 📚 (PoetryDB, attestation) · a GIF 📱 (GIPHY, search) three tiers; the thing and the Spotify track go fourth and fifth
war Bierce 👑, first sentence (1,088 chars whole) Met artwork 📚 · a poem line 📚 · a Guardian or Bing headline 📱 (attestation, dated) three tiers, and the crowd's tile has real evidence
nepotism Bierce, whole (77 chars) Open Library snippet · — no thing, no identity picture; Pexels is :query and excluded by the proposed rule; a two-tile band
logomachy Bierce, clipped before the quatrain Open Library snippet if attested; otherwise nothing possibly lead only — the band is a quotation and no tiles, which is fine
rizz Urban Dictionary 📱, after it arrives a GIF 📱 · a track 📚 the inverted band: the crowd leads, the institutions follow, no dead man spoke; empty on the dead render
topographagnosia none none no band at all. Promise 7: a word with nothing shows nothing, not a skeleton

Alternatives considered

  • O2 — the plaque. Bierce in the rail directly under the headword, tiles alone in the column. Puts the quotation beside the word it defines, which is the classic look; costs the rail its rule (a 1,088-character war entry is not a size the page knows) and puts two voices in the rail on a phone before the reader reaches anything else. Worth one sketch.
  • O3 — the hero. One large picture with the Bierce line set on it. Handsome on love; impossible on an Images tile whose credit must be visible and unclamped, and dishonest on a :query photograph. Not recommended.
  • O4 — one rotating tile. A single today's slot cycling across kinds. Simpler, less variety, and the owner asked for variety. Not recommended.
  • O5 — reorder the shelves instead. Move Out in the world above the definitions (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 the world above the fold). It puts 78 things above the reference and solves nothing about which of them matters. The band is the answer to that question; the shelves keep their order.

What this is a placeholder for

The composition shape is the interface the curation layer will fill:

%{lead: {:card, "card-bierce"} | {:browser, "urban-dictionary"} | nil,
  tiles: [{:result, id}, {:thing, object_id}, …]}

Today Entry.compose/3 (pure, like Shelf) produces it from the rules above. When #96's questions are answered — what identity a composition targets, what granularity is selectable, who edits it — a saved composition for a word replaces the rule's answer and renders through the same component. Exemplars (#105) enter as a fifth kind, a person, once an illustrates claim is selected and public. A persona editor (#97) or the assessor (#101) enters as a better rule, not a different band. The band's component, its obligations and its shape survive all three; only compose/3's body is disposable, and the issue says so in the module doc so nobody hardens it.

Schema impact

None. No table, no column, no provider file. WordPage may gain a lead: field beside opening:; WordLive gains one assign; one new component module and one pure composition module.

Phases

Phase 0 — sketches (this issue's first deliverable). Static HTML in docs/sketches/word-page/ against the app's tokens, as #131 Phase 1 did: love, nepotism, rizz and topographagnosia at 1280 and 375, light and dark, with O1 and O2 side by side. Screenshots under docs/discovery/. The owner picks. /ui first (docs/discovery/issue-131-word-page-comparison.md records what it caught last time).

Phase 1 — the lead. WordPage.build/2 decides the lead text; the band renders it above the slab with the ladder's rungs 1, 2 and 4. Measured page height at both widths against #111's budget (the band adds a screen on a phone; the issue should record what that costs).

Phase 2 — the tiles. Entry.compose/3, the three slots, the fill-without-shuffle rule, the marks, the credits, the honest empty. Conformance: a stub provider on a :required row produces a tile with its credit; a :query-only state produces none for the picture slot unless the row is :gif.

Phase 3 — rotation and the operator's view. The dated pick; a row on mix dd.discovery.status or the health page counting how many index words get a full band, a lead-only band, or none — the number that tells the owner where the next source is worth adding.

Acceptance

  • On love the first screen at 375 holds the headword, Bierce quoted, and three tiles, and nothing on it is rewritten text
  • The Definitions slab is byte-for-byte what it is today: same rows, same open row, same ids
  • Every tile carries its badge, its tier glyph, its reason sentence and its credit where owed, and links to its card on its shelf
  • On love and war the band spans all three tiers; on a word whose only 📱 candidates are stock photographs it spans two and says nothing about the third
  • A source's mark appears once on the band when its item is there, and never when it is not
  • topographagnosia has no band; nepotism has a lead and no stock photograph
  • Nothing in the band reaches the database; Entry.compose/3 is pure and tested with a pinned date
  • The composition shape is documented as the seam curation replaces

Decisions owed by the owner

  1. The band's name on screen, if it has one. The proposal is none: the headword is the heading.
  2. Layout O1 (band in the column) or O2 (the plaque in the rail), after the Phase 0 sketches.
  3. Whether Urban Dictionary may lead a word Bierce and Johnson never defined. The proposal is yes.
  4. Whether :query items may fill a tile. The proposal is GIFs yes, stock photographs no, labelled either way.
  5. Daily rotation, fixed pick, or per-load random. The proposal is daily.
  6. Kind preference when more than three are available: picture · line · thing · sound, or the sound higher.
  7. In the crowd's slot, evidence first (a dated headline over a GIF) or vernacular first (the GIF). The proposal is evidence first, with the sketches showing both.
  8. Whether a 👑 discovery source (a public-domain quotations or poetry corpus with dead authors) is worth adding because of this rule — the only way a 👑 tile, rather than only a 👑 lead, can exist.

Relationship to existing issues

Activity

  1. holden commented on Sep 22, 2026

    @holden
    MemberAuthor

    Phase 0 sketches are up: #159. Four variants on love, V1 across three days, and the three honest cases, as static HTML under docs/sketches/word-page/ (start at entry.html). First screens at 1280:

    V1 · epigraph V3 · mosaic
    V1 V3
    V2 · plaque V4 · broadsheet
    V2 V4

    Two things the sketches settled that the issue body left open, both now written into it above as proposals rather than decisions: on a phone the band sits between the headword and the facts by the app's own grid placement, and the tier rule is what makes every day's band hold 👑, 📚 and 📱. Decisions 1–8 are still yours; the PR body says which the sketches show both ways.

  2. holden commented on Sep 23, 2026

    @holden
    MemberAuthor

    Phase 0 is merged (#159, merge commit ``): four sketches on love, V1 across three days, and the three honest cases under docs/sketches/word-page/entry.html. Phases 1–3 (the lead, the tiles, rotation and the operator's count) are not started; they wait on decisions 1–8 above, which are still the owner's.

  3. added a commit that references this issue on Sep 24, 2026
  4. changed the title [-]The entry above the cards: lead with Bierce, show three things from the shelves, by codified rules that curation replaces (wireframes, no code)[/-] [+]Curated opening section: Bierce-first lead, sourced highlights and inspectable editorial choices[/+] on Sep 26, 2026
  5. holden commented on Sep 26, 2026

    @holden
    MemberAuthor

    Phase 1 evidence. Updated 27 September for PR #202 head 82d02d9, after the remediation plan. The PR is not approved and needs an independent re-audit. Phases 2 and 3 are not started, so this issue stays open.

    love at 1280

    Against the acceptance list

    • love shows its applicable Bierce lead plus up to three actually available, eligible, manually sourced highlights, and nothing is invented. The lead is Bierce's LOVE/n, labelled Satire, clipped at the first sentence with Read the whole entry · 428 characters. The highlights are Gérard's Cupid and Psyche, then Milton and Congreve, verbatim.

      • Each item is pinned by its source identity at an exact revision, and the lead also by the SHA-256 of its quoted words. The artwork is checked field by field against its committed manifest row.
      • A drifted, disabled, superseded or re-worded item is withheld and listed, never substituted.
      • Explanations use only relationships the public may see: a rejected or withdrawn refers_to gives no source-match reason.
    • No-Bierce, sparse and empty cases:

      • oats leads with Johnson, labelled Sourced definition, as a manual fallback.
      • nepotism is lead-only.
      • topographagnosia is an explicitly empty composition and draws no section.
    • Existing definitions and discovery are intact. With ?opening=fixture the Definitions slab keeps the same card ids and open row. Without the parameter, or without :curated_opening_fixtures, every page renders as on main, grid included. There are 139 existing word, culture and quote LiveView tests, all green and unchanged.

    • 375 and 1280, light and dark.

      • No horizontal overflow in all 16 word × width × theme combinations.
      • Required credits are visible and unclamped.
      • Keyboard order checked with real key presses: Tab goes headword → opening → rail → definitions at both widths, and Shift+Tab is the exact reverse. The document order is now the reading order; there is no CSS order.
      • Disclosures and the continuation work from the keyboard with a visible focus ring.
    • Page-height cost is recorded under 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, measured with the same script and database as the first capture:

      Page 1280: section · Definitions start 375: section · Definitions start
      love 1,489 → 975 · 1,702 → 1,188 (197 without an opening) 2,851 → 1,831 · 3,967 → 2,931 (1,068 without)
      oats 595 → 459 923 → 751
      nepotism 447 → 375 599 → 591
      topographagnosia none none

      Detail and provenance now sit in one named disclosure per item (Why this leads, Why this is here). The record is docs/discovery/issue-156-phase1-remediation-2026-09-27.md.

    • Source text and generated reasons are visibly distinct.

      • Source text is labelled Satire, Sourced definition or Sourced quotation.
      • Commentary is labelled Editorial preference (Bierce-first is a preference, not factual authority), Source record (registry fact) or AI-generated note (with author and not reviewed by a person).
      • The fixture label says AI-selected, not reviewed by a person.
      • How this was chosen states that no curation configuration was resolved and no panel ran, so there are no votes to show. Nothing is fabricated.
    • An approved saved composition renders with inference offline; refresh never reshuffles. This is Phase 2/3, and needs Curation persistence: versioned panels, ballots and reviewed page compositions #196/Curation configurations: global default, domain panels and future personal views #201 and Visit-driven curation refresh: coalesced jobs, fenced leases and atomic publication #198. The typed Opening.Configuration seam is in place and empty. Curation transparency: equal votes, reproducible selection, profiles and version history #203's structured decisions and history, and Editorial method: declared perspectives, checkable facts and accountable curation #204's method-page link, join the contract when they exist.

    • mix precommit passes on an isolated test database: 2,161 tests + 16 doctests, 0 failures. Nine new regression tests failed on the audited head before the fixes.

    Still open here

  6. holden commented on Sep 26, 2026

    @holden
    MemberAuthor

    PR #202 remediation plan — A+ target, subject to re-audit

    Reviewed head: 84d5ce56583fedaf0ae8f95ee7b378d630a2f2d6. Independent assessment: B− overall (engineering B−, UX/accessibility C+, future-requirement fit B+). Keep #202 draft until the bounded corrections below and fresh verification are complete. This is a remediation plan, not approval or completion of #156. A+ is a quality target, not something guaranteed by passing tests.

    Actual PR / CodeRabbit feedback

    Checked the current PR comments, submitted reviews and all review threads, including resolved/outdated state. The head is unchanged from the audit. There is one PR comment, zero submitted reviews and zero review threads; consequently there are no resolved or outdated threads to reconcile.

    CodeRabbit's only comment says “Draft PR not reviewed.” It offers a manual review trigger or a repository setting to review drafts. Disposition: deferred review action, not a code finding. Do not change repository-wide CodeRabbit settings as part of this PR or treat its successful status as a completed review. There are no CodeRabbit code suggestions to mark fixed/already addressed/not applicable. If feedback arrives during remediation, inspect it, consolidate duplicates and record each actual suggestion's disposition with evidence. Resolve discussions only when actually addressed; do not fabricate findings or resolutions.

    P2 must-fixes — narrow Phase 1 correctness/accessibility changes

    1. Pin the artwork actually displayed and enforce current source eligibility. references.ex:250–256 checks the fixture checksum against a committed manifest but then displays mutable Artworks.get/1 fields. Two isolated probes reproduced the gap: changing the artwork image URL still displays the item under the old exact-manifest reference; disabling its Wikidata catalog source also leaves it selected. Validate the actual selected row/image/credit/evidence against its pinned source, plus current display/source eligibility. A whole-file checksum alone does not prove the DB view matches it. Use existing manifest/registry evidence mechanisms; no new curation tables are needed. Withhold drift or ineligibility, report a safe reason and never silently substitute another image/provider/item. Avoid retaining a Commons credit when an alternate image source supplied the bytes. Cover exact valid data, changed image/credit/depiction data, changed manifest, disabled source, relevant withdrawal/display denial, and no substitution.
    2. Respect editorial review in source-match explanations. references.ex:205–216 bypasses Claims.visible(:public). An isolated probe rejected the fixture's refers_to relation using Claims.review/3, confirmed the ordinary public visibility check rejected it, and still obtained a Source match explanation. Apply the established public-review policy before using a relationship as evidence. Rejected/withdrawn or otherwise non-public relations must not produce explanatory text or leak withheld sensitive identities. Review analogous relationship checks in this reader, without rewriting the global claim system. An independently eligible artwork/editorial association may remain, but not a false source-supported explanation. Test accepted/imported eligible cases and rejected/withdrawn cases with no resurrection on reread.
    3. Make mobile visual and document/focus order coherent. word_live.ex:806–810 lifts the opening using CSS order while rail controls precede it in the DOM. Restructure to a coherent headword → opening → remaining rail → definitions reading sequence; use desktop grid placement for the two-column presentation. Preserve one copy of every control/ID, no-opening behavior, definitions' existing open state and existing routes. Do not repair with positive tabindex or duplicate responsive markup. Verify actual Tab/Shift-Tab and reading order, not just the presence of CSS classes, at both widths. Check source-entry continuation and disclosures with keyboard activation and visible focus.

    UI quality work — justified refinement, not an invented pixel standard

    The inspected screenshots are legible and attractive, but repeat long meaning/reason/provenance blocks. The author's measured love increase was 2,899px at 375 / 1,505px at 1280; those figures were reported, not independently remeasured in the audit. Build a compact default hierarchy: sourced lead and continuation; highlight image/quotation with creator/source and required rights attribution; clearly named accessible disclosures for explanatory detail and exact provenance. Keep necessary licence/attribution visible; never truncate source text arbitrarily, hide mandatory credits or obscure the AI/unreviewed status. Avoid redundant nested disclosures. Measure before/after section height and Definitions offset under identical conditions and explain the result; no arbitrary universal pixel ceiling. Show love, no-Bierce oats, lead-only nepotism and empty topographagnosia at 375/1280, light/dark, with no horizontal overflow. Use current V1/epigraph as the conservative baseline; no new design-choice approval is needed for routine compactness fixes.

    Reflect newer requirements without expanding Phase 1

    Acceptance evidence and execution boundaries

    The audit personally ran 54 focused tests and 2,142 tests + 16 doctests, all passing, plus compilation with warnings as errors, format checking and diff whitespace checking. The audit used non-mutating equivalents rather than the literal formatting/unlock precommit alias. Three additional temporary adversarial probes exposed the data gaps above; existing green tests do not cover them. Seven saved screenshots were inspected; an actual browser keyboard audit remains required.

    • Reproduce the data defects before fixing; meaningful regression tests fail before and pass after. Include source/revision/meaning/quotation identity, review/rights withdrawal, missing/ambiguous data and no silent substitution.
    • Disabled/absent config and absent/wrong query param remain inert; fixture toggles, navigation/reconnect and scoped noun/verb pages do not retain another page's selection. No new provider/inference calls or writes; existing definitions/discovery behavior remains intact.
    • Fresh browser evidence verifies coherent DOM/visual/focus order, accessible disclosures/continuation, no overflow, light/dark legibility and measured compactness. Store current screenshots and measurements, with viewport/theme/fixture state identified.
    • Run focused regressions then mix precommit against a dedicated isolated test DB; fix failures and report exact commands, counts and latest head. Never migrate/reset/truncate the shared development DB. Use a separate preview port with background jobs disabled; preserve running servers and the existing untracked data symlink.
    • Commit/push the bounded updates to the same PR branch, update the PR description and existing completion evidence honestly, and request re-audit against the new head. Keep Curated opening section: Bierce-first lead, sourced highlights and inspectable editorial choices #156 open and Curated opening section, Phase 1: manual fixture, Bierce-first lead, sourced highlights (#156) #202 unapproved; do not merge/deploy.

    Reuse the existing PR worktree after checking its status; preserve unrelated changes. No model download, inference service, curation migration, full history UI, domain/personal controls, new provider ingestion or automatic publication is in this remediation.

    Next: #195's measured runtime spike and #204's early About page can proceed independently. Approved persistence needs #196 + #201; #190 must precede any bot claim writes. Panel evaluation (#197), refresh (#198) and history integration (#203) follow their dependencies. The final visual choice, automatic fallback order and transient-item policy remain open; use the existing conservative defaults rather than block these fixes.

  7. added a commit that references this issue on Sep 26, 2026
  8. holden commented on Sep 26, 2026

    @holden
    MemberAuthor

    Phase 1 independent readiness audit — PR #202 at 7711e31

    Ready for an authorized merge decision; grade A− for the bounded development/test-only Phase 1. Audited head: 7711e313b4011b238910d29a4923a4f7aa17dad9. No actionable blocker remains from this audit. This supersedes the readiness assessment in my earlier remediation note, not its historical findings.

    The artwork/source eligibility, rejected-claim leakage, DOM reading order and misleading future-contract findings are fixed. The final manifest change also passes independent cold-cache probes: missing, malformed, checksum-invalid and unsupported manifests withhold artwork without raising or substituting content.

    Personally verified: 161 selected tests (including the original three independent regression probes); the full suite of 2,178 tests + 16 doctests, zero failures; compilation with warnings as errors; formatting check; and diff whitespace check. These were nonmutating audit checks, not a claim that I ran the literal mix precommit alias. CodeRabbit covers this exact head with no remaining actionable issue; all three review threads are resolved, and both reported checks pass. No UI changed in the final commit. Keyboard/height measurements remain author-provided rather than newly repeated in this audit; minor compactness/related-word polish is follow-up work.

    No merge, deployment or production-content approval was performed. Keep #156 open: the fixture remains AI-selected/unreviewed and later delivery phases remain outstanding.

    Next bounded implementation: a separate #196 + #201 persistence slice for durable system-default configuration identities/versions and manual composition → authorized human presentation review → explicit atomic publication. Manual composition must work before any model exists, with no fabricated runs, participants, model digests or human approvals. Preserve independent configuration histories and publication pointers; keep production activation gated.

    Current dependency check: routing #194 is already in flight in PR #205; coordinate with that owner and do not duplicate its page/path/schema work. #195 runtime and #204 About remain independent opportunities. #190 must precede any bot claim writes; the proposed manual foundation makes none. Recheck active work before starting, and leave the unimplemented acceptance criteria of #196/#201 open. A self-contained implementation prompt is prepared locally, but has not been dispatched.

  9. added a commit that references this issue on Sep 28, 2026
  10. holden commented on Oct 8, 2026

    @holden
    MemberAuthor

    For Phase 2 (8 October 2026): when the word page gets a reader over Curation.Published, the routing side has one deliverable waiting for it: the page–composition binding and the authored On overview (ADR 0004 §4 and Stage 4), whose table and rules are recorded in docs/routing/stage-1-foundation.md under Curation-composition binding. It is not a launch blocker and was folded out of the routing issues today (#238 closed); it is this programme's to pick up when the reader exists.

  11. holden commented on Oct 21, 2026

    @holden
    MemberAuthor

    Folded into #193, the curation programme's one open tracker, on the owner's word (21 October 2026). The specification here stands; reopen when the work starts. Status is in the consolidation comment on #193.

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