The field of publishing

Process: both. The talk is the working process; whatever is born goes through create-element or the hand's own agent (build). Node step 658; the owner, 2026-11-05: «обычно пользователи используют чистый Claude.ai для того чтобы везти свои социальные сети … но можно достигнуть раза до больших результатов если таким образом использовать Fractera …». Step 673: this skill gives the facts of the field; which shape the work takes — an answer, a route, a hand of its own, a boundary, the network — the method of shape-the-need decides on the node's facts.

Why it matters

Claude.ai alone writes a good post. Publishing is a loop — a channel, a voice, the numbers of each publication, the topic that rises — and each publication can teach the next only where the loop is kept.

The facts the forces act on

• A platform has its own account, API, rules on automation, spam and limits, and its own rhythm. Its rules are read on its own pages, never told from memory (npm run site-rules, skill provider-rules). Where two platforms differ in these, they differ in force 5 of shape-the-need.
• A voice — an author's style taken apart into as many components as possible — serves every channel that writes in it (force 4). It is built from the author's open texts that site-rules allows, or from what the person brings (CLAUDE.md §6: a site that forbids study gives only the person's screenshots); we take the techniques, never the texts.
• The numbers — every publication returns its statistics through the platform's official API; reading them and changing the next publication is what makes the loop grow (force 6). They belong to the one who publishes.
• A rising topic is seen through the official APIs and feeds of networks, channels, video and news portals, on a clock (force 6).
• Media the node lacks — image or video generation, montage, animation — is a capability many will reuse (force 4).
• The person's own domain can hold their long texts, besides the platforms; npm run find and the cards show which hand's area already covers a site.

How the work runs once the shape is chosen — one link at a time, each after the person's yes

1. The channels and the goal, in the person's words: which networks, blogs, boards, forums; what the publications are for.
2. Whatever is new is born with its horizon (create-element, its area and what it may grow into); a new job of a field a hand holds is a route built by that hand's own agent.
3. A portrait — the style taken apart (study-for-element), then adapted to the person's product.
4. A publication — the one who holds a channel asks the one who holds the voices for a text, over the API the two agents agree (route-to-element, i2i). The person approves a draft, or gives a standing yes for one channel and one rhythm.
5. The numbers — read into the publisher's own tables and the deep memory (node step 654: its own space); an analysis at a rhythm the person chose says what works where — the topic, the format, the hour, the voice — and proposes the next changes.
6. The topics — the one who watches proposes a publication in trend to the channel that fits.
7. Community skills for posting and analytics — skills_find first.

Laws

• Every publication, every posting rhythm and every round of watching starts after the person's yes; a resident process is named with its price in memory.
• Official APIs, feeds and the person's own accounts only.
• No tool of the node posts by itself today: the hand that holds a channel builds its publishing on that platform's API.
• The followers' personal data never goes into git; nothing is offered as working that the node cannot do today.