Expand description
Config-driven BlobStore selection (ADR-111 Amendment 2).
khive-db cannot parse khive.toml itself (it sits below khive-runtime
in the crate dependency chain), so the fs-vs-s3 selector lives here, one
layer up, where KhiveConfig is already parsed. This is the choke point
every boot path (single- and multi-backend) resolves the configured blob
store through, so the two never drift onto different construction logic.
Structs§
- Blob
Hydrator - Runtime-owned bounded blob hydration with weighted raw-byte admission.
- Verified
Blob - One verified raw blob buffer and its aggregate admission lease.
Enums§
- Governed
Blob Error - Error from
BlobHydrator::resolve_for_governing_backend, split so boot can distinguish store resolution failures (which fall back to “no blob configured” when[storage.blob]is absent) from budget pairing failures (always fatal).
Constants§
- DEFAULT_
BLOB_ HYDRATION_ BYTES - Default process-local admission budget for resident verified blob buffers.
Functions§
- resolve_
blob_ store - Resolve the
BlobStorethisbackendshould use, percfg.storage.blob. - resolve_
blob_ store_ for_ mode - Resolve the configured store for one pack runtime’s effective access mode.