Problem
Persistent agent services independently reimplemented heartbeat, restart, acknowledgement, recovery, receipt and state mechanics.
ENGINEERING CASE STUDY
How GHOUL became the shared runtime host.
GHOUL — Governed Host for Operational Understanding & Lifecycles — is the common host for persistent agent identity, lifecycle, supervision, recovery and receipts. This case study traces why those mechanics were extracted from independently evolved AVSFT services.
OVERVIEW
GHOUL runtime host
GHOUL — Governed Host for Operational Understanding & Lifecycles — is the common host for persistent agent identity, lifecycle, supervision, recovery and receipts. This case study traces why those mechanics were extracted from independently evolved AVSFT services.
Evidence
Lineage review found the same runtime mechanics recurring across separately evolved services while their operating roles and authority remained different.
Change
The recurring host mechanics were extracted into GHOUL so each resident system could share a durable runtime body without duplicating the same infrastructure.
Boundary
GHOUL owns shared host mechanics. It does not inherit the role-specific authority of the systems running on it.