mc-heartbeat-mc-dispatcher-are-systemd-not-cron
Both mc-heartbeat and mc-dispatcher run as systemd services, not crontab entries. Architecture.md and the enterprise skill must reflect this — listing them under cron jobs creates operational confusion. The dispatcher resolves agent IDs dynamically via the MC API at startup (name→id caching) to avoid brittle hardcoded integer IDs that break when agents are re-registered.
Related
- docker
claude-code-to-nova-enterprise-capability-expansion-20260323(archived)- hybrid-triggerdev-cloud-fargate-over-pure-self-hosted-decisi
- 2026-04-04-oracle-001-self-architecture-analysis
- claude-code-as-ops-team-invalidates-managed-services-choice
- heartbeat-daemon-hardcoded-agent-ids-breaks-on-redeploy
- heartbeat-daemon-over-crontab-for-sub-minute-intervals
- hardcoded-agent-ids-in-heartbeat-daemon-break-on-db-recreate
- heartbeat-daemon-must-resolve-agent-ids-dynamically-at-start
- mc-heartbeat-mc-dispatcher-run-as-systemd-not-crontab