How TEG-Blue Works
The data system behind TEG-Blue. How established theories connect through frameworks, consolidate into root data organized by biological function, and distribute to research pages and interactive tools.
The data system
TEG-Blue operates as a five-layer data pipeline. Each layer has a specific function and feeds the next.
Established science
145+ peer-reviewed theories from neuroscience, psychology, attachment research, and trauma studies. Every source credited.
Concept Architectures
12 framework CAs (F1–F12) and 3 model CAs (M1–M3). Each maps which theories connect, what mechanisms operate, and what predictions follow.
Root data files
Five files organized by biological function — emotions, capacities, modes, restoration, and a master integration table. Each section traces to its originating CA.
Data libraries
JavaScript exports that transform root data into structured objects consumed by interactive tools. Changes to root data propagate automatically through the libraries to every downstream tool.
Published outputs
20+ interactive tools on teg-blue.com. Framework pages, model pages, glossary, and diagrams on teg-blue.org.
Every published claim traces backward through this chain. Every tool traces to a data library, which traces to a root file, which traces to a Concept Architecture, which credits its source theories.
Established science
TEG-Blue synthesizes 145+ established theories from independent research traditions that developed in separate disciplines, often without reference to each other. Every source theory is credited. The system does not replace these theories — it proposes specific connections between them.
The originality is not in the individual theories — it is in the cross-disciplinary connections proposed between them. TEG-Blue connects nervous system regulation to moral perception, attachment patterns to social stratification, self-protection to domination as a continuous gradient, and linguistic complexity to regulatory capacity. These connections generate testable hypotheses that no single source discipline could produce alone.
Concept Architectures
Concept Architectures (CAs) are the intellectual origin layer. Each is a formal working document that maps how established theories connect within a specific scope.
What each CA contains
- The specific claims the framework or model makes
- Which established theories and researchers it draws from
- The cross-disciplinary connections it proposes
- The mechanisms it describes — inputs, processes, outputs
- The testable predictions it generates
12 Framework CAs (F1–F12)
One per framework, organized in three arcs. Each maps the complete intellectual structure: what it explains, what research supports it, what it predicts.
Individual arc (F1–F3)
How the nervous system evaluates safety, calibrates through development, compensates through cognition
Collective arc (F4–F7)
How individual patterns scale into rules, hierarchies, bias, and domination
Repair arc (F8–F12)
How capacities rebuild, neurodivergent variation, generational patterns, paradox, and the two information systems
3 Model CAs (M1–M3)
One per model. Models describe how something works as a usable instrument. They draw from the framework CAs but serve a different, applied scope.
M1 — Nervous System Signaling
What the system does: the instrument, the modes, the observable compass
M2 — Awareness Capacities
What can be perceived: Reading Emotions (RE), Emotional Resonance (ER), Self-Emotional Awareness (SEA)
M3 — Regulation Capacities
What enables return: restoration, substitutes, escalation, what genuine return requires
Status note: Concept Architectures are working documents — designed to be testable, correctable, and open to scholarly review. The theoretical mapping is a working hypothesis, not a finished academic work.
Root data
The Concept Architectures feed into five root data files — the operational consolidation layer. Content from the CAs is extracted and reorganized by biological function rather than by framework or discipline. Each section in a root file has a provenance table mapping it back to its originating CA.
This is where the biological architecture becomes visible. The root layer reveals four independent layers that map the nervous system's response cycle.
Emotions as Signals
The input — what fires the system
Nine canonical emotions, each mapped across four modes in fluid and chronic states. How each emotion signals, what it requires to complete, and how it reroutes under different regulatory conditions.
Awareness Capacities
The receiver — determines if the signal lands
Reading Emotions (RE), Emotional Resonance (ER), Self-Emotional Awareness (SEA). How the three capacities interact, what happens when each is absent or suppressed, and how they recover.
Mode Positions
The state — what configuration the system enters
Four fluid and four chronic positions. Each mapped across multiple dimensions — how the system activates, perceives, behaves, and what repair looks like from each position.
Biological Restoration
The return — whether the cycle completes
What genuine return looks like from each mode. What substitutes step in when return fails. Why substitutes escalate. The mechanics of the regulation thread.
Master Table
All four layers compressed into integration tables and structural rules
The complete compass in tabular form — fluid and chronic states across all dimensions. Structural rules governing how consolidated data derives into published content. Every cell traceable to one of the four mechanism files.
Emotion fires → Capacities determine if it lands → Mode configures the system state → Restoration completes or fails. When restoration fails, a regulation substitute steps in. This is the Regulation Thread — the mechanism that runs through all twelve frameworks.
From root to output
Root data distributes to two sites through different mechanisms. On teg-blue.com, root data is exported as JavaScript data libraries that feed interactive tools. On teg-blue.org, root data is verified against inline content in research pages.
teg-blue.com — Data libraries to tools
Each of the 20+ interactive tools on teg-blue.com has its own data file that draws from these libraries. Changes to root data propagate through the libraries to every tool.
teg-blue.org — Root data to research pages
The .org site has no JavaScript imports from vault data. All content is inline in page files. Root data serves as the verification source — content on the research site must be consistent with root data.
Traceability
Provenance is an architectural constraint — every claim traces backward through the data system. Each root file section has a provenance table classifying its relationship to its originating CA.
The CA contains the complete intellectual architecture. The root file consolidates it operationally.
The CA covers the concept. The root file adds systematic detail or per-mode precision.
Operational detail that correctly lives at root level — systematic tables, neuroanatomical specificity, per-mode × per-emotion data matrices. Not a gap.
The full traceability chain: a tool on teg-blue.com → its data file → the data library it imports → the root file section → the provenance table → the originating Concept Architecture → the established theories it credits. Any claim can be audited by following this chain.
Why provenance matters for integrative work
Design principles
Five constraints govern the data system.
Biological organization
Data is organized by what the body does, not by academic discipline. Emotions, capacities, modes, and restoration each map to a step in the nervous system's response cycle.
Provenance as architecture
Every root file section traces to its originating Concept Architecture. Every CA credits its source theories. Traceability is structural, not aspirational.
Separation of layers
Intellectual origin (CAs), operational consolidation (root data), and published output (sites) are independently verifiable. Each layer can be audited without depending on the others.
Single data source
Both sites draw from the same root data. Changes propagate through the export chain. Research pages and interactive tools always reflect the same underlying data.
Open by default
Methods, data structures, and reasoning are published openly. The system is designed to be audited, tested, corrected, and replicated.
Anna Paretas-Artacho — Independent researcher and systems designer, Barcelona. 25+ years in systems thinking. TEG-Blue developed over two years as an integrative architecture across 145+ established theories. Full background →