Qamus particle family P-00
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 family is
Particle work-ordering family P-00: 12 entries — بِـ, تَـ, فَـ, كَـ / ـكَ / ـكِ, لَـ / لِـ, وَ, أَوْ, فِي, عَلَى, إِلَى, عَنْ, حَتَّى
(pages: p002, p003, p005, p006, p007, p009, p022, p035, p036, p037, p038, p039; source: qamus/data/particle-tranche-membership.json). Function families: jarr clitic bi-; oath-jarr ta- (qasam); connective fa- (ʿaṭf/result); jarr ka- (+ pronoun-suffix homoform); jarr/lām li-/la-; connective wa- (ʿaṭf/oath/ḥāl); disjunctive connective aw; jarr fī; jarr ʿalā; jarr ilā; jarr ʿan; jarr/ghāya ḥattā (multi-function).
Flags: 3 dual-family-tension (rival family assignment recorded, never collapsed).
Includes بِـ (p002) and لِـ/لَـ (p007). The p007 vertical slice already proved this lane end-to-end: 12 occurrences / 78 appearances certified two-vote, 49 typed facts, identical projections at every appearance (incl. fused لِلَّهِ), measured pattern ceiling 580 rows / 1,266 appearances. The بِـ family pre-flight is queue item 3 in qamus/work-queues/next-actions.jsonl (owner ruling: family becomes candidate only after entry id, senses, and population are verified, reusing the p007 machinery with measured reuse reported).
The denominator that makes this the top-yield lane: the particle universe is ~50,263 candidate
occurrences with ~109,364 appearances, and 99.1% of those appearances sit on V/N pages as
example-āyah context words — currently certified: none for every row. The particle pages' own
spans are 983/984 rich live, but that old-era richness does not transclude; only certification does.
Impact on transclusion & the sarf/naḥw lattice projection
This is the purest transclusion lane in the programme: certify one particle occurrence and the
projection-hash parity invariant renders it rich on every card it appears on — across all 24 VN
tranches — with zero per-page authoring (measured on the VN-00 readback pilot: ~2,690 rendered-span
edges corpus-wide from one window's accounting). Surface match never authorizes reuse (og-1/og-2):
membership goes through the candidate matrix → disposition → certification rungs, never lookalike copying.
When this family closes, post the measured unlock counts on the affected VN issues.
Impact on the flywheel & repo
Family certification exercises the sarf/naḥw skills on real corpus at scale; every abstention,
disagreement, or defect (e.g. clitic-host segmentation, allomorph families like لَهُمْ/لَكُمْ) returns
to /fusha/ as fixtures, misconception rows, or registry keys. Dual-function and homograph rows
exercise rival preservation — outcomes feed the naḥw skill's attributed-alternatives machinery.
Closure conditions (ladder)
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).
Qamus particle family P-00
What this family is
Particle work-ordering family P-00: 12 entries — بِـ, تَـ, فَـ, كَـ / ـكَ / ـكِ, لَـ / لِـ, وَ, أَوْ, فِي, عَلَى, إِلَى, عَنْ, حَتَّى
(pages: p002, p003, p005, p006, p007, p009, p022, p035, p036, p037, p038, p039; source:
qamus/data/particle-tranche-membership.json). Function families: jarr clitic bi-; oath-jarr ta- (qasam); connective fa- (ʿaṭf/result); jarr ka- (+ pronoun-suffix homoform); jarr/lām li-/la-; connective wa- (ʿaṭf/oath/ḥāl); disjunctive connective aw; jarr fī; jarr ʿalā; jarr ilā; jarr ʿan; jarr/ghāya ḥattā (multi-function).Flags: 3 dual-family-tension (rival family assignment recorded, never collapsed).
Includes بِـ (p002) and لِـ/لَـ (p007). The p007 vertical slice already proved this lane end-to-end: 12 occurrences / 78 appearances certified two-vote, 49 typed facts, identical projections at every appearance (incl. fused لِلَّهِ), measured pattern ceiling 580 rows / 1,266 appearances. The بِـ family pre-flight is queue item 3 in
qamus/work-queues/next-actions.jsonl(owner ruling: family becomes candidate only after entry id, senses, and population are verified, reusing the p007 machinery with measured reuse reported).The denominator that makes this the top-yield lane: the particle universe is ~50,263 candidate
occurrences with ~109,364 appearances, and 99.1% of those appearances sit on V/N pages as
example-āyah context words — currently
certified: nonefor every row. The particle pages' ownspans are 983/984 rich live, but that old-era richness does not transclude; only certification does.
Impact on transclusion & the sarf/naḥw lattice projection
This is the purest transclusion lane in the programme: certify one particle occurrence and the
projection-hash parity invariant renders it rich on every card it appears on — across all 24 VN
tranches — with zero per-page authoring (measured on the VN-00 readback pilot: ~2,690 rendered-span
edges corpus-wide from one window's accounting). Surface match never authorizes reuse (og-1/og-2):
membership goes through the candidate matrix → disposition → certification rungs, never lookalike copying.
When this family closes, post the measured unlock counts on the affected VN issues.
Impact on the flywheel & repo
Family certification exercises the sarf/naḥw skills on real corpus at scale; every abstention,
disagreement, or defect (e.g. clitic-host segmentation, allomorph families like لَهُمْ/لَكُمْ) returns
to /fusha/ as fixtures, misconception rows, or registry keys. Dual-function and homograph rows
exercise rival preservation — outcomes feed the naḥw skill's attributed-alternatives machinery.
Closure conditions (ladder)
tools/certify_typed_fact.py), guarded projection, or explicit pending/scholar state with causeUpdate & closure discipline
(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).
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.
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).