sketch-findings-genizahsearch

Stars13

Forks3

UpdatedAugust 1, 2026 at 21:04

Validated design decisions, CSS patterns, and visual direction from GenizahSearch sketch experiments — the Phase 136 discovery panel, its browse-page embedding, the evidence-highlighting algorithm, and the corpus-wide findings page. Auto-load when building discovery read surfaces or any NiceGUI browse-page UI.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

gershuni

gershuni/GenizahSearch

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Web and Digital Interface DesignersComputer and Mathematical Occupations·SOC 15-1255

File Explorer

15 files

SKILL.md

readonly

Overall Direction

The register for discovery surfaces, in the owner's words, is "an amazing feature, but caveat is needed" — explicitly neither a quiet scholarly apparatus nor an unqualified product feature, and explicitly not confidence encoded through per-tier styling. So: uniform row treatment, feature-grade presence, and the caveat given a permanent designed slot rather than buried as fine print or shouted as a warning.

The primary reader job on a manuscript page is understanding the whole manuscript, not judging one row — manuscript-level coherence is what makes a single claim judgeable. Layout follows from that: the page's identifications and the manuscript picture get equal weight.

Honesty constraints are absolute and greppable: no precision percentage, no confidence interval, no human-review badge, and none of "copy of" / "quotes" / "witness of" in display. Relation kinds are labelled with match-framing ("Direct match / Partial match / Shared text"). Coverage is shown only for the direct family and always labelled as matched-letter coverage. A negated use still violates the rule — "not proof that a folio is a copy of the work" is a violation, because a grep-based CI guard cannot see the negation.

Evidence quality is displayed as two buckets — "main pool" / "more matches" on every discovery surface (owner, 2026-08-01). The split is not a new rule: it is shared/discovery_band_labels.py::is_default_eligible(), which already exists. Frozen band labels survive as tooltips; the visible chip on a row states the relation ("Direct match / Partial match / Shared text"). Novelty is voiced "Candidates for new finds", asserting candidacy only; "New discovery" was offered and declined, because it stacks two unearned claims (that the match is correct, and that it is new) on a row with no human review until Phase 137.

There is no confidence scale. A three-level Strong/Medium/Weak scale was designed in sketch 003 and ruled system-wide on 2026-07-31, then retired on 2026-08-01 when a check against the live asset showed it was a second, disagreeing implementation of is_default_eligible(). Do not reintroduce it, and do not copy confOf() / STRONG_BANDS / LONG_CITATION out of the sketch HTML. </design_direction>

<findings_index>

Design Areas

Area	Reference	Key Decision
The main-pool rule (read first)	`references/main-pool-rule.md`	How "probably the identification" is decided: multi-folio agreement or near-full page coverage, as non-compensating floors. 56% / 44%. Includes the `density` trap, the containment residue, and the rebuild shopping list
Discovery panel layout & disclosure	`references/discovery-panel-layout.md`	Even two-pane layout (1fr/1fr ≥900px, stacks on mobile); three disclosure levels; manuscript pane NAMES the works; relation + tier filters with match-framing labels
Browse integration & evidence highlighting	`references/browse-integration-and-highlighting.md`	Entry control in browse toolbar row 2; panel full-width beneath the panes via a fifth `enrichment_refs` placeholder; highlighting needs normalized→raw offset mapping plus per-line span clipping
Corpus-wide findings page	`references/findings-page.md`	Nav label "Computed Identifications"; all three row units user-selectable (default = per identification, 65,200); two buckets from `is_default_eligible()`; novelty as a prominent switch voiced "Candidates for new finds"; domain/author/work cascade on the identified work's domain; modes not pages. Blocked on the rebuild — see below

The confidence model, settled 2026-08-01. Two buckets on both surfaces — main pool / more matches — drawn by the rule in references/main-pool-rule.md. Read that file before building either surface; it is the most load-bearing decision in this skill.

A fragment is a probable identification when it matches the work across more than one leaf, or covers almost a whole page on its own. Everything else is "more matches".

