Skip to content

07 — Professor Adjudication

Core claim: Three independent reviewers raised ~15 distinct claims. Of these, exactly 2 are genuine corrections to the core pipeline (Phase 0 and path-sequence preservation). Everything else is either already captured, derivable, withdrawn, out of scope, or opinion.


#ProfileSource
P1Algebraic geometer / Abel Laureatecomments/1.md
P2Mathematician with fiqh awarenesscomments/2.md
P3Professor of ʿIlm al-Farāʾiḍcomments/3.md

Claim 1: Ghost Pressure Anomaly — Phase 0

Section titled “Claim 1: Ghost Pressure Anomaly — Phase 0”

Claim: A murderer (attribute-blocked) should be topologically void but the pipeline would falsely trigger ghost pressure on the mother. Need a Phase 0 splitting attribute-exclusion from person-exclusion.

Verdict: TRUE — Genuine correction.

This was incorporated as Phase 0 in the pipeline. The original v2 pipeline applied ghost pressure before filtering attribute-excluded heirs, which is wrong. faraid/hajb.md is explicit: “المحجوب بوصفٍ وجودُه كعدمه” — an attribute-excluded heir is “as if non-existent.”

Action taken: Phase 0 added. See 04-pipeline.md.


Claim 2: Subspace Projection Failure — Tanzīl / Dhawī al-Arḥām

Section titled “Claim 2: Subspace Projection Failure — Tanzīl / Dhawī al-Arḥām”

Claim: A $c=0$ heir cannot be evaluated by the standard pipeline. Requires a projection operator $T(h) \to h’$ walking up the DAG.

Verdict: TRUE but correctly classified as Extension, not core flaw.

Dhawī al-Arḥām ($c=0$) are handled by the Project extension operator, not by the core pipeline. The core pipeline only processes $c=1$ heirs. P1 is right that projection is needed, but wrong that this is a flaw in the core axioms — it’s an extension by design. See 06-core-vs-extensions.md.


Claim 3: Path-History Destruction — Grandmother Paradox

Section titled “Claim 3: Path-History Destruction — Grandmother Paradox”

Claim: Reducing BFS to scalar $d$ destroys the gender sequence. “Mother of Father of Mother” ($c=0$) and “Mother of Mother of Father” ($c=1$) both yield $d=3$ but have different legal validity.

Verdict: TRUE — Genuine correction at the resolver layer.

The 5-tuple component $c$ captures the result of the path check, but the BFS resolver must preserve the full path sequence to compute $c$ correctly. Specifically, for grandmothers ($j=2$), the pattern “male between two females” must be detected by examining the actual path, not just the scalar distance.

Action taken: The BFS resolver is specified to output full gender sequences. The $c$ value is then computed from the sequence by the axis-specific predicates (Theorem 1). See 01-5tuple-and-graph.md and 05-proofs.md.


Claim 4: Superposition — Mafqūd / Al-Ḥaml

Section titled “Claim 4: Superposition — Mafqūd / Al-Ḥaml”

Claim: Missing persons require solving two parallel cases and allocating via $\min(S_0, S_1)$. The axioms assume deterministic state.

Verdict: WITHDRAWN by P1.

P1 agreed these are “higher-order meta-functions wrapping the base engine” — exactly our Extension classification. See Min operator in 06-core-vs-extensions.md.


Claim 5: Multi-Generational Linear Combinations — Munāsakhat

Section titled “Claim 5: Multi-Generational Linear Combinations — Munāsakhat”

Claim: Sequential deaths require LCM across multiple resolution spaces.

Verdict: WITHDRAWN by P1.

P1 acknowledged “the Taṣḥīḥ step already outputs LCM integers, making Munāsakhat a trivial API wrapper.” Exactly our Chain extension. See 06-core-vs-extensions.md.


P1 also specified three output requirements that the engine must satisfy:

RequirementStatus
Pure functions (no side effects)✓ Pipeline is stateless
Zero-vectors (eliminated heirs get 0, not null)✓ Phase 2 outputs 0-shares
Rational number structs (not floats)✓ All computation in $\mathbb{Q}_{(2,3)}$

These are engineering constraints, not mathematical corrections.


Claim 1: Parameterized Toggle Architecture

Section titled “Claim 1: Parameterized Toggle Architecture”

Claim: Build a pristine base engine (Layer 1: invariants) + jurisprudential toggles (Layer 2: dispute switches).

Verdict: CONSISTENT — this is the Path A / Path B architecture.

P2’s “Layer 1 + Layer 2” is exactly our formulation:

  • Layer 1 = 3 axioms + 1 exception (Path A core).
  • Layer 2 = Additional exceptions activated per-madhhab (Path B variants).

This is architectural guidance, not a correction. See 08-path-comparison.md.


Claim 2: Jumhūr Pattern is “Impossible” to Unify

Section titled “Claim 2: Jumhūr Pattern is “Impossible” to Unify”

Claim: The Jumhūr used istiḥsān (juristic preference), so there is no single formula. Their hidden pattern is “Pareto Optimization / Minimax.”

Verdict: UNPROVEN.

P2 asserts the Jumhūr optimized for a Pareto principle (no close relative collapses to zero). This is a hypothesis, not a theorem. The Pareto claim is plausible for some cases (e.g., Mushtaraka — saving the full brother) but has not been demonstrated for all Jumhūr exceptions.

The claim that unification is “impossible” is too strong — no impossibility proof was provided. It remains an open question whether a single additional axiom or principle can account for all Jumhūr deviations. See 09-open-questions.md.


P2 analyzed three disputes:

