Core Concepts

The ideas behind ergo-sbe's API design: why wire order is enforced at compile time, how exact buffer sizing works without heap allocation, when to use flyweights vs owned structs, and how composites achieve zero-copy access.

• Trust Boundary — try_from validates, wrap trusts
• Wire Order via Named Stages — calling asks before bids is a type error
• Buffer Sizing — stack-allocate the exact byte count before writing
• Flyweight vs Whole-Struct — decode in-place or materialise an owned DTO
• Composite Layout & Endianness — wire images, packed overlays, and why BE costs ~5%