Four non-compensating gates, human_confirmed always Main → 36,152 (56%) / 28,357 (44%). Measured against 211 human grades at 0.92 main precision vs 0.88 for a naive claim-type split — design numbers only; D-06 forbids them on any surface.

Settled along with it:

The panel's tier filter is deleted, not converted. Quality is the bucket; kind is the relation filter. One filter, one toggle.
The §2 amendment shrinks to a note — band labels become tooltip-only, no new display vocabulary. §4's screening exclusion survives as gate 2; BAND-03 untouched.
The corroborated bug stops existing — the invented STRONG_BANDS was what sent the best-measured population (0.926) to the bottom level. And the split was never available: the asset's note forbids a corroborated-only or weak-only split of that measurement.

⚠ Two hard data dependencies before the surface is worth shipping: the tier_a grade (CERT-01 passed 2026-07-28 at 0.9382, but into the unshipped v2 asset — until carried over, the pool collapses to ~2,241), and a page_id → letter count table for the coverage gate.

⚠ Known residue: containment. משנה תורה, ספר אהבה ranks 7th corpus-wide — above Isaiah — because it contains the whole liturgy, and claim_type defaults to same work whenever the true host work is missing from the reference corpus (only 22 liturgy works ship). The rule cuts it 37%; 1–3% of the main pool remains misattributed, and no sidecar-computable signal fixes it.

⚠ Open at gate 1: does the panel's three-level disclosure survive? Its middle bucket ("also shares text with") is behind-the-default on quality and distinguished only by relation, which the relation chip now carries — so it arguably collapses into "more matches". D-13e locks three buckets, so this needs a decision.

Theme

sources/themes/default.css (light), parchment.css, dark.css — exact mirrors of web/static/common.css. Use them rather than inventing tokens.

Source Files

Interactive sketches are preserved in sources/. Both run offline with no build step:

sources/001-discovery-panel-architecture/index.html — 4 layout variants, 13 real manuscripts, relation/tier filters, EN+HE RTL, three themes. Winner: variant D.
sources/002-panel-embedded-in-browse/index.html — the panel inside a faithful /browse frame, with 5 service states and 4 highlight modes (including the two broken ones, so the defects are reproducible).
sources/001-discovery-panel-architecture/data.js — real data extracted from the deployed discovery-v1-33499c5b asset. Shared by sketches 001 and 002.
sources/003-discovery-findings-page/index.html — the corpus-wide page: 3 row units × 4 service states × 2 languages × 3 nav labels, plus a "pretend rebuild has landed" switch that flips novelty from what the asset can honestly show today to the intended tri-state. Its own data.js (real totals + bounded row samples) and work-domains.js / work-domains.sample.json (the 93-work domain feasibility sample).

Hard-won findings that are NOT in any requirement doc

