KampányMűvek / 15 September 2026
Documentation, fleet upgrades and the CI supply chain all got stricter on the same day
The platform did not mature because of a new frontend feature, but because of three less visible layers: bilingual documentation parity, rollback-safe fleet upgrades and pinned release infrastructure.
Situation
The Engine was evolving quickly, and three different forms of debt surfaced at once. Hungarian and English documentation could drift apart, a multi-site upgrade could leave the fleet partially upgraded after a failure, and GitHub Actions plus live-QA dependencies could rely on changing external versions. None of these problems looks dramatic until the day one of them causes an incident.
Approach
We introduced documentation parity checks and a bilingual documentation UI, added preflight and rollback to fleet upgrades, pinned production workflow actions to exact commit SHAs, made SSH host trust explicit and locked the live-QA dependency graph. We also tested preservation of hidden managed files in release artifacts.
Outcome
The platform now depends less on implicit environment state and human memory. Documentation drift, half-finished fleet upgrades and external CI dependency drift are all visible earlier or controlled more tightly. Together, those changes improved operability far more than another UI component would have.