Qamus VN-19 — v858–v902 + n0946–n0995 (95 pages, 1,074 occurrences)

[theislampill]

Qamus VN-19 — v858–v902 + n0946–n0995

Generated from repo ledgers at main@3396d79 (2026-08-05). This issue is a public mirror of the committed ledgers; on any conflict the ledgers win. Evidence in comments must cite repo paths, PR numbers, or blocker ids — never private-workspace packet contents or server topology.

What this tranche is

Live-render tranche VN-19 of qamus.dawah.wiki: 95 pages (v858–v902 + n0946–n0995), carrying
1,074 unique Qurʾānic occurrences across 1,099 appearance rows in their example āyāt
(source: qamus/reports/pvn-rollout-map.jsonl, plan_tranche=VN-19). Every example-āyah word on
these cards must end coloured (rich segmentation) and rich-hover-glossed, with each analysis
traced to certified typed facts.

Current measured state: not yet measured under the respec windows (see ledger tally below).
Ledger row states — span_gate: {'not_measured': 95}; completion_state: {'not_measured': 95} (the
completion ladder is instrumented for 3 pilot entries programme-wide; not_measured is the honest
default, not a pass).

Impact on transclusion & the sarf/naḥw lattice projection

Each word here is an occurrence node (quran:S:A:W). Colour and hover come from certified typed
facts projected through the meta-transclusive sarf & naḥw lattice under the projection-hash parity
invariant: the same occurrence renders identically on every page it appears on. Two consequences:

1. This window receives transclusion for free from particle-family certification — its cards'
   وَ/بِـ/لِـ/فَـ context words light up when the particle-family issues (Qamus particle family P-00 — 12 entries (jarr clitic bi-; oath-jarr ta- (qasam); connective fa- (ʿaṭf…) #210/Qamus particle family P-01 — 17 entries (emphatic nūn (tawkīd, verb mood); naṣb governor (anna, inna-…) #211/Qamus particle family P-02 — 22 entries (homograph: in (condition / negation / mukhaffafa); homograph…) #212/Qamus particle family P-03 — 16 entries (question/response + operator particles) #213/Qamus particle family P-04 — 18 entries (demonstratives + relatives) #215/Qamus particle family P-05 — 15 entries (personal pronouns: subject + iyyā) #216) close (99.1% of particle
   appearances sit on V/N pages). Record those unlocks here as they land.
2. This window donates transclusion outward — occurrences certified while accounting these pages
   render rich on every other card sharing them, and their facts become corpus grounding for the
   curriculum units (Line 3 of the absorption schedule).

Impact on the flywheel & repo

Accounting these pages surfaces defects (mis-segmentation, wrong iʿrāb, collapsed rivals, parity
forks). Each becomes a red-first fixture or misconception row in /fusha/'s sarf/naḥw eval banks —
the flywheel: corpus work returns knowledge to the skills, which improves the next window's
automatic projection rate. Report the measured return (rows emitted) in this issue.

Closure conditions (ladder — later rungs need earlier ones)

• Span gate: 100% live-render completeness verified on all 95 pages (server-side smoke, leak-scan discipline)
• norm@1 measured for this window (tools/check_rich_hover_norm.py) and deterministic-lane ceiling reached (norm is recall instrumentation, never certification)
• Occurrence accounting: every example-āyah word dispositioned — certified typed facts, guarded projection, or explicit pending state with cause; no surface-match reuse
• Colour + hover parity in the candidate plane: projections emitted for all 1,074 occurrences with hash parity across appearances; defects fixture-queued
• 🔒 Deployed live (owner-gated): a bounded deploy window updates qamus.dawah.wiki and these pages render rich — cite the deploy receipt
• Flywheel return: fixtures/misconception/drill rows emitted to /fusha/ from this window's defects, with paths

Update & closure discipline

• The executor updates this issue as work lands: check boxes with a one-line evidence citation
  (PR number + ledger path), and post a comment when another issue's closure changes this window's
  measured state (e.g. a particle-family closure lighting up context words here — cite the count).
• This issue CLOSES only when BOTH are true: the repo ledgers record the closed state AND the live
  website renders it. The deploy rung is owner-gated (docs/blockers.yaml → owner-deploy-packet);
  everything above it is executor work. Candidate-plane completion with no deploy = issue stays open.
• The closing comment must state the realized impact: occurrences accounted, facts certified, cards
  now rich live, cross-page appearances lit elsewhere (name the issues), and what the flywheel
  returned to /fusha/ (fixtures, misconception rows, drill keys — cite paths).