Skip to content

docs+test(ladder): the module update ladder as a rule table; B1/B2/B4 — a platform roll keeps landed modules serving #6141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rbuergi merged 4 commits into from
Oct 5, 2026
Merged

docs+test(ladder): the module update ladder as a rule table; B1/B2/B4 — a platform roll keeps landed modules serving #6141

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6abd86f
docs+test(ladder): the module update ladder as a rule table; B1/B2/B4…
rbuergi Oct 5, 2026
28c8d83
docs(ladder): every row names its tests and PRs (#6139, #6116, #6140,…
rbuergi Oct 5, 2026
df87ab1
test(ladder): no pragma, no null-forgiving; B1 asserts the generation…
rbuergi Oct 5, 2026
665a86f
Merge branch 'main' into test/module-update-ladder
systemorph-com[bot] Oct 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions src/MeshWeaver.Documentation/Data/Architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,6 +363,7 @@ Each theme starts with its introductory page, followed by related architecture t
- [Module-Owned Siblings Ride](ModuleOwnedSiblingsRide)
- [The Module Platform Link Gate](ModulePlatformLinkGate)
- [The Platform Compatibility Ladder](PlatformCompatibilityLadder) — platform builds are backwards compatible within a major and a compatibility epoch, so plugin bytes built on N run unchanged on N+1; the floor/ceiling/epoch that bound it, the machine-checked break declaration, the API-break catalogue (static verdict vs what really happens at run time), the check that blocks every platform pull request on the deployed plugin set, and what no surface check can see
- [The Module Update Ladder — Rule Table](ModuleUpdateLadder) — the ladder written as rows a test can check (platform fixed while a module moves, platform rolls under unchanged modules, store copy against image copy, prebuilt adoption, seals, source sync, the control instance, the 2026-10-05 incident), each row tied to its policy, the code that decides it and the test that holds it, plus the ordered P/M matrix every instance is walked through
- [Rolling-Update Build Tolerance](RollingUpdateBuildTolerance) — why a rolling platform update recompiled Store/Plugin ten times in four minutes and blanked every instance behind "build did not settle within 30s" (two generations, one record, one framework identity per record), and the rules that let an instance render on the last build its process can load instead
- [The Module Publication Gate](ModulePublicationGate) — a bundle used to reach the live registry from inside its own pack leg, before the sibling suites, the portal-host shards, the compile-check and the Tests-area gate had reported; the hand-over moved downstream of the full source verdict, and what it refuses (failed, skipped, cancelled, missing, foreign-lane, substituted)
- [Live Module Update](LiveModuleUpdate) — a module update goes live in the running process by default: every module in its own collectible load context, the old generation swapped out and unloaded; a restart only when a module declares `restartRequired` or the live swap fails (policy `module-live-update-default`)
Expand Down
Loading