Exact finite meaning of prepared native instances #
The native catalogue enumerates the existing residue classes, chunks and pieces. These results
identify its actual output count and per-instance records with that finite construction. Matrix
meaning and padding reuse MatrixSpec and its existing writer-entry formulas.
The consumer extension connects these cells to finite adjacency, deriving piece coordinates and the padding bound.
Main results #
PreparationSpec.count_eq_card: the actual output counter is the finite instance cardinality.PreparationSpec.index_unique: unique existing finite coordinates for each output record.PreparationSpec.instance_readback: exact query slices and matrices at every finite index.
The counter of an actual native output is exactly the existing finite instance count. The weight-array correspondence concerns only the original A–B input, not supplied classes.
Every occupied native instance slot has exactly one existing finite class/chunk/piece index. This uses the standard dependent finite-sum enumeration and ordinary division/remainder; there is no second definition of a residue class or finite instance.
Each existing finite instance is stored at its computed native ordinal. Its six-word
record contains the exact residue, piece, existing query-chunk pointer/cardinality and both
matrix pointers. The matrix readback reuses the same entry formulas as MatrixSpec, including
their modular adjacency and zero-padding results.