The field of people near the architect

Process: both. The talk is the working process; whatever is born goes through create-element (build). Node step 649; the owner, 2026-11-05: «один архитектор может поднимать под любого участника сообщества и его собственный элемент. Пользователь может перейти по ссылке создать агента Telegram и в принципе даже никогда не открывать компьютер» — and «это мой самый желанный сценарий работы проекта». Step 673: this skill gives the facts of the field; the shape comes from the method of shape-the-need.

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. One person who can drive the node is enough; everyone else only talks.

The facts the forces act on

• Each person is an owner of their own: an element's memory, bot and data belong to one person (force 5). The architect sees all of them; the person's agent sees only its own element — say so to the person.
• Each person works on their own Claude subscription — their work never runs on the architect's; the person signs their own element in themselves, choosing its own person's subscription on the element's page «Подписка Claude Code» (its own Claude Code folder, step 689); Anthropic's services are for people of 18 and older; a minor's work does not run on a Claude subscription, and the lawful way for it is the architect's decision, never yours (skill provider-rules, «The integrator case»).
• Registration needs the own domain — on the temporary address it is closed (/api/domain/activate, skill use-domain).
• An account belongs to an app: the person registers on their element's site and becomes its administrator; other elements stay invisible to them (npm run role when the role is missing).
• A bot is the person's door: they make it in @BotFather on their phone and give its token to the architect; the element's Telegram page gives the invite link t.me/<bot>?start=… (npm run telegram).
• Selling a service joins Lagrix only at the person's word (npm run web4).

How the work runs once the shape is chosen — 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.
2. The rules first, in two sentences — the subscription and the age, from the facts above.
3. The own domain first, when the person must register.
4. Whatever is new is born — npm run find, then npm run create (skill create-element) with the person's role and job in the brief.
5. The account, then the bot — as in the facts above.
6. The work runs: the element's agent serves its person.

Laws

• Personal data of the people never goes into git; an order leaves a summary without it (order:save).
• The element boundary holds.
• Nothing is offered as working that the node cannot do today: a capability missing — npm run need and the skill handle-need.