Stored evidence offsets index the normalized Hebrew-letter stream, not the raw text. Slicing raw text at them highlights the wrong characters (652 characters off on the sampled case).
The highlight must additionally be clipped per line, because the line-number gutter splits highlight HTML on \n. Done correctly 72 of 148 grid rows highlight; done naively, 1 — silently.
Search-term highlighting and discovery spans compete for one render parameter; one renderer must emit both.
The version selector invalidates stored offsets — the highlight must be dropped on source change.
Only the largest span is stored, so a row's stated matched-letter count can exceed what is highlightable.
The manuscript-coherence reader aid is coupled to the BAND-03 screening gate — part of the codex picture sits behind a toggle built for a different purpose.
Outage must not look like a genuine zero — today's wrappers cannot tell them apart.
144,294 direct rows carry is_new = 0 meaning UNCHECKED, not "known". A two-state novelty filter over that data makes a false claim on the flagship surface. This is why D-23a's fail-closed tri-state is load-bearing rather than bookkeeping.
coverage_ppm and band_rank do not exist as columns (PRAGMA table_info), so the coverage filter is inert until the rebuild.
A band-derived confidence scale orphans 20,435 never-assessed rows (12.3%) and forces a fourth "not assessed" level. Deriving it from the relation kind avoids this — three levels, honestly.
works.genre is entirely empty, so the domain facet needs a one-time curation pass (~1,088 works, ~96% high-confidence in one pass). The work facet needs nothing; bridging discovery titles to FJMS genizah_titles matches only 5% and is not required.
A manuscript's catalogue domain is the wrong filter axis — Moss. V,374 is catalogued Court Records while carrying a correct Rashi finding, and 338 tier-A findings sit on manuscripts catalogued documentary/legal. Filtering on it hides exactly the findings that disagree with the catalogue.
PERF-01 confirmed twice — the deduped identification count alone took 16 s. A visible real total is not free.
tier_a is 81% of the corpus and carries no measured precision in the deployed asset, so the D-18 gate hides it. The grade exists (CERT-01, 0.9382) but only in the unshipped v2 asset. Any UI that assumes the top pool is populated is describing 2,241 identifications, not 46,644.
corroborated at 0.926 is the highest measured precision in the system — higher than high_confidence_algorithmic's 0.889 — and the measurement covers corroborated ∪ weak jointly; the asset's own note forbids splitting it. Any rule that treats those two bands differently contradicts the frozen contract.
Counting per page inflates same-work matches ~2.3× (88.4% → 77.8% deduped), because a fragment that copies a work matches on every folio while a citation matches once. Bounded, because a Genizah "manuscript" here is a fragment — median 2 pages, 86.5% at one or two, max 427.
The 11,941 shared-wording claims have no matched_letters value at all. A row layout promising "N matched letters" has nothing to show on them.
not_evaluated is labelled "Shared text" but 5,604 of its claims are direct_witness. A UI section built on that band name will contain same-work claims.
density is Levenshtein edit-distance, not coverage — and the repo carries a scar from that exact confusion ("demoted ~100% of witnesses"). Real coverage is computed at bake and discarded.
claim_type is assigned by within-page span dominance (scripts/discovery_ids.py:336-382), so it defaults to direct_witness whenever the true host work is absent from the reference corpus. That is why liturgy is attributed to Rambam — a corpus-coverage problem wearing a classification problem's clothes.
Multi-folio agreement is the strongest free signal in the asset: 1 page → 72% good, 2 pages → 96%, ≥3 → 91% (n=211 human grades).
Competition/exclusivity is nearly useless as a distinctiveness proxy — only 6.7% of same-work rows have any overlapping competitor, because the reference corpus lacks the competing works.
The matcher already knows where in the work a match falls and throws it away at ingest — 3,800-char windows with tracked offsets, positions deliberately preserved. Persisting it is the single highest-leverage change available: it makes citations locatable, which is what makes them worth anything to a scholar.
Sefaria verse maps already exist — 322 *.versemap.json sidecars in refs_staging/, verse-level with character offsets, because the fetcher deliberately kept labels out of the body. But they index the body while the matcher indexes norm_stream — two coordinate systems, the same trap sketch 002 found on the manuscript side. Name the coordinate space of every offset at the point of definition; treat that as a schema rule, not two coincidences.
Only 42% of works can ever show a reference (451 Sefaria of 1,088) even though 75% of claims can — Sefaria works carry far more claims each, so design for the row, not the corpus. Three display tiers, two load-bearing on day one: full reference (Sefaria) · approximate position (JA) · omitted (M-source).
JA and M-source lack a locus for opposite reasons. JA has no data (no divisions exist) but is public — displayed, with an approximate position, and improvable later. M-source is a disclosure limit — not a data problem, so it never improves. Don't collapse them into one "degraded" case.
Rendering reference text is licence-gated PER WORK, not per corpus. SC-3's absolute ban was lifted 2026-08-02, but the gate is the acquisition manifest's existing reuse_ok: yes 277 (PD 264 · CC-BY 11 · CC0 1 · CC-BY-SA 1) · unclear 46 · noncommercial_only 1 · absent 21 = every JA work. So ~17% of Sefaria works are not clearly reusable, and JA text cannot render at all today despite being public — a licensing question entirely separate from its missing divisions. Fail closed on a missing flag; carry attribution_text for CC-BY/CC-BY-SA. And the staged bodies are lossy (nikud, punctuation and rubrics stripped at acquisition) — decide whether that is the comparison view or whether display text is re-fetched.

