AI-augmented psychotherapy for the twenty-first century

An ecosystem where psychology meets AI

This page introduces the people building DETai, the founding vision for the ecosystem, its participation principles, and the path into the team. Here, the concept becomes distributed work across the method, research, psychotherapy, education, technology, and products.

Our team

DETai is developed by a team. The founder holds the original vision, methodological concept, and strategic horizon; participants take responsibility for the technological, research, institutional, product, and management domains.

You could be part of the team
Team member avatar: Anton Kolhonen

Anton Kolhonen

Founder of DETai and author of the DET method

Defines the DETai research framework and aligns psychological practice with AI architecture.

Management Layerpsychologyproduct
Team member avatar: Vsevolod Arkhipov

Vsevolod Arkhipov

Onboarding & Team Operations Coordinator

Helps new contributors join the DETai working environment, develops team processes, and contributes to practical improvements of the ecosystem's internal systems.

U.L.I.team operationsonboarding

Our vision

How we turn vision into action

Vision gives direction, but development needs structure: first a strategic course, then levels of responsibility, then tools that turn decisions into a living work process.

First, vision becomes a shared course.

Development strategy

The DETai ecosystem develops from its mission, values, founding concept, and the observable state of practice, research, the team, and products.

Governance maintains long-term boundaries and authority, while Management translates the strategic course into priorities, accountable owners, and measurable work cycles.

Then strategy is distributed across levels of responsibility.

Levels of work

Once the course is chosen, work is distributed not only by level, but also across institutional, technological, product, research, and operational domains.

Every decision needs a clear owner, scope of authority, coordination method, and escalation path. U.L.I. supports technical development but does not replace governance of the ecosystem as a whole.

After that, the levels receive an operational stack.

Work tools

To turn architecture into action, the team uses tasks, code, design, documentation, AI assistants, automations, and communication channels.

These tools form an operational stack, but they are not the governance model itself: decisions and responsibility remain with people and defined roles.

How the system works

This is the team’s operational stack: the tools through which decisions become tasks, code, designs, documents, communications, and publications. The complete Governance and Management model is described in the knowledge base; the tools merely support it.

GPT logo

GPT

AI reasoning layer

ClickUp logo

ClickUp

Tasks and production cycles

Codex logo

Codex

Agentic development

GitHub logo

GitHub

Code and review

Linear logo

Linear

Issue design

VS Code logo

VS Code

Local workspace

Make logo

Make

Automation layer

Airtable logo

Airtable

Structured data

Telegram Bots logo

Telegram Bots

Operator interfaces

MkDocs logo

MkDocs

Knowledge base

GPT logo

GPT

AI reasoning layer

ClickUp logo

ClickUp

Tasks and production cycles

Codex logo

Codex

Agentic development

GitHub logo

GitHub

Code and review

Linear logo

Linear

Issue design

VS Code logo

VS Code

Local workspace

Make logo

Make

Automation layer

Airtable logo

Airtable

Structured data

Telegram Bots logo

Telegram Bots

Operator interfaces

MkDocs logo

MkDocs

Knowledge base

Participation principles

The DETai ecosystem is more than a concept, structure, and products.
It is a space of shared responsibility where participation begins with an inner choice and becomes a visible contribution.

Inner desire

Participation is not forced from outside. It begins with a personal impulse: the desire to develop, build and expand the horizons of psychology and technology.

The full version of the principles and their expanded explanation are introduced during onboarding.

Cyclical onboarding

How to become part of the team

The full entry route is described on a separate page: stages, roles, participation principles and the current application status.

team entry runs in cycles; the process is scheduled to begin in the second week of September 2026.

Learn about onboarding