TEAF at Workynet: linking multi-country compliance to tracked architecture governance
Workynet is the second UGM-Group subsidiary to roll out TEAF, the enterprise architecture governance framework created by Mathieu Urbitsch. What that changes for an activity already governed by GDPR, FADP/nFADP and PIPEDA.
Our Compliance page details how we apply GDPR, FADP/nFADP and PIPEDA depending on our clients' country of operation. Since early September 2026, an additional layer has been added to that discipline: Workynet is, alongside Trustiatis, 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
Our compliance guarantees stay unchanged: confidentiality training, secure VPN and CRM/ERP, a collaborator replaced within 72 hours, regular audits. What TEAF adds is formal traceability for the decisions that evolve our setup — for instance, choosing which compliance framework applies to a new country of operation now becomes a dated, justified Living ADR, rather than an undocumented internal call.
A role that maps directly onto our business
Among the five roles TEAF requires to be named, the Compliance Liaison maps most directly onto our trade: it maintains the map of applicable frameworks (GDPR, FADP/nFADP, PIPEDA, and any other relevant regime depending on where our clients operate) and confirms that no decision binds the company outside that framework. That role already existed in practice at Workynet; TEAF gives it a name and a formal record.
What's still to be confirmed
As at Trustiatis, this rollout currently sits at the Inferred level of TEAF's taxonomy (Declared / Observed / Inferred / Validated) — nothing is marked Validated yet. That's the same rule we implicitly ask our own compliance partners to follow, applied at home first.
The framework's detail is available on temporal-architecture.com.
A question about your situation?
Let's talk about your compliance and outsourcing needs.