EXPcalibur guide
One tile is read across rows and down columns. The same 64 body bytes support two independent readings The same 64 body bytes support two independent readings Tile 0 b o d y [ 0 . . 15 ] Tile 1 b o d y [ 16 . . 31 ] Tile 2 b o d y [ 32 . . 47 ] Tile 3 b o d y [ 48 . . 63 ] Tile 0 enlarged: each cell is one byte b 0 b 1 b 2 b 3 b 4 b 5 b 6 b 7 b 8 b 9 b 10 b 11 b 12 b 13 b 14 b 15 RowCursor · contiguousFor row 0, read b0, b1, b2, b3. Four rows in each tile produce row events. ColumnCursor · stride 4For column 0, read b0, b4, b8, b12. Four columns produce independent events. Host decision Each report must satisfy its own checks under one admitted context. A safe copy alone proves neither report valid. Four tiles × sixteen bytes = 64. Neither cursor consumes the other cursor’s parsed events. Diagram shows read order, not a byte pattern that satisfies the Entry verifier. The highlighted first row and first column share one cell but produce different four-byte records. The other three tiles follow the same layout. This depicts cursor order, not a successful Entry body.