Problem
Persistent agent services independently reimplemented heartbeat, restart, acknowledgment, recovery, receipt and state mechanics.
Engineering Case Study
How Ghoul became the shared runtime host.
Governed Host for Operational Understanding & Lifecycles (Ghoul) is the common host for persistent agent identity, lifecycle, supervision, recovery and receipts. This case study explains why those mechanics were extracted from independently evolved AVSFT services.
Ghoul runtime host
The same heartbeat, restart, acknowledgment, recovery and receipt mechanics kept reappearing in services that had evolved independently. Extracting them into one host removed the duplication without collapsing the distinct authority each resident system owns.
Evidence
Lineage review found the same runtime mechanics across separately evolved services with distinct roles and authority.
Change
Ghoul consolidates recurring host mechanics without duplicating infrastructure across each resident system.
Boundary
Ghoul owns shared host mechanics.It does not inherit the authority of the systems running on it.
Current Evidence
Identity, lifecycle, supervision, messaging, recovery and deterministic runtime behavior.
Ghoul does not inherit the role-specific authority of the systems it hosts.
One host replaces repeated per-service reimplementation of the same mechanics.