content-factory · diff
git:20261107.6622c7f to git:20261107.81427d0
34 added, 38 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: content-factory
- description: "Both natures. The content factory — a channel element for every platform (a social network, a blog, a board, a forum), an element of author portraits, publications in the voices of different authors, the numbers of every publication read back to learn what works where, and a scout of social networks, Telegram channels, YouTube and news portals that catches a hot topic first. Load it when the person wants to run their social networks or blogs with the node — «контент-завод», «вести соцсети», «посты голосами авторов», «публиковать в Telegram и YouTube», «отслеживать тренды», «content factory», «grow my channels» — or chose the root page's card «Создать контент-завод»."
+ description: "Both natures. The field of publishing — channels on social networks, blogs, boards and forums, the voices of authors, the numbers every publication brings back, the topics that rise. The facts the method of shape-the-need weighs when a person's goal involves publishing, and how the work runs once the person chose its shape. Load it together with shape-the-need, never instead of it."
---
- # The content factory
+ # The field of publishing
- **Process: both.** The talk and the order are the working process; every element is then born by the skill `create-element` (build).
+ **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 для каждого канала создать отдельный элемент».
+ можно достигнуть раза до больших результатов если таким образом использовать 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. A node holds the whole loop: every channel with its own agent and rhythm, the voices of the authors
- the person admires, the numbers of every publication, and a scout that sees a topic rise before others. Each publication teaches the next.
-
- ## First — which hand (step 670)
- The first answer walks the order of CLAUDE.md §4 «A request comes» (skill `shape-the-need` §2a) before the order below:
- 1. `npm run find` with its reasons; an element nearest by its AREA is read by its card — root may grow into «the project's blog»: when
- the texts deserve a home on the person's own domain, that is a route there, built by root's own agent.
- 2. The boundary — a channel with its own account, bot and rhythm, and the author portraits every channel reuses, are elements,
- proposed with their area and what they may grow into; each is about 150 MB while awake (`npm run load`).
- 3. Lagrix — `npm run lagrix`, simulated today: say so.
- 4. `skills_find` — every skill with its name, stars and installs and the idea it brings.
- 5. A fork, never one line: a single post — right here, nothing built; a series that grows post by post — the route and the elements
- above; your own pick and why; then one question.
+ 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.
- A series of publications recurs: never «a trial post first», never the main agent writing the posts with a skill of its own — the
- posts are the elements' work, the main agent holds the map (670-7, run 1: «один пробный пост», «свой собственный навык» — the owner:
- «очень очень слабо»).
+ ## 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.
- ## The order — one link at a time, each after the person's yes
+ ## 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. **The channels** — one element per channel when accounts, APIs and rhythms differ; one element with routes when they do not
- (`shape-the-need`). Each has its own bot.
- 3. **The author portraits** — an element «author portraits»: each author a route; the style taken apart into as many components as
- possible for an exact portrait (`study-for-element`), then adapted to the person's product.
- 4. **Publications in the authors' voices** — a channel's agent asks the portraits element for a text in a voice 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** — each channel element reads its publications' statistics through the platform's official API into its 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 scout** — an element that watches the chosen social networks, Telegram channels, YouTube and news portals through their
- official APIs and feeds, catches a rising topic and proposes a publication in trend to the channel that fits.
- 7. **What the node lacks** — an image or video generator, montage, animation — is an element of its own (`shape-the-need`); community
- skills for posting and analytics — `skills_find` first.
+ 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 the scout starts after the person's yes; a resident process is named with
+ - 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. A platform's rules on automation, spam and limits are read on its own pages,
- never told from memory (`provider-rules`, `npm run site-rules`).
- - No tool of the node posts by itself today: each channel's element builds its own publishing on its platform's API.
+ - 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.