lab: a scheduled container fires on its cadence without gating (ADR 0053)

The bed that proves the scheduled-container primitive end to end. schedtest is the thinnest carrier of ADR 0053: one container marked schedule: "* * * * *" that appends a timestamp to a mounted data dir each time the host fires it -- no service, no listener, no provisioner, no runtime, no tools, no events. The three claims it proves, from the ADR's "How each claim is checked": installing the schedule leaves the node current WITHOUT a run (baseline captured right after settled, the deliberate inversion of run-once); the container fires on its cadence (a line beyond the baseline within ~150s); and it recurs (a second line on the next minute -- cadence, not a one-shot). schedtest serves and consumes nothing and carries no runtime, so it is not issued a broker account: module add -> assign -> one push is the whole sequence, no module issue. The tick image is a bare alpine served by the scenario's registry by digest. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
2026-09-06 14:20:54 +02:00
parent 399549db36
commit 76ecbaed85
2 changed files with 308 additions and 0 deletions
@@ -0,0 +1,49 @@
+# One machine that becomes a mesh and is then assigned schedtest — the bed that proves the
+# scheduled-container primitive (novox/hq ADR 0053) end to end.
+#
+# schedtest is the thinnest possible carrier of the ADR's claim: no service, no listener, no
+# provisioner, no runtime, no tools, no events — just a `container` marked `schedule: "* * * * *"`
+# that appends a timestamp line to a file in a mounted data directory each time the host fires it.
+# It is the recurring twin of the run-once bed (catalogue-mqtt), with the gating rule deliberately
+# reversed: installing the schedule must NOT run the container and must NOT gate convergence — the
+# node reports current as soon as the schedule is state that is present, and the clock (not the
+# apply) fires the runs thereafter.
+#
+# The sharp points this bed proves, straight from ADR 0053 "How each claim is checked":
+#   - installing it does not run it, and the node is current WITHOUT a run;
+#   - the container fires when the cron is due (top of the next minute);
+#   - it fires AGAIN on the following minute — recurrence, not a one-shot.
+#
+#   MESH_LAB_HOST_BINARY=.../mesh-host   MESH_LAB_MODULES=.../mesh-control/examples/modules
+#   alpine:latest must be in the local daemon; the scenario stocks it into its own registry and
+#   serves it by digest, which is what the scheduled container declares (via pinned("alpine")).
+#   There is no runtime image: schedtest carries no code of its own — the scheduled container is a
+#   bare alpine that runs `date >> /data/runs.log` and exits.
+scenario: schedule-tick
+
+segments:
+  hosting:
+    kind: public
+    cidr: [192.0.2.0/24]
+
+machines:
+  anchor:
+    at: { segment: hosting, address: [192.0.2.10] }
+    inbound: allow
+    memory: 3GiB
+    cpus: 2
+
+images:
+  # The first-node substrate: store, broker, control.
+  - postgres:17-alpine
+  - cloudamqp/lavinmq:latest
+  - mesh-control:development
+  # The tick container's image. schedtest has no runtime of its own — its scheduled container is a
+  # bare alpine that appends a timestamp and exits. alpine:latest must be in the local daemon; the
+  # scenario stocks it and serves it by digest, which is what the manifest pins via pinned("alpine").
+  - alpine:latest
+
+place:
+  # Only the host — schedtest has no mesh-runtime to place. The tick image is served by the
+  # scenario's registry and pulled by the host, not placed inside the machine.
+  all: [host]