The problem NodeRail™ was built to solve
Intellectual work has a continuity problem. A researcher builds a framework, publishes a paper, and moves on. The framework is never updated, never linked to the work that builds on it, and within five years it is effectively lost — even if the paper is still technically accessible. A student completes a dissertation that contains genuinely original thinking. It is submitted, graded, and filed. No one builds on it. It compounds nothing.
This is not a storage problem. It is a structural problem. The tools we use to produce and share intellectual work — documents, wikis, papers, slide decks — are not designed for continuity. They are designed for point-in-time communication. NodeRail is designed for something different: structured, versioned, citable intellectual infrastructure that compounds over time.
What NodeRail™ is
NodeRail is versioned knowledge infrastructure. It gives researchers, practitioners, and students a permanent, citable home for their intellectual work — with DOI versioning via Zenodo, Git-based lineage tracking, and academic citation built in from the start.
Work on NodeRail is organised into four structured units called nodes: Fields, Frameworks, Measurements, and Projects. Each node follows a consistent template, is version-controlled in Git, and receives a permanent DOI on its first stable release. Nodes can be forked, extended, and built upon by others — with full attribution and lineage preserved.
The result is an intellectual record that persists, compounds, and remains citable long after the original author has moved on.
Where we are now
NodeRail is at v0.1. The platform is live at noderail.org, the first Founder Field (Human Capacity Science) is in development, and the first DOI has been issued. We are in early access, onboarding the first cohort of researchers, students, and practitioners who will publish the platform's founding nodes.
This is a deliberate pace. NodeRail is infrastructure. Infrastructure needs to be built carefully, with the right people, before it scales. The early access period is how we ensure the first nodes set the right standard for everything that follows.
Our principles
Permanence over convenience
We build for the 20-year view, not the 20-minute view. Every design decision prioritises the long-term integrity of the work over short-term ease of use.
Attribution as infrastructure
Every fork, extension, and adoption preserves the full lineage back to the origin. Credit is structural, not optional.
Open by default
NodeRail is open source and all nodes are open access. Knowledge infrastructure should not be locked behind paywalls.
No prestige filter
A student's dissertation and a professor's framework are evaluated by the same standard: the quality and structure of the intellectual work, not the institution behind it.
Structure enables compounding
Freeform text does not compound. Structured nodes do. The template is not a constraint — it is the mechanism that makes intellectual work reusable.
Built in public
NodeRail is being built transparently. The code is open, the decisions are documented, and the platform itself is published on NodeRail.
Milestones
February 2026 — v0.1 launched
NodeRail goes live at noderail.org. First Founder Field (HCS) in development. First DOI issued: 10.5281/zenodo.18764766.
Q2 2026 — v0.2 (planned)
First external nodes published. DOI integration automated. University partnership programme launched.
Q4 2026 — v1.0 (planned)
Public node registry. Continuity Standard v1.0 published. First institutional cohort onboarded.
Gao Kabubi
Gao is the founder of NodeRail and the originator of Human Capacity Science (HCS). She is also the founder of Dustoff Reset, a cognitive health tool built on HCS principles. NodeRail was built to solve a problem Gao encountered directly: intellectual work that could not find a permanent, structured, citable home.