Documentation

LeanPool.JacobianDiffgeo.FormTrace

form-trace-tower: pair-form residues and residue-trace compatibility (namespace RS.FormTrace) #

Unit: form-trace-tower (docs/design/form-trace-tower.md). Builds on meromorphic-trace (complete). Fibrewise trace tower for pair-forms h·F^*(dz) along F : X → Y: pair-form residues, chart handling, and residue-trace compatibility (Miranda Lemma 3.2 globalized).

Three design bugs were found and corrected/documented during construction — read before use:

  1. resAtX's target-chart invariance is FALSE in general (PairForm.lean). The design's resAtX_eq_of_mem_source claimed resAtX may be recomputed in an arbitrary pair of maximal-atlas charts with no correction. Counterexample: X=Y=ℂ, F=id, h=1/z, comparing target chart id vs y↦2y gives residue 1 vs 2. Only the SOURCE-chart half survives as a general, exported fact: resAtX_eq_of_mem_source_left.
  2. The main theorem needs an explicit calibration hypothesis (ResidueTraceCompat.lean). resAtP1_trace_eq_sum (Miranda Lemma 3.2 globalized) is proved, but — because of finding (1) — it takes an extra hypothesis hcal asserting the FiberStack's adapted target charts are translates of chartAt ℂ y₀. This is satisfied by any stack from exists_fiberStack (verified by reading exists_adaptedChartsAt's construction directly), but is NOT derivable from the abstract FiberStack/AdaptedChartsAt structure fields alone.
  3. trace_eq_zero_of_holomorphic (design's HolomorphicVanishing.lean) is FALSE, and was NOT built. RS.MTrace.trace is the UNWEIGHTED fibre sum (trace_eq_finsum', mtrace, zero sorries, unconditional). For constant h ≡ 1 (globally holomorphic on compact X — such h is automatically constant by the maximum-modulus principle, so this is not a degenerate case) and ANY nonconstant F : X → ℙ¹, trace F h equals degree F at regular values but only the (strictly smaller, by Riemann–Hurwitz, since branch points always exist for deg ≥ 2 maps to ℙ¹) fibre CARDINALITY at branch values — i.e. trace F h is not even continuous at a branch point unless h vanishes there, let alone identically 0. This is a genuine defect in the design's plan for Miranda's "integration of a trace" ingredient (Item 5), not a proof-effort gap: fixing it would need a materially different object (a genuinely Jacobian-weighted trace of the FORM, not the bare function trace D1 deliberately avoided introducing) — flagged LOUDLY for the orchestrator / a future builder, not attempted here. RationalOnP1.lean (the other file gated behind similar bonus/non-load-bearing status, §0.3 of the design) was also not built, for time-budget reasons (lowest priority per the design itself).

What IS here, zero sorries #

Notes for downstream consumers #