Rails looks less like a creator's kingdom than like a civilization where many architects share the same ground — and relational gravity reads that flatness honestly.

The top author still sits where the structure was first laid: Design 100, Indispensability 100, the founder's signature on the shape of the system. Yet their Gravity reads a quiet 4.0. Under relational gravity, surviving structure alone does not mint influence — the gates ask whether the code still lasts where others actively commit, and whether someone is observably building on it. The top author's modules are revered, but they sit largely undisturbed; the telescope does not confuse that stillness with the system leaning on them today. Might a founder's centrality fade not by being displaced, but simply by no one needing to lean on it anymore?

Around them the field stays remarkably even. #2 (3.8), #3 (3.6), and #4 (3.5) hold gravity within touching distance of the founder, and the design history runs deep across many hands — #2 (Design 96.8), #3 (89.5), #4 (89.2). Ten contributors clear Design 35, with the Top-10 averaging 57.0. Rails is "framework-driven" in its outward API, yet internally it reads like a project that no single person holds.

Gravity Concentration of 9.8% — top-3 holding under a tenth of the total — is among the lowest of any universe observed, well below the Rust compiler (27.6%) or Kubernetes (27.5%). In a vast, dispersed collaboration, not even the creator's gravity dominates — the system observably rests on no one in particular. That is not a verdict on anyone. It is the instrument declining to read ownership, or seniority, or being first, as gravity.