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.