Map Idunn managed service policy boundary

This commit is contained in:
Meta Vens 2026-07-12 12:51:12 +01:00
commit bf7dd9fc81
5 changed files with 28 additions and 3 deletions

View file

@ -362,6 +362,12 @@ that store with empty stderr and lifecycle receipts. The attached PowerShell
vigil is deleted. The remaining service boundary is durable Idunn policy and
operator readback: advertise/configure the heartbeat service through typed
daemon state so restart intent survives beyond one explicit `service-launch`.
Source inspection corrected the proposed owner: standing daemon restart policy
requires a topology daemon and liveness status, while heartbeat is an
Idunn-managed child service. The durable owner must therefore be a typed
managed-service desired-state document keyed by service id. It delegates all
starts to the existing service lifecycle primitive and must not invent an
`epiphany-daemon-heartbeat` topology identity.
This map must change when ownership changes. Historical scars belong in git,
evidence, or an explicitly archived note—not in the machine's proprioception.

View file

@ -2202,6 +2202,12 @@ had empty stderr and compact clean closure receipts. Lifecycle receipt ids are
The old `tools/epiphany_ruminate_until.ps1` attached loop is deleted. Next give
Idunn a durable typed heartbeat service policy/readback so restart intent and
current pulse status survive beyond an explicit operator `service-launch`.
Do not reuse `epiphany.cultmesh.daemon_restart_policy` for this. Inspection of
`epiphany-daemon-supervisor::write_policy` and scheduler reconciliation shows
that family requires a standing topology daemon plus daemon liveness status.
Heartbeat is an Idunn-managed child service. Add a typed managed-service
desired-state policy keyed by service id, and have reconciliation delegate to
the existing `service-launch` lifecycle owner.
## Immediate Re-entry Instruction

View file

@ -102,8 +102,12 @@ refusals, resumes from the same persisted store, and can be launched again by
Idunn without duplicate pending turns. The heartbeat binary owns pulse timing
and typed heartbeat receipts. Idunn owns child launch, stdout/stderr artifacts,
and lifecycle receipts. Self remains only the routing organ consuming heartbeat
pressure. The remaining step is durable Idunn restart policy and compact
operator readback for the heartbeat service, not another explicit launch smoke.
pressure. Existing `epiphany.cultmesh.daemon_restart_policy` is not the right
owner for the remaining step: it is keyed to standing topology daemons and
their liveness status. The heartbeat loop is an Idunn-managed child service.
The missing owner is a typed managed-service desired-state policy keyed by
service id, plus compact operator readback; do not forge an eighth standing
daemon to reuse the daemon policy table.
### Owner
@ -128,6 +132,15 @@ operator readback for the heartbeat service, not another explicit launch smoke.
- Idunn service lifecycle receipt and sealed stdout/stderr artifacts;
- explicit clean shutdown or failure status.
### Durable service policy requirement
Add one typed Idunn managed-service policy with owner `Idunn` and key
`service_id`. It may read the desired command/args/cwd, enabled state, restart
mode, cooldown/backoff, expected heartbeat store, stdout/stderr artifact refs,
and latest lifecycle receipt. It emits desired-state readback and delegates
every actual start/restart to the existing service lifecycle launch primitive.
It does not own heartbeat scheduling state, daemon topology, or routine output.
### Forbidden writers
- PowerShell wall-clock loops deciding heartbeat truth;