What we built. Every version of a case is now kept under the hash of its own bytes. A receipt is rebuilt from the bytes the shift was actually played on, not from whatever the case has become since. Replay those same bytes and you get the same receipt back.
What we learned. When the bytes are gone, the receipt shows nothing rather than a chart derived from today's version of the case. Nobody's mark improves, and we did not soften the marking. We held ourselves to it. Just after midnight on 26 September, 85 of 95 anchored shifts replayed to the exact leaf the chain holds, and 10 did not. Five of the ten were played on a case version that was overwritten on 23 September; their receipts show nothing, as designed. The other five still had their bytes, and the fault was ours: the live shift and its replay disagreed about one rule, an idle cap. That fix went out at 01:06, and the same check then read 90 of 97 proved, with two of those five still open. (Both reads are from the ward's own integrity check, not yet public; times are Bangkok.)
What broke, in public. A renamed field left the ward with no new patients for 14 hours. We wrote a new version over a case the chain already had a shift against, and put the original back, byte for byte, in 14 minutes. Our own test browsers held the ward's connections for days and turned real visitors away. Three incidents, all written down.
What's next. A security check, an audit, the road to mainnet, and an explanation of how it all works.
Ward: world.vitals.academy · demo (2 min, live product): https://youtu.be/JEoNwBoIqZ0 · weekly update (1 min): https://youtu.be/UONdHIoWkJQ
Give feedback to the team
Your message is private to you and the Vitals World team.
Create an account to send feedbackAfter signup, you can write a private message with this update attached.
