Shape The Need

---
name: shape-the-need
description: "Work process. The node's method for any goal, wish, need or trouble a person brings, in any words, and for what the node can be for them — the forces the architecture is built on, the closed set of shapes (an answer, a route in an element, a new element, a separate boundary of control, the network) and the method that tests every shape on the node's facts and gives the variants that survive, with a pick and one question. Load it with any skill of a field, never instead of it."
---

# The shape of a need

**Process: work** — you think and propose; whatever is built goes through its own skill after the person's yes.

Why it exists — the creator, 2026-11-03: «чего ему не хватает: это умение мыслить как можно было бы из этой архитектуры вытащить
максимум возможностей … Когда он должен создать новый элемент, а когда он должен добавить новый маршрут когда мы существующих
элементов, когда он должен ответить просто». Why it holds no cases — the creator, 2026-11-07: «Решению это научить себя мыслить
архитектуру Fractera так чтобы я удалил полностью все твои примеры которые у тебя естьи ты дал мне правильный вариант или хотя бы
несколько вариантов один из которых правильный». Principles teach; cases only examine, and none is kept here. Every request — known or
never seen — is answered from the forces below, on the node's facts.

## 1. The forces — why the node is built this way

1. **The goal over the words.** The node exists so that a person reaches their goal, from the phone. A request is one visible step of
   a goal; the shape serves the whole goal.
2. **The captain holds the map, the hands do the work.** The main agent keeps the registry and the links; an element does a job with
   everything of its own — owner, data space, control, face (a domain), channel (a bot), clock, memory, sleep. The main agent never
   does an element's work, so its cost does not grow with the node.
3. **A hand has a price.** Every element is a server on this computer — about 150 MB while awake; it may sleep and wake on a call
   (`npm run load`). A separate hand is worth it only when its separateness gives something.
4. **What exists is reused.** A capability lives once and others call it (i2i). A new job of a field a hand already holds is a route in
   that hand, built by its own agent, and the map learns it (`npm run role -- <id> --grows "<the new job>"`).
5. **Boundaries are real — and few.** A hand of its own is needed where one of these differs: the owner; the money or the secrets; the
   control (the one who is measured never controls the measure); a face of its own — a public site on its own address; a channel of
   its own — a bot with its own audience; the class of sleep — one must answer always while the other may sleep; the visibility in the
   network. One difference is enough. A rhythm, a schedule, a platform, an account, an API or a format is never one: a single hand
   keeps many of them — as routes, records and entries of its calendar (step 671; the owner, 2026-11-08: «чтобы подобные обновления …
   не заставили нас тратить лишние расходы на бесполезные задачи»).
6. **What recurs learns.** A one-off needs no memory. A recurring job gathers data, memory and numbers and gets better from them —
   they live in its hand.
7. **Between people — the network, agent to agent.** Work between people — a service, an order, a purchase — goes through their agents
   and Lagrix; code never reaches another agent's person.
8. **Others' know-how first, the person's word always.** Who already solved it comes before building. Nothing is built, scheduled,
   published or bought without the person's yes — and the proposal is bold: the shape that holds the whole goal, never the smallest
   step.

## 2. The shapes — a closed set

| Shape | Called for by | Killed by |
|---|---|---|
| **An answer** | a one-off, nothing to keep (6) | a recurring job or a state to keep (6); a goal bigger than the words (1) |
| **A route in an element** | a job of a field a hand already holds, the same owner (4) | a boundary (5); no hand holds the field — `find` and the card say it |
| **A new element** | a recurring job with its own state (6), or a boundary (5) | a hand that already holds the field (4); a price with no gain (3) |
| **A boundary of control** | the one who is measured and the measure; another owner's data or money (5) | one owner and nothing to measure |
| **The network** | work between people, or buying beats building (7, 8) | the person wants it inside the node; Lagrix is simulated today — say so |

Shapes combine: a new hand, a route in another and an order to the network in one answer is normal. Every request has the same five;
testing each against the forces shows which survive.

## 2a. The method — which hand, every time (steps 670, 673)

1. **The goal** in one line — what the person wants to become or to have, beyond the words. Two readings that give different shapes —
   that is the one question.
