48 public repositories · 36 physics/mathematics projects

Repository
landscape

Every public repository is listed, with a separate physics/mathematics filter for the research corpus. Theory, metric kernels, JIF phase models, trajectories, lensing, data pipelines, mathematical experiments, tests, plots and documentation are mapped as one inspectable research landscape.

git
How repository counts are defined: 48 is the current public GitHub snapshot; 36 are classified physics/mathematics projects; 38 is the local public-scope inventory used by the atlas; and 28 is the subset carrying test records. These are different denominators, not contradictory totals.
Dependency map

Research flow

Theory
canonical scope
Metric
core functions
Observables
trajectories/lensing/data
Tests/docs
locks and releases

Core

ssz-complete-documentation, SSZ-METRIC_COMPLETE, ssz-full-metric, ssz-metric-final and ssz-metric-pure.

Phase and closure research

ssz-jif-core, ssz-jif-forward-lab, ssz-jif-bounded-physical-fusion, ssz-hilfsdateien and ssz-recursive-closure-pc. Open JIF · Open closure lab

Forward models

ssz-trajectories, ssz-lensing, mass projection, G79 and energy analyses.

Verification

ssz-all-tests, metric suites, frequency-curvature validation, plots and documentation audits.

Interactive catalogue · API snapshot 5 August 2026

All public physics and mathematics repositories

The catalogue is generated locally from GitHub’s public repository metadata and shipped as static JSON; no browser token or live API request is used. “Archived” is a hosting status, not a judgement that the scientific content is obsolete. Repository descriptions are quoted metadata and do not override the portal’s P0 scientific scope.

Loading…matching public repositories

Loading static repository metadata…

Cross-repository rules

Single scientific vocabulary

Ξ, D, r_s, branch domains and observable methods must mean the same thing across repositories. A local toy formula must carry a toy/legacy label.

Locks before downstream results

Branch, field and model locks should precede expensive data runs. Results must record the exact lock and commit they consumed.

No silent result promotion

A plot repository may visualise a result but does not raise its epistemic status. The underlying derivation and test provenance remain authoritative.

Dirty working trees

The inventory records local modification state without changing those repositories. Unrelated working changes were preserved.

Reading compass

How to read Repositories

This page separates the declared definition, its computation or visualisation, the evidence supporting it, and the conclusions that remain outside its scope.

1 · Reading path

Start with the formula or control, identify its domain and inputs, then follow the linked implementation and evidence record.

2 · What a result means

A passing identity, numerical limit, plot or comparison supports only the stated relation under its recorded assumptions and provenance.

3 · What it does not mean

It is not automatically an independent experiment, a complete physical theory, or a proof beyond the explicit claim boundary.

Foundational synthesis

Definitions, evidence and limitations stay linked

The portal keeps current canonical locks above historical descriptions and keeps software verification separate from empirical confirmation.

01

Canonical source

Use the current P0, JIF or mathematical lock for the formula and domain shown on this page.

02

Evidence class

Read tests, convergence, reference compatibility, dataset-conditioned comparisons and independent replication as different evidence classes.

03

Boundary

Every result retains its assumptions, limits and explicit non-claim so a visual or passing assertion is not over-promoted.