In brief
This page teaches the source hierarchy used by the v1 guide so public wiki prose does not confuse orientation, implementation, releases, KIPs, papers, tools, and local experience.
What this page explains#
This page teaches the source hierarchy used by the v1 guide so public wiki prose does not confuse orientation, implementation, releases, KIPs, papers, tools, and local experience. This page sits in Foundations. It gives the topic a plain-language handle first, then shows the working idea, the mechanism, the source trail, and any limits that still matter. This category gives the reader durable handles before any source walk begins. It keeps identity, motivation, vocabulary, history, and first practical routes separate so a later consensus or developer page does not have to carry every introduction at once.
The writing follows a simple Kaspa documentation pattern: answer the practical question first, then link outward for details. The closest public sources for this page are WIKI-HOW-TO-HELP, WIKI-DEVELOPERS-KB, RK-REPO, KIPS-REPO, DOC-TOCCATA-REFERENCES. Local notes can help choose what to explain, but public-facing references resolve to upstream websites, repositories, papers, release pages, or docs.
How to think about it#
The practical model starts by naming the layer that owns the topic: wallet use, node operation, consensus, transaction validation, Toccata script behavior, tooling, or research. From there, the page shows which public source can support the explanation and where the explanation becomes incomplete.
For How This Guide Uses Sources, the model is built around these anchors: implementation and merged KIPs are the strongest sources for current behavior; release notes support rollout and version status; official docs and wiki pages orient readers; papers and research notes stay labeled research; local project lessons are useful only after cross-checking. This model is useful, but it does not encode every constant, branch, error type, or edge case. Those details belong in the source path and the source notes.
How it works#
1. implementation and merged KIPs are the strongest sources for current behavior. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
2. release notes support rollout and version status. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
3. official docs and wiki pages orient readers. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
4. papers and research notes stay labeled research. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
5. local project lessons are useful only after cross-checking. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
This mechanism section is intentionally shallow-to-deep: it gives the first usable explanation, then names the later page where source-level mechanics belong. Foundation pages must not smuggle in covenant, ZK, or readiness claims unless the Source List and Source Notes support that exact bridge.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check implementation and merged KIPs are the strongest sources for current behavior. | Use WIKI-HOW-TO-HELP, WIKI-DEVELOPERS-KB, RK-REPO; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 2 | Check release notes support rollout and version status. | Use WIKI-HOW-TO-HELP, WIKI-DEVELOPERS-KB, RK-REPO; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 3 | Check official docs and wiki pages orient readers. | Use WIKI-HOW-TO-HELP, WIKI-DEVELOPERS-KB, RK-REPO; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 4 | Check papers and research notes stay labeled research. | Use WIKI-HOW-TO-HELP, WIKI-DEVELOPERS-KB, RK-REPO; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 5 | Check local project lessons are useful only after cross-checking. | Use WIKI-HOW-TO-HELP, WIKI-DEVELOPERS-KB, RK-REPO; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
When using this page for a wiki article, keep orientation separate from mechanics. The page can name the path and the next concept, but detailed wallet, node, mining, consensus, transaction, or Toccata behavior belongs in the downstream page that carries the stronger Source List.
Related Pages#
- background-reading
- foundations
- kaspa-docs-flow-and-contribution-style