Mack Palomäki

Mack Palomäki is the founder of Ljusa Tider AB, a consultant working with Plone, multilingual content, regulated documentation, and AI-assisted development.

At Plone Conference 2025 he presented two talks: one on standards-driven AI for Plone and Volto interface translations, and one on AI-driven documentation workflows. The first became Project Polyglot, whose translation corpus was merged into Nick in June 2026.

Earlier in his career he contributed to Nordic and international standards in satellite communications, GSM, and mobile Internet, and holds three patents in multi-stakeholder brokering, delegated trust, and authentication. He has led technology products and organisations in Europe and Asia across mobile payments, RFID, medical diagnostics, manufacturing, and regulated environments. He is based in Sweden.

en
In a Plone translation catalogue shipping today there is a string that asserts something its source does not — placeholder counts match, length is normal, every automated check passes, and only a human reading it would notice. If translations ever have to carry legal weight — and in the EU, safety information must, in up to 23 official languages — that is exactly the class of bug that matters. For more than a year I have run Nick and Volto in production as the backend and frontend of a regulated-documentation platform: 358,627 translations across 71 languages in one database-backed model — merged into Nick through the release team in June 2026 — guarded by a meaning-drift detector that structural QC cannot replace, with the AI kept on local hardware as a written architectural rule, not a preference. This talk is what a year of running that stack for real taught me, including the failures I paid for — and it ends with a question I want the room's answer to: how an AI-assisted corpus should live alongside Weblate.
Frontend
Backend
Integrator
Intermediate
en
Most compliance systems begin with documents, and most of them end as document graveyards. The relationships are what matter, and folders cannot express them. A regulation imposes an obligation. A policy interprets it. A control implements the policy. A risk assessment determines where the control is needed. Evidence demonstrates that the control exists and still operates. Break any link and an auditor's question — show me why this control exists, and prove it worked — has no answer.
Frontend
Backend
Integrator
Business
Other
Intermediate