DisputeP2’s AssessmentOur Assessment
Grandfather-SiblingḤanafī = elegant, Jumhūr = messyAgreed. Ḥanafī = Path A, Jumhūr = $\epsilon_3$
MushtarakaḤanbalī = sound, Mālikī/Shāfiʿī = patched$\epsilon_8$ under Path B. See 03-exceptions.md
AkdariyyaStandard = apply ʿawl, Zayd = overrideSub-case of $\epsilon_3$ (grandfather-sibling interaction with ʿawl)

These are accurate descriptions of existing positions, not corrections.


Claim 1: Ghost Heir Paradox (Order of Operations)

Section titled “Claim 1: Ghost Heir Paradox (Order of Operations)”

Claim: Father eliminates brothers via $\alpha$, but brothers still reduce mother from $\frac{1}{3}$ to $\frac{1}{6}$. The system needs $\beta$ to read the original state before $\alpha$ filters.

Verdict: TRUE — resolved by pipeline ordering.

This is the same issue as P1’s Phase 0, but from a different angle. P3 identifies that ghost pressure must be evaluated before person exclusion. P3 later agreed it’s a “sequence/pipeline issue, not an axiom flaw.”

Action taken: Phase 1 (ghost pressure) precedes Phase 2 (person exclusion). See 04-pipeline.md.


Claim: Spouses do not participate in Radd. Axiom $\gamma$ cannot be universal normalization.

Verdict: TRUE — already captured as $\epsilon_8$.

The spousal Radd immunity is already exception $\epsilon_8$ in our framework. The unified normalization formula handles it by locking the spouse and normalizing only the blood heirs. P3’s observation is correct but was already in the model. See 03-exceptions.md.


Claim 3: Dynamic Baseline — Gharrāwayn / ʿUmariyyatān

Section titled “Claim 3: Dynamic Baseline — Gharrāwayn / ʿUmariyyatān”

Claim: The mother’s $\frac{1}{3}$ is sometimes applied to the remainder, not the total. The system lacks a dynamic baseline mechanism.

Verdict: FALSE — derivable, not exceptional.

P3 frames this as a missing mechanism, but Theorem 7 (05-proofs.md) proves that the ʿUmariyyatān are forced by the constraint father $\ge$ mother. The “dynamic baseline” is a consequence of the axioms plus the gender rule, not an independent principle. It is captured as $\epsilon_6$ (derived exception, not irreducible).


Claim: The linear priority vector cannot model Jumhūr’s Muqāsama between grandfather and siblings.

Verdict: TRUE under Jumhūr — already $\epsilon_3$.

Under the Ḥanafī path (Path A), grandfather excludes siblings entirely — no exception needed. Under the Jumhūr path (Path B), this is $\epsilon_3$ with the max(Muqāsama, $\frac{1}{3}$, $\frac{1}{6}$) optimization. Already captured.


Claim 5: Blessed Kinsman (Upward Entanglement)

Section titled “Claim 5: Blessed Kinsman (Upward Entanglement)”

Claim: A great-grandson ($d=3$) rescues a son’s daughter ($d=2$) zeroed by the $\frac{2}{3}$ ceiling.

Verdict: CONCEDED by P3.

P3 acknowledged this is emergent from ʿaṣaba bi-l-ghayr (a male at $d \ge d_{\text{female}}$ converts the female to ʿaṣaba, saving her from being zeroed). No new exception needed.


Challenge: Does the system let the full brother get 0 (Ḥanbalī) or save him via joint-coordinate fusion (Shāfiʿī/Mālikī)?

Response: Both paths are modeled:

  • Path A / Ḥanbalī: Full brother is ʿaṣaba. Remainder = 0 after farḍ. He gets 0. Mathematically consistent — no exception needed.
  • Path B / Shāfiʿī-Mālikī: Full brother is reclassified as maternal sibling for this case. This requires a specific exception ($\epsilon_8$ variant or separate Mushtaraka toggle). See 08-path-comparison.md.

#SourceClaimVerdictAction
P1.1Abel LaureatePhase 0 (attribute exclusion)TRUEAdded Phase 0
P1.2Abel LaureateTanzīl projectionTRUE (extension)Classified as Project
P1.3Abel LaureatePath-history preservationTRUEBFS outputs full sequence
P1.4Abel LaureateMafqūd superpositionWITHDRAWNClassified as Min
P1.5Abel LaureateMunāsakhat chainingWITHDRAWNClassified as Chain
P2.1MathematicianToggle architectureConsistent= Path A/B design
P2.2MathematicianJumhūr impossible to unifyUNPROVENOpen question
P2.3MathematicianPareto/minimax hypothesisUNPROVENOpen question
P3.1Farāʾiḍ ProfGhost pressure orderingTRUE= P1.1 (same fix)
P3.2Farāʾiḍ ProfSpousal Radd immunityTRUE (already $\epsilon_8$)Already captured
P3.3Farāʾiḍ ProfGharrāwayn dynamic baselineFALSE (derivable)Theorem 7
P3.4Farāʾiḍ ProfGrandfather-siblingTRUE (Jumhūr $\epsilon_3$)Already captured
P3.5Farāʾiḍ ProfBlessed KinsmanCONCEDEDEmergent property
P3.6Farāʾiḍ ProfMushtaraka challengeBoth paths modeledPath A vs Path B

Genuine corrections to the pipeline: 2 (Phase 0, path-sequence). Already captured: 5 ($\epsilon_3$, $\epsilon_8$, Blessed Kinsman, extensions). Withdrawn: 2 (Mafqūd, Munāsakhat). Derivable: 1 (ʿUmariyyatān). Unproven: 2 (Jumhūr impossibility, Pareto hypothesis). Architectural guidance: 1 (toggle design). Challenge answered: 1 (Mushtaraka).