FAQ
Frequently asked questions
The TEAF framework: the loop, TEAF Light, scientific validation and the organizations using it.
What is TEAF?
TEAF (Temporal Enterprise Architecture Framework) is an enterprise architecture framework for the AI era: a continuous eight-component loop (Intent, Capability, Knowledge, Decision, Automation, Execution, Observation, Learning). TEAF does not replace TOGAF, ITIL or COBIT — it orchestrates their continuous execution, with AI as an accelerator.
How does a TEAF deployment unfold?
A deployment follows four phases: Why (strategic scoping), What (mapping of capabilities and knowledge), How (target architecture, automation and AI) and Who/When (governance and deployment calendar). Each phase produces concrete deliverables before moving to the next — see the Framework page for detail.
Which technologies does TEAF Light use?
The reference stack favors open source and sovereignty: Dolibarr, GitLab, PostgreSQL/pgvector, n8n, Python, Cloudflare. TEAF remains a model, not an imposed stack, though — any organization can choose its own tools as long as the loop principle is respected.
Can I assess my maturity before going further?
Yes. The online maturity diagnostic is free, anonymous and takes about six minutes. It positions your organization across the model's seven levels and identifies your two most urgent priorities.
Has TEAF been deployed in real organizations?
Yes. The TEAF loop and the TEAF Light 1-1-1 principle have been implemented in organizations across different sectors — IT, human resources, industry, logistics, business consulting, real estate. Names are not disclosed: some organizations asked for anonymity, others prefer to wait until the framework is more established before being publicly associated with it. This is a common constraint in architecture consulting, not an evasion.
Why don't the books cite named case studies?
Because the organizations involved aren't yet in a position to speak publicly (see previous question). The scenarios in Books III and IV are explicitly presented as fictional and pedagogical — they illustrate the method, not a real client outcome. The V2 of the collection aims to incorporate feedback and constructive criticism from other organizations.
Has TEAF been scientifically validated?
Not yet, and the collection doesn't claim otherwise. One year after publication, TEAF has been tested in the field — the loop runs, the diagnosis holds across varied contexts — but no independent, reproducible measurement protocol has been run yet. That's the acknowledged next step: laying the groundwork for a more rigorous validation of the concept, beyond field feedback.
Are all 4 books in the collection available on Amazon?
Yes, the V1 collection is now complete: Books I to III remain available in paperback and Kindle (individually, or as a 3-book series), and Book IV — the operational implementation guide — is now published too, in Kindle (available instantly) and paperback (currently being restocked by the publisher). Its practical counterpart remains the TEAF Light open-source repository on GitLab, an executable implementation of the 1-1-1 principle it details.
Is TEAF an alternative to TOGAF, ITIL or COBIT?
No, and that's not its ambition. These frameworks remain the foundations; TEAF is a continuous orchestration layer that connects their deliverables to real execution, at the same pace AI accelerates it. A TOGAF architect or an ITIL practitioner has nothing to unlearn to use TEAF — the Intent→Learning loop adds to these frameworks, it doesn't replace them.