Origins and reuse¶
The formal research began with a study of Netrunner, using comprehensive rules version 26.03 maintained by Null Signal Games. This reference presents neutral formal mechanisms and original explanations. It preserves the distinctions and limits of the selected models rather than treating a change of vocabulary as new evidence.
Netrunner is a trademark of R. Talsorian Games, Inc. This independent project is not affiliated with or endorsed by the rights holder. The source maintainer’s rules site is the route to the maintained source-game rules.
Formal specifications and configurations¶
Project-authored TLA+ specifications and their TLC model configurations are offered under CC0 1.0 Universal. This also covers the original TLA+ examples embedded in these documents.
The project’s position is that these purely functional descriptions of mechanics fall outside copyright protection. To the extent copyright or related rights nevertheless subsist in the contributors’ material, the contributors dedicate those rights under CC0. If the dedication is ineffective or unavailable, CC0’s fallback licence applies. If neither dedication nor licence can be granted, the contributors promise not to sue for using, copying, modifying or distributing their contributions, and not to assert copyright or related rights they control against those activities.
This is the project’s position and grant for rights its contributors control. It does not dedicate another party’s expression, artwork or trademarks, and it does not make a worldwide legal determination. The recorded rules-versus-expression rationale refers to 17 U.S.C. § 102(b) and DaVinci Editrice v. ZiKo Games, 183 F. Supp. 3d 820 (S.D. Tex. 2016). Those references provide context; readers do not need them to use the formal reference.
Explanations and diagrams¶
Original explanatory prose, analysis and diagrams use the Project Document Licence, which is modelled on the W3C Document License but has project-specific terms. These documents are not covered by the specifications’ CC0 dedication merely because they contain formal examples.
You may redistribute unchanged documents or identified unchanged excerpts while retaining the applicable notice, licence or licence link, source reference, version and review status. The terms also permit proposed edits and translations for review, and limited adaptation into implementation-supporting documentation. They do not grant general permission to publish an unapproved altered reference entry. Read the full terms for their scope and exceptions.
Implementation and example code¶
Project-authored implementation tooling and executable implementation examples use the MIT License. TLA+ specifications and examples retain CC0. Surrounding explanatory prose retains the document terms. Third-party tools and source material retain their own notices; file format alone does not change the applicable licence.
Propose a correction¶
Identify the document or definition and the release you read. Prepare a patch, proposed replacement passage or issue report explaining the problem and supporting evidence. Mark edited reference text as a proposal, preserve its source and review history, and submit it to the project maintainer through the project’s review process.
Submitting an edit does not make it an approved reference. Accepted changes become a subsequent version with the appropriate review and checking evidence. Contributors retain ownership and provide the project permission to incorporate their submissions under the applicable component terms; they must identify third-party material and have the rights needed for inclusion.
Preserve the claim’s context¶
Keep the release and input identity with a saved source bundle or copied result. A later source change needs its own evidence rather than a rewritten historical receipt. The evidence guide explains how to distinguish a specification, a bounded result and an implementation claim.