Expand description
Workspace-internal replay and lifecycle semantics for Prikk.
During replay-boundary stabilization this crate is not a public API commitment. It owns semantic
replay/lifecycle substrate types while repository layout, refs, WAL, object storage,
verification, doctor, and store-backed resolver construction remain in prikk-store.
Structs§
- Live
Node - A node currently live in the reconstructed clean tree.
- Node
Lifecycle State - Replay-derived node lifecycle index. Not a root of trust (FDD-02 §12).
- Repo
Path - A validated repository-relative path.
- Tombstone
- The latest deletion preimage retained per node for restoration-equivalence.
Enums§
- Node
Content - Content-payload identity of a node (FDD-03 §10.2
node_payload).
Functions§
- ensure_
node_ id_ nonzero - Reject the reserved all-zero
node_idat every seeding boundary (erratum P1-3), matching the object decoder’sNodeId::try_from_bytesrule. - validate_
kind_ content_ shape - Structural kind/content discriminator (erratum P1/P2): no node or tombstone may
hold a payload whose kind disagrees with its content. Shared by
create_node,seed_live_node, andseed_tombstoneso the discriminator cannot diverge. Blob- kind matching (TextFile -> Text,BinaryFile -> Binary) stays at the blob- resolution boundary, since this substrate stores onlyblob_id. - validate_
no_ path_ collisions - Reject duplicate paths and case-insensitive collisions.
- validate_
repo_ path - Validate that a path is safe as a repository-relative path.