Requirement amendments these sketches owe

Item	Change	Status
D-09	Strike "collapsed" (variant D never collapses the manuscript group); keep the left-to-right ordering	narrow amendment owed
D-12	Offsets index the normalized letter stream; result must be clipped per line; highlight dropped on version change; search-term precedence rule	rewrite owed
`discovery-band-labels-v1.md` §2	Band labels become tooltip-only; the visible split is §4's default-shown boundary, which §4 already defines. No new display vocabulary, so a note rather than a contract rewrite. §3, §4 and BAND-03 all unaffected	small amendment owed
Panel tier filter	Deleted, not converted — quality is the bucket, kind is the relation filter	resolved 2026-08-01
`band_precision.tier_a`	Carry the CERT-01 result (`measured_pass` + real `ci_low`) into the v2 bake	data fix, blocks the surface
`page_norm_letters`	A `page_id → letter count` table (~139K ints, no text, masking-safe) so the coverage gate can ship	data fix, blocks the surface
Work-side offsets `w_start`/`w_end`	Highest-value rebuild item. Already computed by the matcher and discarded at ingest. Fixes containment, but far more importantly makes citations locatable — enabling side-by-side evidence, join sequencing and leaf ordering. Written into `docs/specs/discovery-v2-bake-plan.md`, Amendment 2026-08-01. Sefaria first (75% of claims, and 322 verse-level maps already exist); JA needs an investigation; M-source stores but never displays	rebuild, planned
`span_competitors` pre-shadowing + 8-gram IDF	Honest distinctiveness; a tuned prototype already exists in the gitignored spike	rebuild
`works.genre` + composition year	Genre is entirely NULL; missing liturgy dates neutralised date-based demotion	rebuild
`discovery_routing_audit.kept_tie`	NULL `demoted_work_id` makes tie pairs unreconstructable	rebuild
D-16 / PANEL-01	The findings page needs the relation filter currently specified only for the panel	open, gate 1
D-13e	Panel's middle disclosure bucket may collapse into "more matches" under the two-bucket model	open, gate 1
NOVEL-01 / D-23b	D-23b mandates "Not found in the finding aids checked" and prohibits "new"; shipped wording uses "new finds" under a candidacy hedge	amendment owed, with the candidate ≠ discovery reasoning on the record
D-21	—	no change (owner declined "Citations")
PANEL-01/02	Panel-level relation/tier filters are new scope (D-16 covers `/work/{id}` only)	carry to gate 1
~~`LONG_CITATION = 200`~~	Dropped with the confidence scale — it existed only to define the Medium level	no longer applicable

Verification technique worth reusing

All three sketches ship a node render-smoke harness asserting the prohibited-wording invariants across every manuscript × variant × language × state combination (114, 540 and 160 assertions), each proven live by a positive control — seeding a precision figure, a confidence interval or a stored vocabulary key makes the suite fail. A green check that cannot fail is worthless. This is the same technique 136-VALIDATION.md specifies for Success Criterion 7.

Sketch 003 adds a second lesson: scope every assertion to the element it is about. Its facet-header assertion tested the whole rendered page and passed while the header was wrong, because unrelated design-note prose happened to contain the phrase it grepped for. An assertion that can pass for the wrong reason is worse than none. </findings_index>

## Processed Sketches

001-discovery-panel-architecture (winner: D)
002-panel-embedded-in-browse (accepted)
003-discovery-findings-page (accepted; nav label "Computed Identifications", all three row units ship)

name	sketch-findings-genizahsearch
description	Validated design decisions, CSS patterns, and visual direction from GenizahSearch sketch experiments — the Phase 136 discovery panel, its browse-page embedding, the evidence-highlighting algorithm, and the corpus-wide findings page. Auto-load when building discovery read surfaces or any NiceGUI browse-page UI.

