Canonical Models

A canonical table has one schema, many protocols, and a lineage key back to the raw log. It is a union, not a lowest-common-denominator dump.

Protocol tables are accurate and unusable across protocols. Canonical tables are usable and must not lose the protocol. The protocol column is required.

Domain fields are the intersection of what every decoder can populate honestly. Protocol-specific extras stay on the protocol table.

If a canonical table cannot be rebuilt from a block range of raw + decoded tables, it does not ship.