Create and explore imaginative 3D worlds with our new product Dreamfield (opens in a new tab)

Lift the hypergeometric confluence diagram to equivariant meromorphic connections

Determine whether the entire hypergeometric confluence diagram can be lifted to a diagram of equivariant meromorphic connections in which confluence arrows are supplemented by arrows corresponding to finite coverings and foldings, and establish a categorical or moduli-theoretic formulation if one exists.

Background

The paper realizes the passage from the Bessel equation to the Bessel–Clifford equation through a Z2-equivariant meromorphic connection and the quotient coordinate ξ = λ². Its Schrödinger-gauge analysis also identifies the associated Kummer and Bessel potentials within the classical confluent hypergeometric picture.

The authors ask whether this single example extends to the full diagram of confluent special-function equations, with confluence and finite covering or folding operations represented simultaneously at the level of meromorphic connections. They also suggest a categorical or moduli-theoretic framework for such a construction.

References

This raises the question of whether the “entire hypergeometric confluence diagram can be lifted to a diagram of equivariant meromorphic connections”, in which arrows corresponding to confluence are supplemented by arrows corresponding to finite coverings and foldings. One may equivalently ask whether there exists a categorical or moduli-theoretic formulation of these results.

— Folding to the Bessel-Clifford system, and Equivariant Topological Recursion  (2610.23320 - Alameddine et al., 16 Oct 2026) in Section 4, Further directions

A particularly interesting problem is to determine whether the fractional shifts of monodromy parameters produced by folding can be described directly from the ramification indices and the characters of the equivariant structure.

— Folding to the Bessel-Clifford system, and Equivariant Topological Recursion  (2610.23320 - Alameddine et al., 16 Oct 2026) in Section 4, Further directions