RSPS Wiki
What Is an RSPS Source?
The human-readable code behind a project, and why a source-base name is not a complete feature specification.
Code before the running program
Source code is the set of instructions developers maintain before or alongside producing a runnable application. In RSPS conversation, “source” often means the server-side codebase, but the context may also involve client code.
A project name can refer to a starting codebase, a later fork or a heavily changed descendant. Record which version or revision of that project is being discussed.
Inheritance does not guarantee identical behaviour
Developers can change networking, combat, persistence and content after adopting a starting point. Two projects with the same ancestry may behave very differently. A source-base label is useful context, but it is not an audit.
When assessing a claim, ask whether it refers to original code, a particular release or a later modification. A statement about one descendant should not automatically be attributed to the original project.
Historical claims need their own evidence
Claims about the first release, original author or influence of a codebase should be tied to surviving release records and other sources. Later recollections can be valuable, but they should be identified as recollections.
Our historical drafts use this distinction so that a popular project name does not become a shortcut for unsupported dates or attribution.