Manuscript VII-E-ST@1 · VII-E-ST.tex · section · d28d9c5d
Exact guard, locations, and finite reversible encoding
A four-face certificate and its supported 3+1 lift › Exact guard, locations, and finite reversible encoding · lines 1042–1084
VII-E-ST@1#eq:guard, VII-E-ST@1#eq:event-code
Let , denote the two regular transverse epochs and their event germs. At the event, retained central edge slots have zero length and realize the same junction; they are metadata, not regular embedded one-cells.
The forward event rule has guard
It changes the mode to one, spends one permission, and chooses the outgoing germ without advancing . A fixed abstract location map sends the incoming central slot and its endpoint labels to the outgoing event-junction slot; persistent labels are unchanged. No physical matter is transported through the patch by this metadata rule. If a spectator has an abstract location there, its location history is separately reserved.
Fix a finite parameter grid
stored exactly. Store rounded length reports only as reports. A rounded zero length cannot replace the exact guard: if , floor quantization at resolution reports zero for .
Let be a tuple of valid location words and its fixed event transport. On valid forward codewords prescribe
At zero, both central reports are zero and all common noncentral formulas agree, so the report words remain valid.
Displayed formulas in this passage
VII-E-ST@1#eq:guard · line 1051
VII-E-ST@1#eq:event-code · line 1076
unlabeled · line 1065