## Project: GenizahSearch

Comparable surfaces run ~68% mobile (measured on /atlas), so design phone-first.

Sketch sessions wrapped: 2026-07-31 (sketches 001–002), 2026-07-31 (sketch 003).

<design_direction>

Overall Direction

<findings_index>

Design Areas

Area	Reference	Key Decision
The main-pool rule (read first)	`references/main-pool-rule.md`	How "probably the identification" is decided: multi-folio agreement or near-full page coverage, as non-compensating floors. 56% / 44%. Includes the `density` trap, the containment residue, and the rebuild shopping list
Discovery panel layout & disclosure	`references/discovery-panel-layout.md`	Even two-pane layout (1fr/1fr ≥900px, stacks on mobile); three disclosure levels; manuscript pane NAMES the works; relation + tier filters with match-framing labels
Browse integration & evidence highlighting	`references/browse-integration-and-highlighting.md`	Entry control in browse toolbar row 2; panel full-width beneath the panes via a fifth `enrichment_refs` placeholder; highlighting needs normalized→raw offset mapping plus per-line span clipping
Corpus-wide findings page	`references/findings-page.md`	Nav label "Computed Identifications"; all three row units user-selectable (default = per identification, 65,200); two buckets from `is_default_eligible()`; novelty as a prominent switch voiced "Candidates for new finds"; domain/author/work cascade on the identified work's domain; modes not pages. Blocked on the rebuild — see below

A fragment is a probable identification when it matches the work across more than one leaf, or covers almost a whole page on its own. Everything else is "more matches".

Settled along with it:

The panel's tier filter is deleted, not converted. Quality is the bucket; kind is the relation filter. One filter, one toggle.
The §2 amendment shrinks to a note — band labels become tooltip-only, no new display vocabulary. §4's screening exclusion survives as gate 2; BAND-03 untouched.
The corroborated bug stops existing — the invented STRONG_BANDS was what sent the best-measured population (0.926) to the bottom level. And the split was never available: the asset's note forbids a corroborated-only or weak-only split of that measurement.

Theme

sources/themes/default.css (light), parchment.css, dark.css — exact mirrors of web/static/common.css. Use them rather than inventing tokens.

Source Files

Interactive sketches are preserved in sources/. Both run offline with no build step:

sources/001-discovery-panel-architecture/index.html — 4 layout variants, 13 real manuscripts, relation/tier filters, EN+HE RTL, three themes. Winner: variant D.
sources/002-panel-embedded-in-browse/index.html — the panel inside a faithful /browse frame, with 5 service states and 4 highlight modes (including the two broken ones, so the defects are reproducible).
sources/001-discovery-panel-architecture/data.js — real data extracted from the deployed discovery-v1-33499c5b asset. Shared by sketches 001 and 002.
sources/003-discovery-findings-page/index.html — the corpus-wide page: 3 row units × 4 service states × 2 languages × 3 nav labels, plus a "pretend rebuild has landed" switch that flips novelty from what the asset can honestly show today to the intended tri-state. Its own data.js (real totals + bounded row samples) and work-domains.js / work-domains.sample.json (the 93-work domain feasibility sample).

Hard-won findings that are NOT in any requirement doc