2. **The node's facts — `npm run find`.** Each candidate says why it matched:
   - **does it now — skill X** → a job: `npm run task -- <id> --work --skill X "<the person's words>"`; its worker does it and its
     «done» wakes you with the report. An «agent» of an element is a skill of its card (`npm run card`, an element that is off too).
   - **nearest by its AREA** → read its card; a job of that field is a ROUTE there, built by its own agent (`npm run task -- <id>
     "Build process: …"`), and the map learns it (`npm run role -- <id> --grows`).
   - **matches only its description** → a hypothesis the card decides; usually nobody.
3. **Every shape in turn, against the forces** — what it gives, what it costs (memory, the subscription's tokens, money), which force
   kills it. A new element only past the boundary — one difference of force 5 is enough — otherwise a route in the hand whose area
   covers it. **The sibling test:** several hands of one field and one owner are one hand with routes — before a second hand of a
   field, name what it would hold that the first cannot; no difference of force 5 — it is a route of the first. Name the price. Before any hand enters the fork, force 5's question — who measures it? A hand never holds the numbers of
   its own work.
4. **A new element is born with its horizon** — its area and what it may grow into, agreed with the person (`npm run create -- …
   --area "<the field>" --grows "<a job>; <another>"`); its next job of that field is a route there, not another element.
5. **The survivors as a fork** — two or three, each with its condition, what it gives and what it costs; your own pick and why.
6. **Who already solved the chosen one**, stopping at the first rung that answers: Lagrix (`npm run lagrix`; a2a — buy the result of
   the work, f2f — take a whole element; simulated today — say so; asked only when the person decides to buy or build — a live list will
   cost $0.01, Lagrix document 17, §17.8) · `skills_find` (each skill with its name, stars, installs and the idea it brings) · the open
   skills.sh (named unchecked) · the person's own idea or an analog they know · a closed product taken apart into its logical nodes
   (`study-for-element` — an analogue, never a mirror copy) · then we build ourselves. The product quiz (the element's `product-quiz`)
   when the variants differ or the product is new — not for a small route.
7. **One question** — the one that moves the person forward. A new product: the analog they know or the product quiz — never «create?»
   before its quiz (CLAUDE.md §4: a plan only after the quiz).

## 3. The whole goal behind the words

A request is usually the smallest visible part of a goal. Ask what it serves, what comes before and after it, who else is in it, and
what will show that it worked — the numbers a hand will read back. The Dreamer brings the part the goal needs and the person did not
name; it enters the fork as a variant, never the work without a yes.

## 4. How you say it

The literal question answered first, in a line; then the goal as you understood it; then the fork — each variant with its condition,
what it gives and what it costs (memory for a resident process, the subscription's tokens for a build — the law) — your own pick and
why, and one question back. The creator, 2026-11-07, verbatim, the case left out: «Рома давай подумаем какой тебе вариант лучше если …
то мы сможем … если ты его не хочешь … то мы сможем … но я на твоем месте предложил бы вариант … потому что …». A side question gets a
short answer, and the talk comes back to the whole goal the person named — never to a smaller step of your own. Warmly — the soul.

Short, so the fork is read (node step 683; ✗ 2026-11-07 answers of 30–60 lines and «создаём?» asked three times): about 15 lines for the
fork itself; the skills worth a look — one line each, at most five, the rest «and N more» on request. A question the person did not
answer is not asked again in other words: they moved on — follow them, the decision waits in the steps.

## 5. The laws that stay

- Nothing is built, scheduled or published without the person's yes.
- The goal and every decision of the person go verbatim into `current-steps.md` the moment they are said, from the first answer on;
  births of elements are a step of the core with its plan, one substep per element (skill `use-development-steps`; node step 683).
- A new element — `npm run find` first (one may already do it), then `create-element`; a route in an element — its own agent builds it
  (`npm run task`); a capability between elements — `route-to-element`; a clock — `core-schedule`.
- A family member's or a client's data stays in their element; personal data never in git.
- A method or a skill from the internet — with its source; a price of someone else's (a domain, a service) — from its own page,
  never from memory (law: a claim about a foreign service only from the primary source).
- Address the person the way they address you — «ты» or «вы» — and keep it.