TEG-Blue Engine

Custom nervous-system-informed tools for institutions.

TEG-Blue Engine builds applied products for schools, NGOs, therapists, public institutions, and companies that need a clear way to name emotional and relational patterns.

The research stays visible on teg-blue.org. The applied tool lives where people need to use it: on teg-blue.com, a partner surface, or a dedicated public domain.

Start an institutional tool Research foundation

First public applied implementation

Violentómetro Digital

A public pilot showing how an existing institutional framework can become an interactive, safety-aware tool. It uses the IPN Violentómetro as source material and adds nervous-system-informed framing by TEG-Blue.

Visit public tool Project context

Domain architecture

Research proof and applied products stay connected, but separate.

The Engine is not a public dump of internal framework mechanics. It is a translation layer: enough provenance for trust, enough restraint for safety, and a tool surface designed around the audience in front of it.

teg-blue.org

Open research layer

Public methodology, citations, concepts, and provenance stay on the research site.

teg-blue.com

Applied tool studio

The Engine turns that proof layer into clear, humane products for a defined setting.

tool domain

Public or private implementation

Each project gets the right name, attribution, privacy posture, language, and launch surface.

What gets built

Custom tools, not generic quizzes in institutional colors.

Each product is shaped around a real use case: what people need to recognize, how much risk the context carries, what language is appropriate, and what action path should exist after recognition.

Public awareness tools

Interactive pages for prevention campaigns, public education, and shared language around sensitive relational patterns.

Psychoeducation instruments

Session-friendly visual tools that help people name patterns without turning the tool into diagnosis or treatment.

Reflective assessment flows

Guided questions, pattern maps, and result pages designed for self-recognition, referral, or education.

Institutional campaign sites

Standalone microsites with careful attribution, safety framing, SEO, translation pathways, and launch context.

Who it serves

Built for the setting, language, and stakes of the people using it.

The same research base can produce very different public forms. A school prevention tool should not sound like a clinical worksheet. A therapy aid should not behave like a campaign site.

Schools and universities

Prevention, student support, classroom discussion, peer education, and non-punitive language for harm, pressure, repair, and boundaries.

NGOs and public institutions

Public-facing tools that make risk patterns readable while preserving dignity, privacy, and user safety.

Therapists and clinicians

Psychoeducation aids for naming emotional and relational patterns in session, supervision, or reflective practice.

Companies and teams

Practical maps for accountability, conflict, pressure, repair, burnout signals, and relational safety at work.

Trust boundaries

The work is careful because the subject matter is sensitive.

Engine tools can make patterns easier to read, but they should not overpromise clinical outcomes or push vulnerable users toward exposure. The ethical posture is part of the product.

Not a diagnosis

Engine tools can support education, reflection, and pattern recognition. They do not diagnose, triage, or replace clinical judgment.

Safety-aware by design

Sensitive projects can use neutral naming, restrained attribution, noindex settings, referral language, and careful content warnings.

Research stays public

The proof layer belongs on teg-blue.org. Applied products on .com or dedicated domains should point back without exposing internal build details.

Privacy before metrics

The default stance is to reduce unnecessary collection and avoid turning vulnerable users into a data source.

Appropriate use matters

TEG-Blue Engine is for education, pattern recognition, prevention, reflection, and institutional language-building. It is not an emergency service, diagnostic system, or substitute for professional care.

Research ethics

How projects usually start

A practical path from institutional need to usable tool.

The first conversation should define the problem and the boundaries before it defines the interface. That keeps the tool useful, legible, and appropriately cautious.

STEP 01

Context brief

Define audience, risk level, use case, language, partners, and what the tool should help people recognize.

STEP 02

Tool architecture

Shape the content model, decision paths, visual system, safety boundaries, and research attribution.

STEP 03

Build and launch

Create the public or private surface, test responsive behavior, clarify ownership, and prepare the contact or referral path.

Contact path

Have an institutional tool in mind?

Email contact@teg-blue.com with the subject Institutional tool with TEG-Blue Engine.

Start an institutional tool

Useful details to include

Who the tool is for
The situation or pattern it should help people recognize
Any safety, privacy, language, or attribution constraints
Whether it should live on teg-blue.com, a partner site, or its own domain