Library says embark carrying the memory store forward is designed behaviour; embark says the memory store is not an embark family and does not travel

Library says embark carrying the memory store forward is designed behaviour; embark says the memory store is not an embark family and does not travel

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/04-surfaces/07-library.md:427 — "/abcd:embark carrying the store forward is designed behaviour"
• End B: .abcd/development/brief/04-surfaces/03-embark.md:126 — "Terminology, docs and the memory store are not embark families; they do not travel."

Library's composition note says embark carrying the store forward is designed behaviour, with the receiver running the store lint after unpacking. Embark says terminology, docs and the memory store are not embark families and do not travel, and its design-target section lists no memory carry. A builder cannot implement embark both to carry the store and to leave it behind.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 263.