Controller Logic that Manages Godon Systemtender Lifecycles
- Systemtender lifecycles — create, start/stop, update, purge; the shutdown-signaling state table; the systemtender metadata registry.
- Credentials and targets — catalog tables for secrets and target hosts.
- Steerwishes — the declared-outcome registry: wish records plus their
lifecycle events (declared, planned, refused, acted, landed, missed,
re_opened, closed). State derives from the latest event, never stored.
Windmill scripts:
steerwish_create,steerwish_get,steerwishes_get,steerwish_close(folderf/controller/).
The controller owns the wish OBJECT and its lifecycle — identity, coordinates (outcome, band, limits, budget, regime), events, timestamps, adoption lookup, purge cascade. causal owns the steering CALCULATION keyed by wish id — the plan, bars, refusals, verdict stamps, vigilance. The controller asks, never computes: it holds the wish as it holds systemtenders without optimizing and curves without measuring.