Expand description
The compile-time payload: everything the binary serves or lands.
include_dir! embeds each authored root at compile time, so the binary
and the canon it carries cannot drift. Which roots exist is declared
once, in crate::payload_roots, read here, by build.rs for change
tracking, and by the packaging test; a test below holds this module to
that inventory.
Re-exports§
pub use crate::payload_roots::PAYLOAD_ROOTS;
Constants§
- SENTINEL
- The sentinel marker a landed file may carry;
rk init --applyreports every line holding one so nothing lands half-configured silently.
Statics§
- BINDINGS
- The per-technology bindings.
- BLOCKS
- The whole texts the binary writes outside
snippets/. - FORGES
- The per-forge documents answering the fifth axis.
- LICENSE
- The root license statement naming both halves.
- LICENSE_
CC_ BY - The CC BY 4.0 text covering the method.
- LICENSE_
MIT - The MIT text covering the distribution.
- METHOD
- The technology-agnostic method chapters.
- RUNBOOKS
- The human-facing runbooks
rk guiderenders. - SETUP
- The setup scripts, one subtree per forge, executed by
rk setupand landed nowhere. - SKILLS
- The agent skills, one directory per skill.
- SKILL_
SHARED - The artifacts every skill shares, installed once outside the skill roots.
- SNIPPETS
- The deterministic files
rk initlands, one subtree per technology, laid out exactly as they land in a target repository. - VERSIONS
- The pinned-tool registry.
Functions§
- artifacts
- Every artifact the payload carries, root by root in inventory order, sorted by path within each root.
- root_
files - The files one payload root carries, as
(path, bytes)with the path carrying the root as its first segment, orNonefor a name the inventory does not declare.