Expand description
Lineage rules — the cross-field checks that bind one passport to another.
Top-level rather than under a product group because the edges are envelope fields every product group carries, and because the linkage obligation is framework-level: ESPR (EU) 2024/1781 Art. 11(d) requires that “where a new digital product passport is created for a product that already has a digital product passport, the new digital product passport shall be linked to the original digital product passport or passports.”
The operation vocabulary those edges use is battery-specific
(Reg. (EU) 2023/1542 Art. 77(7)), but the shape of the rule is not, and
filing it under batteries would imply only batteries can have second-life
lineage — which the envelope contradicts.
Re-exports§
pub use consent::check_derivation_consent;pub use consistency::check_life_status_consistency;pub use finding::ConsentDefect;pub use finding::ConsentFinding;pub use input::DerivationEdge;pub use input::TransferEvidence;pub use status_defect::StatusDefect;
Modules§
- consent
- Does a second-life claim carry the predecessor operator’s authorisation?
- consistency
- Does a passport’s life status agree with the edges that produced it?
- finding
- What the lineage consent rule reports about an unsupported edge.
- input
- Borrowing views a caller supplies to the lineage consent rule.
- status_
defect - What the life-status consistency rule reports.