Struct LedgerLineage 

pub struct LedgerLineage { /* private fields */ }

The lineage a served ledger hands on to the findings and facts restored from it (ctx_handoff pull). It exists for every ledger that was checked at creation, has at least one bound part and was just served — also one with an originless part: the marker decides whether the ledger as a whole may register a lineage, not whether a restored part gets a binding.

Implementations

impl LedgerLineage

pub fn carry( &self, part: &LedgerPart<'_>, index: usize, derived: &Item<'_>, ) -> Result<Option<Carried>, Withheld>

The binding of part — the element at index of its own list in the stored ledger — restored as derived.

Ok(None) — the item is restored originless — for an element that is not recorded as bound at that place: it had no binding at creation. A part is never upgraded because the ledger has bound siblings, nor because another element has the same text.

Err (store.ledger_authority_inconsistent) for an element that IS recorded at that place while part does not have the recorded digest: a known-bound element is refused, never restored unbound.

A recorded element is bound to the ledger’s joined source set (archive::bindings::carry_from). This over-approximates per item: the ledger keeps no per-item source lists, so the item is bound to ALL files of the ledger, not only to those of the finding or fact it once was. More sources have to hold, never fewer; the cost is that a restored item is withheld when an unrelated file of the same ledger changes.