Stored evidence offsets index the normalized Hebrew-letter stream, not the raw text. Slicing raw text at them highlights the wrong characters (652 characters off on the sampled case).
The highlight must additionally be clipped per line, because the line-number gutter splits highlight HTML on \n. Done correctly 72 of 148 grid rows highlight; done naively, 1 — silently.
Search-term highlighting and discovery spans compete for one render parameter; one renderer must emit both.
The version selector invalidates stored offsets — the highlight must be dropped on source change.
Only the largest span is stored, so a row's stated matched-letter count can exceed what is highlightable.
The manuscript-coherence reader aid is coupled to the BAND-03 screening gate — part of the codex picture sits behind a toggle built for a different purpose.
Outage must not look like a genuine zero — today's wrappers cannot tell them apart.
144,294 direct rows carry is_new = 0 meaning UNCHECKED, not "known". A two-state novelty filter over that data makes a false claim on the flagship surface. This is why D-23a's fail-closed tri-state is load-bearing rather than bookkeeping.
coverage_ppm and band_rank do not exist as columns (PRAGMA table_info), so the coverage filter is inert until the rebuild.
A band-derived confidence scale orphans 20,435 never-assessed rows (12.3%) and forces a fourth "not assessed" level. Deriving it from the relation kind avoids this — three levels, honestly.
works.genre is entirely empty, so the domain facet needs a one-time curation pass (~1,088 works, ~96% high-confidence in one pass). The work facet needs nothing; bridging discovery titles to FJMS genizah_titles matches only 5% and is not required.
A manuscript's catalogue domain is the wrong filter axis — Moss. V,374 is catalogued Court Records while carrying a correct Rashi finding, and 338 tier-A findings sit on manuscripts catalogued documentary/legal. Filtering on it hides exactly the findings that disagree with the catalogue.
PERF-01 confirmed twice — the deduped identification count alone took 16 s. A visible real total is not free.
tier_a is 81% of the corpus and carries no measured precision in the deployed asset, so the D-18 gate hides it. The grade exists (CERT-01, 0.9382) but only in the unshipped v2 asset. Any UI that assumes the top pool is populated is describing 2,241 identifications, not 46,644.
corroborated at 0.926 is the highest measured precision in the system — higher than high_confidence_algorithmic's 0.889 — and the measurement covers corroborated ∪ weak jointly; the asset's own note forbids splitting it. Any rule that treats those two bands differently contradicts the frozen contract.
Counting per page inflates same-work matches ~2.3× (88.4% → 77.8% deduped), because a fragment that copies a work matches on every folio while a citation matches once. Bounded, because a Genizah "manuscript" here is a fragment — median 2 pages, 86.5% at one or two, max 427.
The 11,941 shared-wording claims have no matched_letters value at all. A row layout promising "N matched letters" has nothing to show on them.
not_evaluated is labelled "Shared text" but 5,604 of its claims are direct_witness. A UI section built on that band name will contain same-work claims.
density is Levenshtein edit-distance, not coverage — and the repo carries a scar from that exact confusion ("demoted ~100% of witnesses"). Real coverage is computed at bake and discarded.
claim_type is assigned by within-page span dominance (scripts/discovery_ids.py:336-382), so it defaults to direct_witness whenever the true host work is absent from the reference corpus. That is why liturgy is attributed to Rambam — a corpus-coverage problem wearing a classification problem's clothes.
Multi-folio agreement is the strongest free signal in the asset: 1 page → 72% good, 2 pages → 96%, ≥3 → 91% (n=211 human grades).
Competition/exclusivity is nearly useless as a distinctiveness proxy — only 6.7% of same-work rows have any overlapping competitor, because the reference corpus lacks the competing works.
The matcher already knows where in the work a match falls and throws it away at ingest — 3,800-char windows with tracked offsets, positions deliberately preserved. Persisting it is the single highest-leverage change available: it makes citations locatable, which is what makes them worth anything to a scholar.
Sefaria verse maps already exist — 322 *.versemap.json sidecars in refs_staging/, verse-level with character offsets, because the fetcher deliberately kept labels out of the body. But they index the body while the matcher indexes norm_stream — two coordinate systems, the same trap sketch 002 found on the manuscript side. Name the coordinate space of every offset at the point of definition; treat that as a schema rule, not two coincidences.
Only 42% of works can ever show a reference (451 Sefaria of 1,088) even though 75% of claims can — Sefaria works carry far more claims each, so design for the row, not the corpus. Three display tiers, two load-bearing on day one: full reference (Sefaria) · approximate position (JA) · omitted (M-source).
JA and M-source lack a locus for opposite reasons. JA has no data (no divisions exist) but is public — displayed, with an approximate position, and improvable later. M-source is a disclosure limit — not a data problem, so it never improves. Don't collapse them into one "degraded" case.
Rendering reference text is licence-gated PER WORK, not per corpus. SC-3's absolute ban was lifted 2026-08-02, but the gate is the acquisition manifest's existing reuse_ok: yes 277 (PD 264 · CC-BY 11 · CC0 1 · CC-BY-SA 1) · unclear 46 · noncommercial_only 1 · absent 21 = every JA work. So ~17% of Sefaria works are not clearly reusable, and JA text cannot render at all today despite being public — a licensing question entirely separate from its missing divisions. Fail closed on a missing flag; carry attribution_text for CC-BY/CC-BY-SA. And the staged bodies are lossy (nikud, punctuation and rubrics stripped at acquisition) — decide whether that is the comparison view or whether display text is re-fetched.

