Glossary, Continuity Standard, and FAQ in one place.
Ten core terms that define the vocabulary of intellectual continuity infrastructure.
The property of a body of knowledge that allows it to be extended, built upon, and cited over time without losing its lineage, definitions, or authorship trail. The opposite of documentation debt, concept drift, and knowledge fragmentation.
A structured, citable unit of intellectual work on NodeRail. Each node has a type (Field, Framework, Measurement, or Project), a version history, a permanent DOI, and an explicit lineage back to its origin.
The authoritative, versioned definition of a term or construct within a field. A canonical definition has an owner, a version number, and a change log. It is the single source of truth for that construct in the field.
The gradual, untracked shift in the meaning of a term or construct across documents, teams, or time. One of the most common and costly forms of intellectual continuity failure. NodeRail prevents it through canonical definitions with version history.
The traceable chain of versions of a node, from its origin to its current state. Version lineage preserves the authorship trail and allows anyone to see how a concept evolved, who contributed, and when each change was made.
The structured system of definitions, governance, contribution standards, and citation norms that allows a field of knowledge to grow coherently over time. A Field node on NodeRail is the primary unit of field infrastructure.
The gradual misalignment of a classification system as new terms are added without governance. Related to concept drift but applies to the structure of categories, not just individual terms.
The explicit, typed relationship between two nodes. NodeRail supports four link types: supports, depends-on, conflicts-with, and supersedes. Links are directional, versioned, and part of the node's permanent record.
The responsibility for maintaining, updating, and governing a node over time. A steward is not necessarily the original author, but is accountable for the node's continuity. Stewardship separates knowledge from its originator.
The accumulated gap between the intellectual work that has been done and the intellectual work that has been properly documented, versioned, and made citable. Like technical debt, continuity debt grows silently and becomes expensive to resolve.
The minimum requirements for a node to be considered continuity-grade. Every node published on NodeRail must meet all six criteria.
NodeRail Continuity Standard v0.1 · Published 2026
The node uses the official NodeRail template for its type (Field, Framework, Measurement, or Project). Freeform documents are not accepted. Structure is what makes nodes connectable and comparable across the platform.
The node has a semantic version number (e.g. v1.0.0) and a change log entry for every version increment. The version history is preserved in Git and is permanently accessible.
The node has a named author and a named steward. Authorship is never anonymous. If the author and steward are different people, both are named and their roles are explicit.
The node has a permanent DOI issued via Zenodo on every stable release. The DOI resolves to the archived snapshot of the node at that version. The DOI is permanent and will resolve for decades.
The node has at least one typed link to another node in its field. Links use one of the four NodeRail link types: supports, depends-on, conflicts-with, or supersedes. Isolated nodes are not continuity-grade.
The node has a Continuation Hook: a structured section that explicitly documents what was established, what remains unresolved, and what the next contributor should explore. This is required for all node types, not just Project nodes.
Common questions about NodeRail, answered directly.
NodeRail is versioned knowledge infrastructure. It is a system for publishing, linking, and preserving intellectual work in structured units called nodes, each with a permanent identifier, a version history, and an explicit lineage back to its origin. It is not a wiki, a note-taking app, a research database, or a CMS.
Wikis and docs platforms store text. NodeRail stores structured intellectual units (nodes) with version lineage, DOI citation, governance metadata, and explicit typed links between concepts. Every node is citable, forkable, and traceable to its origin. Wikis are designed for retrieval. NodeRail is designed for compounding.
NodeRail uses Git as its version control backbone, but it is not a code repository. The node templates, DOI integration, governance model, and link types are all specific to intellectual work. GitHub stores code. NodeRail stores knowledge infrastructure with academic citation built in.
NodeRail is built for researchers building new fields, practitioners documenting frameworks and methods, students publishing capstone and project work, universities that need research output to compound across cohorts, and organisations that need institutional knowledge to persist rather than reset.
A Digital Object Identifier (DOI) is a permanent identifier for a digital object. Unlike URLs, DOIs never break. They are indexed in academic databases, recognised by citation managers, and resolve permanently. When your node has a DOI, it can be cited in academic papers, grant applications, and other formal contexts — and that citation will always resolve to the correct version of your work.
A Continuation Hook is a required section in every NodeRail node. It explicitly documents what was established in this node, what remains unresolved, and what the next contributor should explore. It is the mechanism that turns every piece of work into a starting point for the next one, rather than an endpoint that gets archived and forgotten.
The NodeRail platform infrastructure is publicly available on GitHub at github.com/Noderail/noderail. The platform itself is in early access. The governance model, node templates, and contribution standards are all publicly documented.
NodeRail is in early access. Submit a request at noderail.org/access and Gao Kabubi will review it personally. Access is not a gate — it is a handshake. The process takes less than five minutes.