Assessment 229: a meaningful suffix pays learned access
13 October 2026. Written construction 78, a sufficient native subclass argument. No root admission or external originality claim.
Subsequent progress: construction 80 supplies growing-delay envelopes and bounded speculative readout. This dated review retains its original scope and evidence. Current research target.
Contents
Result and prior controls
The complete proof handles a growing family of independent namespace maps. One source activation dictionary remains shared. Each target suffix has equal halves a,z; the namespace learns an arbitrary partial map sigma(a), and the foreign owner is 1 sigma(a) z. The actual second half pays both the released prefix lookup and suffix replay. The right block supplies and validates every map entry through ordinary records.
The first attempted route, input-built prefix-tree automorphisms, is already section 16’s bounded-prefix-ambiguity mechanism. Its adaptation to the current syntax requires explicitly decoding store names during their actual fields. That corollary is retained as a control and counted neither as construction 78 nor as a separate result.
The new schedule admits prefix reversal followed by unchanged suffix even when no fixed observed ambiguity bound covers the decoded one-tick clock contract. This is a scoped comparison, not separation from every older theorem. The second half is meaningful owner-key data, not padding. Arbitrary transformations whose useful result arrives only at the endpoint remain unresolved.
Independent adversarial review
The reviewer checked the ordinary-input producer, odd-width half-ruler, immutable provisional map updates, cross-group consistency, current-source routing, actual-incidence masks and final-symbol schedule. The critical implementation obligations are explicit: learn r from the first actual store, check conflicts while the suffix arrives, preserve separate primary/foreign support bits, and let unsupported short pins abandon unfinished service without a flush.
The service proof charges setup, r mapped-prefix steps, the stream switch and r suffix steps. Four normalized service slots per suffix bit cover 2r+2 steps, including r=1. Queue ingestion is a separate fixed lane. Each normalized slot expands to a fixed primitive batch; host running time is not the timing argument.
Independent evidence
The standalone checker uses direct relations and Horn closure independently of the representation model.
| Check | Completed count |
|---|---|
| Full and sparse instances, including noninjective maps | 1,164 |
| Retained-version query comparisons | 624,360 |
| Independent Horn closures | 52,380 |
| Rejected producer counterexamples | 6 |
| Unit-service cases, through half-width 512 | 1,024 |
| Growing reversal-width witnesses | 11 |
All pass. This is finite semantic and unit-service evidence, not a native simulator. The all-length construction is the resource argument.
Continuation and integration
Next remove the unchanged suffix condition. Every newly released lookup must have a charged remaining window, including setup, route length and replay of consumed bits. A fixed phase count alone does not establish that budget. Compare delayed-output transduction and persistent multi-index access in the next primary-proof review. Arbitrary whole-suffix permutations, arbitrary names and heterogeneous store service remain open.
The source, proof, checker and review remain in GitLab. The Site uses generated styled readings and an exact-download highlighted source reader. Construction 78 is a research note and overview update; established paper ordering and admission are unchanged. Scoped render checks, the repository test baseline and exact publication receipts are recorded in integration state. Browser viewport inspection is unavailable in the supported workflow.
Scheduled completion advances 133 to 134 and mathematical count 140 to 141 once. Window one, last reassessment 140, native construction 78. Next scheduled 135 is a substantive primary-proof review of at least two papers; editorial 138. Prior SAT/scaffold results remain intact. Installed legacy-writer retirement remains separate and unverified.