Expand description
Tree manifests: {"schema":"khive-tree/v1","entries":[{path,ref,mode}]}.
A manifest is stored as one blob whose reference is the tree id. The serialization is canonical (entries sorted by path, compact JSON) so two runs that leave identical content produce identical tree references.
Structs§
- Path
Coverage - Exact-or-directory-prefix coverage, independent of manifest collision rules. Declarations are used as given; this does not validate or normalize them.
- Tree
Entry
Constants§
- MAX_
MANIFEST_ BYTES - Largest manifest the shared load path will read back.
- TREE_
SCHEMA
Functions§
- blob_
store - entries_
json - load
- Load a manifest by reference. An unknown reference or a non-manifest object is an error naming the reference.
- parse_
entries - Validate wire entries in input order: paths, refs, modes, duplicates, and
file/directory collisions.
exec.tree_putuses this for candidate manifests. - store
- Validate and store entries from any producer; returns a loadable tree ref.
- store_
from_ value - Validate and store a manifest built from wire entries; returns the tree ref.
- validate_
relative_ path - Validate a relative path: no empty components, no
./.., no leading/, no NUL, no backslash. Returns the normalized path. - verify_
blobs - Every entry’s blob must exist before materialization starts.