 jschoubben
|
d93dc2628f
|
Adoption bed: the anchor keeps its host service, so a machine that reboots comes back holding itself; only the fresh-machine dry run goes without
|
2026-09-22 20:52:42 +02:00 |
|
|
jschoubben
|
23ca9cadad
|
Adoption bed: the machine the predecessor leaves also runs a container with no restart policy
|
2026-09-22 20:05:21 +02:00 |
|
|
jschoubben
|
204a226e36
|
Adoption bed: prove the guard rather than the found firewall, the runtime's own settings and a container with no restart policy, a held file not reverted once its writer stops, and the operator's rule outliving the mesh's opening
|
2026-09-22 19:53:47 +02:00 |
|
|
jschoubben
|
8d9e4bdb77
|
Adoption bed: the container probe asks the guard's promise, admitting the container interface through the found firewall for itself alone
|
2026-09-22 19:00:39 +02:00 |
|
|
jschoubben
|
3f224c2876
|
Adoption bed: an opening the operator's own rule answers is satisfied, and a failed container probe records its evidence
|
2026-09-22 18:49:06 +02:00 |
|
|
jschoubben
|
a53dc8c586
|
Adoption bed (in progress): a machine in use raised adopted, held, opened through its firewall, taken and converged (hq ADR 0100-0103)
|
2026-09-22 18:19:36 +02:00 |
|