---
name: integrator
description: "Both natures. The integrator — one architect gives every person of a family, a team or a community an element of their own, and the person talks to its agent from Telegram without ever opening the computer: a deep memory, a coach, household expenses, services to sell (rides, help at home, home cooking), learning a language, programming or AI. Load it when the architect speaks of people near them — «для жены», «для сына», «для моей команды», «чтобы мама тоже могла», «one node for the whole family» — or asks who else the node can serve."
---

# The integrator — one node for a family or a team

**Process: both.** The talk and the order are the working process; every element is then born by the skill `create-element` (build).
Node step 649; the owner, 2026-11-05: «один архитектор может поднимать под любого участника сообщества и его собственный элемент.
Пользователь может перейти по ссылке создать агента Telegram и в принципе даже никогда не открывать компьютер» — and «это мой самый
желанный сценарий работы проекта».

## Why it matters
Many people have heard of AI and never let it into their lives: a chat is already hard for them, building an agent is out of reach.
Here one person who can drive the node is enough. Everyone else gets an element and a bot, and only talks.

## The order — one person at a time
1. **Who and what for**, in the architect's words: the person, what their agent should do for them, in which language. Several
   people — one element each, never one element for many: an element's memory, bot and data are one person's.
2. **The rules first**, in two sentences (skill `provider-rules`, «The integrator case»): the person works on their **own** Claude
   subscription — their work never runs on the architect's; Anthropic's services are for people of 18 and older. A minor's element
   does not run on a Claude subscription; the lawful way for it is the architect's decision, never yours.
3. **The own domain first** — on the temporary address registration is closed (`/api/domain/activate`, skill `use-domain`).
4. **The element:** `npm run find` → none fits → `npm run create` (skill `create-element`) with the person's role and job in the brief.
5. **The person's account:** they register on the element's site and become its administrator — an account belongs to an app, other
   elements are not visible to them (`npm run role` when the role is missing).
6. **The bot:** the person makes a bot in @BotFather on their phone and gives its token to the architect; the token goes on the
   element's Telegram page, which gives the invite link `t.me/<bot>?start=…` — the person opens it and talks (`npm run telegram`).
7. **The work runs:** the element's agent serves its person; a service to sell joins Lagrix only at the person's word (`npm run web4`).

## What to propose — from the owner's list
Deep memory · a personal coach · household expenses · selling services (rides, help at home, home cooking to order) · ordering
services of other people through Lagrix · learning: a foreign language, programming, AI. Each is a custom element of its own.

## Laws
- Personal data of the people never goes into git; an order leaves a summary without it (`order:save`).
- The element boundary holds: the person's agent sees only their element; the architect sees all — say so to the person.
- Nothing is offered as working that the node cannot do today: a capability missing — `npm run need` and the skill `handle-need`.
