The subject convention was compiled into two binaries, the runtime and the controller, and ADR 0159 extended it in both. This record moves the deciding to one place: the controller publishes each assignment a membership — what it serves and where, in which queue, its seat verbs, where its events land, what it may reach — on mesh.assignment.<node>.<module>, last per subject; the runtime serves exactly that; the grant is the same membership read the other way; the console's listing carries subjects. One bootstrap rule remains, the membership's own subject. Whether an instance answers for the module or only for its machine becomes the mesh's decision, from one fact a definition may state (instances interchangeable). Designs 25, 32, 33 and 34 carry the notes. Code follows in mesh-controller, mesh-tools and the SDK. Checks pass.
The subject convention was compiled into two binaries, the runtime and the controller, and ADR 0159 extended it in both. This record moves the deciding to one place: the controller publishes each assignment a membership — what it serves and where, in which queue, its seat verbs, where its events land, what it may reach — on `mesh.assignment.<node>.<module>`, last per subject; the runtime serves exactly that; the grant is the same membership read the other way; the console's listing carries subjects. One bootstrap rule remains, the membership's own subject. Whether an instance answers for the module or only for its machine becomes the mesh's decision, from one fact a definition may state (instances interchangeable). Designs 25, 32, 33 and 34 carry the notes. Code follows in mesh-controller, mesh-tools and the SDK. Checks pass.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The subject convention was compiled into two binaries, the runtime and the controller, and ADR 0159 extended it in both. This record moves the deciding to one place: the controller publishes each assignment a membership — what it serves and where, in which queue, its seat verbs, where its events land, what it may reach — on
mesh.assignment.<node>.<module>, last per subject; the runtime serves exactly that; the grant is the same membership read the other way; the console's listing carries subjects. One bootstrap rule remains, the membership's own subject. Whether an instance answers for the module or only for its machine becomes the mesh's decision, from one fact a definition may state (instances interchangeable). Designs 25, 32, 33 and 34 carry the notes. Code follows in mesh-controller, mesh-tools and the SDK. Checks pass.