KampányMűvek / 14 September 2026
One command had to tell the truth about five sites
`fleet-status` could not be just another version list. Local source state, Engine commit, release, deployment and live-QA status had to appear together without reporting false success.
Situation
As more sites moved onto the same Engine, it became increasingly difficult to keep track of which repository was clean, which Engine artifact it used, what had been released, whether deployment had succeeded and whether the same revision was actually live. An answer such as 'package.json says alpha.9' was no longer useful because it said nothing about production reality.
Approach
We built a fleet registry and `make fleet-status` to assemble state from several sources. Early versions produced false positives, so the source-of-truth and advisory logic were separated and corrected. A live release fingerprint was added later so the artifact actually being served could be compared with the expected release.
Outcome
Platform state became visible in one place, both machine-readable and easy for a human to scan. The command now shows not only which Engine each site expects, but also the state of its release, deployment and live verification.