In brief
Public source-path map for implementation, KIPs, docs, tooling, and research sources.
Purpose#
This folder is the public map from guide claims to upstream evidence. It intentionally avoids local storage citations. Local files can be useful during study, but public guide claims must resolve to official websites, GitHub repositories, papers, release pages, docs pages, or timestamped public observations.
Source Classes#
| Class | Use for | Boundary |
|---|---|---|
| Rusty Kaspa implementation | Current protocol/source behavior when checked at the relevant commit or current source state. | Needs refresh before broad current wording. |
| KIPs | Accepted, proposed, or historical design depending on status. | Open PR text is proposed until merged/accepted evidence exists. |
| Release notes | Versioned current or historical behavior. | Does not replace source review for internals. |
| Kaspa documentation | Orientation, workflow, and docs-backed behavior. | Kaspa documentation is not sole authority for implementation internals. |
| Tooling repos | SilverScript/vProgs/tool behavior. | Tooling does not prove L1 readiness by itself. |
| Papers/upstream ZK docs | Research background and proof-system context. | Research does not equal deployed behavior. |
Expanded Source Path Method#
Source path pages exist to stop the guide from treating broad citations as proof. A public source ID should tell the reader which upstream location matters and what kind of claim that source can support. Implementation source can support implementation behavior when the exact path is read. A release note can support versioned release status. A KIP can support proposal or accepted design depending on status. Official docs can support public documentation posture. Tooling repositories can support tooling behavior. Papers support research background.
When a guide page is challenged, this folder should help a reader find the authority class before arguing about wording. If the exact source has not been read, the claim should remain in Open Questions or be rewritten narrowly.