Archived
jschoubben
16faadfe52
Work breakdown 1.2. Two sessions run on the control-plane node — the node's own and the mesh's (novox/hq ADR 0026) — so a machine stopped being a usable answer to "whose licence is this". 14-model-access.md called per-module-per-machine "a step toward it and not it", and that is true of a worker: many run on one machine from one module, so the pair cannot name them apart. It is not true of a session. The two sessions are two modules — the same mechanism started in different context roots, and a context root is what a module delivers — so (node, module) tells them apart and nothing needed adding. Checked rather than argued: different licences on one machine, each with its own key, and a session on no licence is not handed the other's. The third test exists because a fault injection stayed silent. The first two put the sessions on different licences, so the licence alone disambiguates and the module argument is never load-bearing — removing it from the query changed nothing and everything still passed. Two sessions on the SAME licence is the case that needs the pair to be the identity: releasing one must leave the other, and a machine-shaped answer takes both.