Requirement amendments these sketches owe

Item	Change	Status
D-09	Strike "collapsed" (variant D never collapses the manuscript group); keep the left-to-right ordering	narrow amendment owed
D-12	Offsets index the normalized letter stream; result must be clipped per line; highlight dropped on version change; search-term precedence rule	rewrite owed
`discovery-band-labels-v1.md` §2	Band labels become tooltip-only; the visible split is §4's default-shown boundary, which §4 already defines. No new display vocabulary, so a note rather than a contract rewrite. §3, §4 and BAND-03 all unaffected	small amendment owed
Panel tier filter	Deleted, not converted — quality is the bucket, kind is the relation filter	resolved 2026-08-01
`band_precision.tier_a`	Carry the CERT-01 result (`measured_pass` + real `ci_low`) into the v2 bake	data fix, blocks the surface
`page_norm_letters`	A `page_id → letter count` table (~139K ints, no text, masking-safe) so the coverage gate can ship	data fix, blocks the surface
Work-side offsets `w_start`/`w_end`	Highest-value rebuild item. Already computed by the matcher and discarded at ingest. Fixes containment, but far more importantly makes citations locatable — enabling side-by-side evidence, join sequencing and leaf ordering. Written into `docs/specs/discovery-v2-bake-plan.md`, Amendment 2026-08-01. Sefaria first (75% of claims, and 322 verse-level maps already exist); JA needs an investigation; M-source stores but never displays	rebuild, planned
`span_competitors` pre-shadowing + 8-gram IDF	Honest distinctiveness; a tuned prototype already exists in the gitignored spike	rebuild
`works.genre` + composition year	Genre is entirely NULL; missing liturgy dates neutralised date-based demotion	rebuild
`discovery_routing_audit.kept_tie`	NULL `demoted_work_id` makes tie pairs unreconstructable	rebuild
D-16 / PANEL-01	The findings page needs the relation filter currently specified only for the panel	open, gate 1
D-13e	Panel's middle disclosure bucket may collapse into "more matches" under the two-bucket model	open, gate 1
NOVEL-01 / D-23b	D-23b mandates "Not found in the finding aids checked" and prohibits "new"; shipped wording uses "new finds" under a candidacy hedge	amendment owed, with the candidate ≠ discovery reasoning on the record
D-21	—	no change (owner declined "Citations")
PANEL-01/02	Panel-level relation/tier filters are new scope (D-16 covers `/work/{id}` only)	carry to gate 1
~~`LONG_CITATION = 200`~~	Dropped with the confidence scale — it existed only to define the Medium level	no longer applicable

Verification technique worth reusing

## Processed Sketches

001-discovery-panel-architecture (winner: D)
002-panel-embedded-in-browse (accepted)
003-discovery-findings-page (accepted; nav label "Computed Identifications", all three row units ship)

sketch-findings-genizahsearch

More from this repository

More from this repository

Overall Direction

Design Areas

Theme

Source Files

Hard-won findings that are NOT in any requirement doc

Requirement amendments these sketches owe

Verification technique worth reusing

Overall Direction

Design Areas

Theme

Source Files

Hard-won findings that are NOT in any requirement doc

Requirement amendments these sketches owe

Verification technique worth reusing