Why we apply TEAF to our own architecture before recommending it
Trustiatis is one of the first two UGM-Group subsidiaries to roll out TEAF, the enterprise architecture governance framework created by Mathieu Urbitsch. What that actually changes, and what's still to be confirmed.
We often talk, in these articles, about our clients' IT governance — how to structure an ERP/CRM before wiring automation into it, how to avoid architecture debt piling up unnoticed. Since early September 2026, we've been holding our own organization to the same discipline: Trustiatis is one of the first two UGM-Group subsidiaries to roll out TEAF (Temporal Enterprise Architecture Framework), the framework created by Mathieu Urbitsch.
What that actually changes
A documented governance layer, separate from the infrastructure itself: our servers, our Dolibarr/n8n stack and our Trusteco offers haven't changed. What changes is how an architecture decision — for instance our recent move of SaaS offers into Trusteco blocks integrated directly into trustiatis.com — now gets tracked in an Intent → Learning loop instead of documented informally across internal exchanges.
What isn't settled yet
TEAF requires its users to qualify every finding with a four-level taxonomy: Declared, Observed, Inferred, Validated. On this internal rollout, nothing is marked Validated yet — most findings sit at Inferred, still to be confirmed by sustained use over time. We'd rather say so than present a few weeks of work as an already-settled success.
Why we're saying this publicly anyway
Because a provider that recommends a governance discipline to its clients without applying it to itself loses part of its credibility. The framework's detail is available on temporal-architecture.com; the group-level context for this rollout is developed in the corresponding article on the UGM-Group site.
A question about your situation?
Request a free audit, we'll look at your specific case.