01
Preserve the source
Record where an idea comes from, what the source supports, what TEG-Blue adds, and where the claim must stop.
From framework to tools
The TEG-Blue Engine
The TEG-Blue Engine connects research and the framework to the questions people encounter in a tool. This page explains how that work is done, shows The Harm Gradient as its first application and describes how to develop a tool for a particular audience.
01
How the Engine connects sources and tools
A public question needs a traceable explanation behind it. The Engine links that explanation to the source material and separates research findings from TEG-Blue’s interpretation. It also records what the tool is intended to help readers understand and what its answers cannot establish.
The Engine is not an automated judge of people. It does not diagnose, prove motive, identify an inner state from the outside, or turn one answer into a verdict.
02
Four parts of tool development
02
Translate for the reader
Choose the distinctions and level of detail a particular reader needs without presenting the shorter explanation as the whole science.
03
Write questions about specific situations
Name whose response the reader will examine and what they can observe. An apology tool, for example, asks whether the person acknowledges their action, listens to the person affected and changes the behaviour.
04
Check purpose, safety and rights
State who the tool is for, what its answers can establish, when other support is needed, who contributed the material and how it may be used.
03
Questions for different situations
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, readers can examine their own responses or someone else’s behaviour. The people-pleasing tool asks whether they can express their needs without agreeing to avoid disapproval. The apology comparison asks what they or another person acknowledge and change after saying sorry. A tool developed for a workplace, classroom or support service needs questions suited to that setting.
Readers compare responses across situations rather than treating one exchange as a complete account of a person. A tool can name a harmful action and ask whether the person responsible acknowledges it and changes their behaviour, without claiming to know their motives or nervous-system state.
Explore the practical tools ↗04
The Harm Gradient
The Harm Gradient is an educational guide powered by the TEG-Blue Engine, and the first tool built with it. It explains patterns of control, harm and violence in relationships.
In collaboration with Dr Martha Alicia Tronco Rosas, the guide brings together TEG-Blue’s contribution and the foundations in Violentómetro 1 and 2.0.
Readers can explore 64 patterns in English and Spanish, beginning with something they recognise. Each entry provides examples and explanations, with links to information about healthy relationships and support. The guide is free to read without an account.
The Harm Gradient organises patterns of harm. Its bands do not identify someone’s nervous-system state or correspond directly to positions on The Nervous System Gradient. They help readers browse the guide; they do not score a relationship or predict what will happen.
05
Develop a tool for your context
Practitioners, institutions, NGOs, research teams and companies can bring a question, relevant material and experience of the people they work with. The first decisions are who will use the tool, where they will use it and what it should help them recognise or understand.
The content, language and format are developed around that purpose. A collaboration could produce a public guide, a resource for use in sessions, training material or a tool for a research project. Its audience and access, evidence limits, accessibility and safety needs, and review responsibilities are agreed for that project.
To begin, describe the people the tool would serve, the question it would address and any material you already have.
Discuss a tool for your context ↗06
Authorship, permissions and ownership
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.
How are collaboration terms agreed?
Each project defines its scope, ownership, attribution, permitted use, review responsibilities and handling of confidential material before substantive work begins. An initial conversation is exploratory and does not create a partnership or commitment to build.
Can the public framework or Engine be reused?
Original public written framework content may be reused under CC BY 4.0 with attribution, unless a page says otherwise. Marks, tools, code, Engine logic and third-party material are excluded. Use of Engine logic, custom tools or product integrations requires written permission or a separate agreement.