pure/docs/research/115-apps-that-change.md, branch masterVerified execution runtime unifying state, persistence, and replication.
http://git.yeowoo.org/pure/atom?h=master2026-10-19T09:01:53Z115: the modules replaced are freed (0 bytes a change over 4,000, was 19,284), how, what checks it (586 of 600 loads at a freed address, answers right; ASan clean), what a mutant comparing addresses showed (nothing: requests hold their module and freeing waits a pass), the push group woken again, the bindings left (24 B an input a module); the bank's queries within 0.4% (s50, s51); CHECKPOINT's remaining list without it2026-10-19T09:01:53Zeunhhunecpition205@gmail.com2026-10-19T09:01:53Zurn:sha1:de1c3dd822c7bd6ae01c510a53372445b1b993eaSay that reading the code found stage 3's two races, and how a host changes apps2026-10-04T10:11:00Zeunhhunecpition205@gmail.com2026-10-04T10:11:00Zurn:sha1:91bb0dc2f471f7fb90d7d5bc08c87805dceac326
The use after free in local_done and the owner's lock made after another
app's outlet used it were found reading the code, not by the check,
which passed with both before it was made to change senders (115, 017).
The usage now says changed lines change in place unless their store
moved; and 115 names the path no check takes: a module refused while
changing in place.
Say what apps that change on a running host showed (017 stage 3, research 115)2026-10-04T10:07:55Zeunhhunecpition205@gmail.com2026-10-04T10:07:55Zurn:sha1:52e51e4231f2e119c97826ae6d6e2f2af0da0c58
Changing an app in place keeps a million items' app answering but for
1.12 ms (a host restart: 150 ms; stopping and starting it again from its
store, as first built, 150.4 ms), 171.5 ms when its records change shape
(332 ms). Another app's p99 stays 0.97 times as it was while one changes
every 0.2 s; a host of one app is as it was (TPC-C +0.7%, instructions
at most +0.02%); each module change leaves 19 KB. 030 holds the windows
of both builds, the isolation, the pairs, the counts and the memory.