Ecosystem overview

StringForge is the shared infrastructure layer for a family of JAX-based packages targeting string compactifications, Calabi-Yau geometry, and effective field theories. It standardises the data and provenance boundary: catalogues, caches, model-loading bridges, vault layouts, and validation.

StringForge intentionally carries minimal physics. Physics engines consume its data interfaces, but their computations live in their own packages.

Package status

Package	Role	Status	Reference
jaxvacua	Type IIB flux vacua: complex-structure sector, vacuum finding, stability analysis.	Public	arXiv:2306.06160
jaxpolylog — GitHub  docs	JAX-compatible polylogarithm functions with autodiff support.	Public	–
kahlerjax	Planned Kähler-moduli stabilisation package.	Planned; API not stable	arXiv:2507.00615
jaxiverse	Planned multi-axion EFT package.	Planned; API not stable	–
cytools	External toric Calabi-Yau geometry library.	Public external dependency	arXiv:2211.03823

Important

KahlerJAX and JAXiverse are shown to explain the intended ecosystem boundary. They are not installed by StringForge, are not imported by StringForge, and their public APIs should be treated as provisional until their own releases.

Ecosystem flow

The figure below shows the practical boundary between StringForge and sibling packages. StringForge owns shared data movement and validation; the physics packages own their package-specific calculations.

StringForge ecosystem flow

StringForge supplies the shared data and vault infrastructure; the physics packages keep their numerical engines and public APIs separate.

External catalogues and numerical leaves

CYTools Toric Calabi-Yau geometry and triangulation data.

JAXPolyLog JAX-compatible polylogarithms used by the EFT packages.

HuggingFace datasets CY catalogues, KKLT subsets, and curated vacua vaults.

Shared infrastructure layer

StringForge Catalogue I/O, mirror-convention model loaders, vacuum persistence, and vault validation.

Physics packages and user workflows

JAXVacua Flux EFTs, vacuum finding, sampling, and stability analysis.

KahlerJAX Kahler-moduli stabilisation and corrected 4-D EFTs.

JAXiverse Axion spectra, couplings, and multi-axion effective theories.

Research pipelines End-to-end scans that combine database access and package-specific analysis.

Boundary rule: StringForge moves, validates, and names shared data; sibling packages own the physics calculations performed on that data.

Where to read what

If you want…	Look here
Database queries, cache/offline behaviour, and HuggingFace layout.	Calabi-Yau Geometry Database.
Loading JAXVacua models from database rows.	Getting started and Database interface.
Vacuum-solution storage, designation, validation, and vault publication.	Vault workflow, Vacua storage, and stringforge.vacuavault.
Flux vacuum search, ISD sampling, flux bounding, periods, and mass spectra.	The JAXVacua documentation.
Advanced KKLT-style curated index and tagging.	KKLT Database.
Planned Kähler or axion packages.	The planning pages, with the caveat that these are not first-release APIs.

Future optimisation tooling

PFV/fan-roots style optimisation packages are natural future consumers of the StringForge data and vault conventions. They are not public release components and no install links are provided here yet.

Citing the framework

Cite the package release together with the package-specific physics/software papers relevant to your workflow. For flux-vacuum calculations, cite the JAXVacua paper in addition to StringForge.