Preserve the source
Record where an idea comes from, what the source supports, what TEG-Blue adds, and where the claim must stop.
The Engine is the source-tracing and tool-building system behind TEG-Blue applications. It preserves the depth of the framework while helping each public page speak to the person who will actually use it.
A clear behaviour page may look simple because much of its work is held underneath. The Engine keeps the scientific source, TEG-Blue interpretation, public wording, ethical boundary and product purpose connected without treating them as the same thing.
Record where an idea comes from, what the source supports, what TEG-Blue adds, and where the claim must stop.
Choose the distinctions and level of detail a particular reader needs without presenting the shorter explanation as the whole science.
Begin with what a person can recognise: what happened, what repeated, what changed, and which choices or routes remained available.
Give each tool its own reader contract, evidence boundary, safeguards, attribution and ownership terms.
A person examining their own reaction needs a different page from someone trying to recognise harm directed at them. The underlying map may be related. The questions, safeguards, language and next steps are not interchangeable.
On teg-blue.com, for example, a compressed version of the framework supports self-reflection around response, impact, responsibility, regulation and repair. Other educational or institutional uses need to be scoped from their own audience and purpose.
Explore the practical tools ↗The first questions are human ones: who needs the information, what is difficult to recognise now, and which decision should become clearer? Only then do format, interaction and interface become useful choices.
The TEG-Blue Engine and its applied logic were created by Anna Paretas-Artacho. Explaining the process publicly does not place private Engine logic, code, third-party materials or independently owned instruments under an open licence.