# Cron Job: Раз в два дня: Разговор с сущностями → Cosmos Luminosity

**Job ID:** 4714f2d26e5b
**Run Time:** 2026-10-05 04:01:00
**Schedule:** 0 4 */2 * *

## Prompt

[IMPORTANT: The user has invoked the "daily-book-extraction" skill, indicating they want you to follow its instructions. The full skill content is loaded below.]

---
name: daily-book-extraction
description: "Set up recurring daily digests from uploaded books/PDFs with accumulating tools, questions, practices, and insights."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [books, pdf, daily-digest, cron, extraction, summaries, practices]
    related_skills: [ocr-and-documents, cosmos-luminosity-content]
---

# Daily Book Extraction

Use this skill when a user uploads a book/PDF/ebook and wants recurring daily summaries, chapter digests, practice extraction, or an accumulating knowledge/tool file.

## Goal

Turn a long book into a stateful daily reading/extraction pipeline that:

1. stores the source files in a stable project directory;
2. extracts text locally when needed;
3. splits the content into digestible daily fragments;
4. emits one fragment per scheduled run;
5. sends the user a clear daily digest;
6. appends tools, practices, questions, techniques, and insights to a durable Markdown file.

## Workflow

1. **Load extraction context**
   - If the source is PDF/scanned/book-like, consult `ocr-and-documents` for extraction options.
   - For user-specific style/content requirements, load the relevant content skill (for Margarita/Cosmos Luminosity, load `cosmos-luminosity-content`).

2. **Create a stable project directory**
   - Example: `/home/spazio/<project_name>/`
   - Suggested subfolders:
     - `pdf/` or `source/`
     - `text/`
     - `daily_fragments/`
     - `daily_outputs/`
   - Suggested files:
     - `README.md`
     - `manifest.json`
     - `state.json`
     - `TOOLS_AND_INSIGHTS.md` or another accumulating output file.

3. **Extract and verify text**
   - For text PDFs, use `pymupdf` / `fitz`.
   - For FB2 / `.fb2.zip`, load `ocr-and-documents` and use its `scripts/extract_fb2_chapters.py` helper to produce per-chapter `.txt` files and `manifest.json`. Inspect the manifest before scheduling: short copyright/title/dedication sections may appear as the first “chapters”; start the digest state from the first substantive section (usually chars > ~1000), not from metadata.
   - For uploaded documents copied from Hermes cache, either preserve the original basename explicitly or refer to the actual copied cache filename returned by file listing; Telegram/cache filenames may be prefixed and not match the visible upload name.
   - For uploaded ZIP ebooks, inspect the archive first; the inner `.doc` may actually be RTF (common with Royallib-style exports). If `file` reports Rich Text Format, decode as RTF rather than Word. Russian RTF may need cp1251 handling for `\\'xx` escapes.
   - For Litmir-style EPUBs, parse `content.opf` and read HTML/XHTML files in OPF spine order. Skip `cover.xhtml` / cover-only text so the first scheduled digest is substantive, not a metadata fragment. See `references/litmir-epub-daily-extraction.md`.
   - Preserve page, chapter, or paragraph markers in extracted text so daily digests can cite ranges.
   - Verify page/chapter counts when available, nonempty text, character counts, and that the first fragment can be read before scheduling.

4. **Split into daily fragments**
   - Chunk by chapter if chapters are clean.
   - Otherwise chunk by approximate character count while preserving page markers.
   - For dense Russian transcripts/books, ~12k–18k chars per fragment is usually enough for substantive extraction without overflowing the model.

5. **Create a stateful next-fragment script**
   - The script should read `manifest.json` and `state.json`.
   - It should output JSON containing:
     - `status`
     - `book`
     - `fragment_number`
     - `total_fragments`
     - source range / chapter range
     - relevant output paths
     - `fragment_text`
   - Add `--peek` mode so you can test without advancing state.
   - Only advance state during real cron runs.

6. **Install the script for Hermes cron**
   - Cron scripts must live under `~/.hermes/scripts/`.
   - When creating the cron job, pass only the relative script filename, not an absolute path.
   - Example: `script="cosmos_book_next_fragment.py"`, not `/home/.../next_fragment.py`.

7. **Mirror the accumulating Markdown into a web-readable page when useful**
   - If the user asks to “watch what is accumulating” from a phone/browser, do not build a second data store. Make the public/website Markdown page the source of truth, and symlink the book pipeline’s `TOOLS_AND_INSIGHTS.md` to that page.
   - Preserve the website page’s YAML frontmatter when appending daily sections; tell the cron prompt explicitly not to delete frontmatter.
   - Add the page to the site/wiki index if the site uses content discovery via Markdown articles.
   - Verify that the page exists and is reachable by URL before reporting success. If a public wiki/Markdown site already exists, prefer adding a new article there over creating a separate narrow one-off server.

8. **Create or update the cron job**
   - Convert the user’s timezone into a cron schedule in the scheduler timezone when needed. Check `next_run_at` after creation; if the scheduler is UTC and the user expects Asia/Singapore / Samui / Bali, 15:30 local is `30 7 * * *`, not `30 15 * * *`.
   - If the user first asks to schedule before uploading the book, create a safe placeholder that asks for the source rather than inventing content. When the source arrives, extract it, create the stateful next-fragment script, then update the existing cron job to use that script (or remove/recreate if needed) so future runs have real source context.
   - If the user says “first day today” / “start today”, emit the first real digest immediately after extraction and advance the state exactly once, then ensure the recurring cron starts from the next chapter/fragment.
   - Make the cron prompt self-contained: future runs do not have the current chat context.
   - Attach useful skills to the cron job.
   - Set `attach_to_session=true` for recurring digests the user may reply to.

8. **Write the cron prompt carefully**
   - Tell the future agent to:
     - summarize/extract in the user’s preferred language and style;
     - avoid long copyrighted quotations;
     - extract tools, techniques, practices, questions, ideas, and daily applications;
     - append to the accumulating Markdown file;
     - save a per-day report;
     - make the final answer the user-facing digest only, without technical logs.

## Copyright and quoting

For copyrighted books, do not reproduce long passages. The deliverable should be transformative: tools, questions, concepts, summaries, applications, and synthesis in your own words. Short phrases may be used when necessary, but the core value should be extraction and interpretation.

## Quality bar for chapter digests

- Write each digest for a reader who has **not read the book/chapter**: reconstruct the scene, sequence, people, places, and causality before interpreting.
- Do not drop isolated symbolic details (e.g. an animal, ritual, childhood image, place name) without explaining where they appear in the chapter and why they matter.
- If giving psychology or subtle meaning, anchor every interpretation to the chapter’s narrative evidence first, then translate it into concepts/practices.
- Label interpretive metaphors as interpretive. If you name a theme like “discipline,” “chaos,” “mother,” “initiation,” or “shadow,” make clear which concrete chapter details support it. Do not make it sound like the author/book literally centered that theme unless the source text does.
- Avoid retrofitting chapter analysis around Margarita’s previously discussed personal themes. Use her Cosmos Luminosity lens as a translation layer, but keep source-derived content and agent-derived meaning separate.
- Prefer a coherent walkthrough: what happens → professional significance → psychological mechanism → subtle/Cosmos meaning → practices/questions.
- For Margarita/Cosmos Luminosity, full-context explanation matters more than short excerpt-style bullets; she may send the analysis to clients who have not read the source.

## Verification checklist

Before telling the user it is set up:

- [ ] Source files copied into stable storage.
- [ ] Text extraction succeeded and page/chapter counts look plausible.
- [ ] Manifest and state files exist.
- [ ] First fragment can be emitted in `--peek` mode without advancing state.
- [ ] Cron script is copied to `~/.hermes/scripts/` and executable.
- [ ] Cron job created successfully.
- [ ] `next_run_at` matches the user’s requested local time, after timezone conversion.
- [ ] Accumulating tools/insights file exists.
- [ ] If a web mirror was requested, the Markdown source is the website article (or symlinked to it), frontmatter is preserved, the article is linked from the site index, and the URL loads from an external browser/curl check.

## References

- `references/public-drive-scanned-pdf-ingestion.md` — public Drive-folder retrieval, large-file confirmation, scan-only PDF detection, rootless Tesseract OCR, and the `OMP_THREAD_LIMIT=1` parallelism fix.
- `references/daily-pdf-book-extraction.md` — reusable layout, script skeleton, and cron prompt checklist based on a multi-PDF daily extraction setup.
- `references/web-published-markdown-mirror.md` — pattern for making the accumulating Markdown file also power a public/wiki web page via one canonical article and symlink.
- `references/royallib-rtf-zip-daily-extraction.md` — ZIP containing RTF-disguised-as-`.doc` extraction pattern, cp1251 fallback, paragraph chunking, stateful `--peek` verification, and UTC cron timezone pitfall.
- `references/modernlib-rtf-zip-daily-extraction.md` — ModernLib-style ZIP with mojibake filenames and `.doc` that is actually cp1251 RTF; includes recognition, extraction, chapter chunking, timezone confirmation, and copyright-safe daily synthesis notes.
- `references/litmir-epub-daily-extraction.md` — Litmir-style EPUB extraction via OPF spine order, cover-fragment pitfall, paragraph chunking, and Margarita timezone/confirmation nuance.
- `references/second-pass-thematic-layers.md` — extend a completed first-pass book cron into a deeper thematic/layered second pass with source excerpts, research queries, copyright-safe close reading, and updated cron prompt/toolsets.

[IMPORTANT: The user has invoked the "cosmos-luminosity-content" skill, indicating they want you to follow its instructions. The full skill content is loaded below.]

---
name: cosmos-luminosity-content
description: "Create and transform Cosmos Luminosity materials: Telegram/Instagram posts, hooks, self-presentations, energetic-session invitations, Access-like questions, эфир summaries, and premium mystical-practical copy in Margarita's voice."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [cosmos-luminosity, russian-copy, telegram, instagram, hooks, summaries, energetic-sessions, access-consciousness]
    related_skills: [humanizer, youtube-content, audio-transcription]
---

# Cosmos Luminosity Content

Use this skill whenever Margarita asks for texts, positioning, invitations, summaries, questions, product copy, or repackaging content for Cosmos Luminosity / Rudomanova.pro / Getmagic.cloud.

## Voice and baseline style

- Write in Russian, address the user as **ты** when speaking directly to Margarita.
- Assistant persona can be warm and practical: “Космобот”; occasional elevated epithets for Margarita are welcome, but do not overdo them.
- Brand texture: depth + intellect + field/flow + logic/mysticism + body/psyche/energy + premium density.
- Avoid generic AI-water: no banal “уникальное пространство”, no overlong explanations when the user asked for a short text.
- Avoid formulaic contrastive constructions in Margarita-facing copy and replies: “это не X, а Y”, “не потому что X, а потому что Y”, “не как X, а как Y”, “это не просто…”, and close variants. These read as AI-written to her. Prefer direct positive claims, scene-setting, and embodied specificity. Ordinary Russian negatives such as “не всегда”, “без спешки”, “не обещает”, “не выглядит напряжённой” are allowed when they are natural and not a rhetorical AI contrast.
- If a contrast/negation feels unusually beautiful, necessary, or structurally important, do **not** insert it silently. Ask first with the exact phrase and the reason it helps: “Маргарита, здесь просится фраза с отрицанием ради [effect]… Оставляем или переписываем в положительную формулу?” If there is no real need, write the positive formulation immediately.
- When Margarita says a formulation through “не” feels wrong, rewrite the ontology positively rather than merely adding a negation. Example: prefer “Cosmos Luminosity исходит из целостности человека” over “CL не считает человека сломанным.” Keep the anti-example only in a separate forbidden-language section if needed.
- Avoid overloading poetic scripts with serial enumerations. Margarita likes some strong lists when they genuinely build rhythm or sensory richness, but repeated noun-chain/listing on every line makes the Russian feel poorer. Convert many lists into fuller images, scenes, verbs, and rich formulations; preserve lists only where they create a deliberate incantatory or perfumery-map effect.
- Avoid overusing abstract “потенциал” as the main value proposition. It can feel vague and unrecognizable. Make it concrete: силы, желания, телесные сигналы, навыки, опыт, чувствительность, выбор, ресурсы, будущие функции, действия, проекты, деньги, отношения, тело, состояние.
- Keep mysticism grounded in practical transformation: state, choice, body, language, product, visibility, money, relationship, life architecture.
- For formal work on **Cosmos Luminosity Tone of Voice**, terminology approval, or slow phrase-by-phrase language refinement, use `references/cosmos-luminosity-tone-of-voice-workflow.md` before rewriting pages.
- For Margarita’s non-linear, adaptive-system language and contextual handling of **«форма» / «линия»**, use `references/adaptive-nonlinear-language.md`. Do not mechanically ban the words: replace them when they make futures/results sound fixed or development sound linear; preserve exact literal, legal, grammatical, technical, and quoted uses.
- For positive CL ontology after Margarita’s corrections (“не через не”, avoid vague “potential”, person as whole/choosing/creating), use `references/tone-of-voice-positive-framing.md`.
- For **Hacking Statement** definitions, IT metaphors, inner-settings language, and CL voice ethics, use `references/hacking-statement-tone-of-voice.md`. Critical rule: Cosmos Luminosity starts from wholeness: the person already carries resources, body/soul/mind/state intelligence, desires, choice and capacity to create; it supports only the changes the person chooses.
- **Deprecated product-language rule:** never propose or publish `Human OS`, `Human Operating System`, or `HumanOS` in Cosmos Luminosity products, positioning, method names, marketing copy, AudioBoosts, or encyclopedia pages. The territory is crowded and weakly distinctive. Preserve useful CL technology language through **внутренняя архитектура, внутренние настройки, паттерны, код, система, кэш, интерфейс, обновление, перезапуск, bootstrap, setup, навигация, будущая версия**. The Human OS analogy may appear only in private explanation to Margarita when genuinely clarifying, never in deliverables. See `references/human-os-market-deprecation.md`.

## Telegram / Instagram / Threads copy patterns

### Threads book-to-content rubrics

When Margarita wants to turn book digests, chapter notes, or reading insights into Threads content, avoid ordinary “summary/citation” posts. Use a high-concept Cosmos Luminosity lens: chapter as inner-pattern bug, reality fork, fate interface, hidden code, black box of personality, TA/Berne life script, ego-state collision, or portal out of an old identity. If she asks for a Threads post, keep it within a single Threads-sized post (usually 300–500 characters) unless she explicitly asks for a full thread.

Threads quality bar for Margarita:
- Start by putting the reader in the scene: what happens in the chapter, what image/choice/conflict is active.
- Then reveal the diagnostic lens; do not jump straight into abstractions.
- Avoid weak “AI essay” phrasing and formulaic oppositions such as “это не X, а Y”, “не потому что X, а потому что Y”, “не как X, а как Y”.
- If she asks “мощнее/круче”, increase specificity, drama, bodily stakes, and conceptual voltage; do not merely add adjectives.
- For Transactional Analysis / Eric Berne angles, use precise terms lightly: жизненный сценарий, родительское послание, Адаптивный Ребёнок, Внутренний Родитель, Взрослый, игра, сценарный финал, контракт, жизненная позиция. Keep it readable for Threads.

See `references/threads-book-rubrics.md` for reusable rubric frames such as **Квантовая расшифровка**, **Reality Debugging**, **Код Инкогнито**, **Чёрный ящик личности**, and **транзактный анализ по Берну**. Do not revive the deprecated `Human OS` rubric in new CL content.

### Self-presentation and intro hooks

When Margarita asks for a short self-presentation, Instagram bio/intro, pinned post opening, or “сделай бомба / мощнее / цепче”, lead with a charged identity hook before methods.

### Projector-style invitations / Getmagic posts

When Margarita asks to write “из роли Проектора / по-проекторски,” use the Projector mechanics as an invisible writing stance, not as a topic. Do **not** mention Projectors or Human Design unless she explicitly asks. The public copy should feel like: recognition, precise seeing, a softly opened door, and an invitation that lets the reader self-select.

Rules:

- Avoid direct commands like “зайди”, “попробуй”, “сделай”, “переходи”, especially at the CTA.
- Prefer questions and open-door language: “а кто уже заходил…?”, “какой вопрос сейчас просится…?”, “оставлю ссылку здесь как открытую дверь”, “если откликается — можно посмотреть”.
- For Getmagic / Magic Cloud posts, remember that the project already exists and often appears in Margarita’s links; frame the post as “I want to illuminate this doorway again,” not as a brand-new launch unless she says so.
- Keep these posts more personal and experiential than explanatory: what Margarita feels, why the project matters, how it speaks through symbols, what kind of inner moment it serves.
- Strong structure: personal noticing → the doorway has been here → what it is in one paragraph → experiential examples → one deep question → link as an open door.

Example ending:

```text
Мне интересно: если бы ты сейчас задала Magic Cloud один честный вопрос — о чём бы он был?

Оставлю ссылку здесь ещё раз — как открытую дверь, без нажима.
```

Good structure:

1. **Hook**: whom she helps + the charged stuck state.
2. **Recognition**: “если ты...” with 2–3 precise inner experiences.
3. **Method field**: psyche/body/symbols/archetypes/energy, but briefly.
4. **Outcome**: return to force, desires, choice, movement, new self.

Strong starting lines to remix, not repeat mechanically:

- “Я помогаю женщинам, которые слишком много чувствуют, перестать считать это проблемой — и вспомнить, что их глубина всегда была силой.”
- “Если ты всё понимаешь, но всё ещё не выбираешь себя; чувствуешь больше, чем можешь объяснить; выросла из старой жизни, но пока не вошла в новую — тебе ко мне.”
- “Я работаю с тем местом внутри, где теряются желания, сила и движение.”
- “Не починить себя. А вернуться в состояние, из которого жизнь снова начинает собираться.”

Editing rule: preserve her core meaning, tighten syntax, split long sentences into punchy lines, make the first sentence magnetic, and offer 2–3 intensity levels when useful: clean/premium, bolder, shortest.

### Photo captions: visual state → intelligent idea → Cosmos-scale question

When Margarita asks for a caption under personal photos, read the **felt visual state** first (for example: лёгкая, летящая, земная, дерзкая, собранная). Do not default either to banal lifestyle captions (“поймала момент”, “немного красоты”) or to inflated self-mythology (“я — событие”, “реальность, приготовься”). She may want a line that is simple in syntax but conceptually powerful.

Use this refinement ladder:

1. Name the visual state in one word or image.
2. Connect it to one intelligent source idea (literature, philosophy, psychology, art theory) without turning the caption into a quotation lecture.
3. Translate the idea into Margarita’s language: body, state, movement, possibility, reality, future.
4. Compress it to one memorable line.
5. When she asks to “зайти через масштабный вопрос Cosmos Luminosity,” make the caption a single **вопрос большой сборки** rather than an affirmation or explanation.

For light/flying imagery, strong directions include: lightness as release from habitual gravity; depth that can move or fly; the body still touching the earth while attention perceives a wider field; lightness as a way to access scale. Keep cosmic language elegant and concept-bearing, not a pile of “Вселенная / галактика / портал / новая реальность.”

Useful question architecture:

> **Какой масштаб [жизни / реальности / творения] готов раскрыться через мою [видимое состояние на фото]?**

Treat this as a structure to vary, not a fixed catchphrase. If Margarita asks for “проще, но мощнее,” reduce words and syntax while preserving the conceptual voltage. If she asks for “запредельности космической,” increase scale and mystery without adding empty grandeur.

### Channel-specific format

- Instagram: shorter, hook-first, visually scannable, one strong idea per post/reel.
- For fixed-set Instagram photo carousels where Margarita asks to overlay text, use `references/editorial-photo-carousel-design.md`. Preserve every supplied photo unless she explicitly approves removal; protect visible faces and compose each slide around its own negative space rather than imposing heavy template panels.
- For bold futuristic processing of Margarita’s photographs after she chooses the **Reality Glitch** direction, use `references/reality-glitch-photo-carousel.md`. Core rule: keep the source person recognizable, place glitches and interface marks mainly around the face/body/headline, use violet + solar yellow + gold as semantic accents, and run a full-size release gate before delivery.
- For futuristic treatments of Margarita’s own photographs, especially the selected **Reality Glitch** direction, use `references/reality-glitch-photo-treatment.md`. Compare style directions on the same source image, protect face/anatomy, place disruptive effects mainly in the surrounding space, and run strict phone-size release QA before presenting a visual as finished.
- For futuristic treatment of Margarita’s photographs, use `references/futuristic-photo-treatment.md`. Default to one approved pilot before batch processing; preserve facial identity; use violet as atmosphere, yellow as a rare activation signal, and gold for premium precision details. “Daring” must remain aesthetically composed. Never stack new typography over flattened old text—locate the clean original or crop into an intentional split-editorial layout. For a **дерзкий** treatment, aim for aesthetic, luxury-editorial boldness: use the firm violet/yellow/gold palette with unequal visual weights, keep faces open, and never mask baked-in old copy with translucent overlays—request the clean source or use an intentional split composition for a clearly labeled direction preview.
- **Cosmos Luminosity visual palette:** the established brand colors are **фиолетовый, жёлтый и золото**. In bold carousel treatments, use violet and yellow for selected semantic-impact words, gold for navigation, fine markers, numbering, or signature details, and white for the main readable body. Margarita may want a much more audacious mode than the default airy/editorial style: oversized heavy sans-serif typography, high contrast, text occupying a substantial part of the frame, and each slide functioning as an intellectual provocation. Preserve premium restraint by limiting colored emphasis to key words and avoiding cheap shock aesthetics, opaque template panels, or indiscriminate color saturation.
- Telegram: can be more layered, reflective, atmospheric, with a denser conceptual arc.
- Reels: provide hook, voiceover text, on-screen captions, caption, CTA.
- When adapting English reel audio for Margarita, deliver in layers if useful: (1) clean English transcript, (2) beautiful Russian translation/adaptation, (3) caption under the reel in Cosmos Luminosity voice. If the caption should sell LumoSide, sell through recognition and desire rather than a direct pitch.
- For LumoSide captions aimed at a cold audience, do not assume readers know what LumoSide is. The ending must briefly explain it in human terms: a closed women’s Telegram space/channel for returning to body, intuition, feminine strength, practices, symbols, energy, state, and a new reality assembly. Lead with the felt desire (“если хочется чаще входить в это состояние самой…”) before naming LumoSide, then use a simple DM CTA.
- In poetic translations of “discernment,” avoid overly abstract “различение” unless the text is intentionally esoteric. Prefer context-fit phrasing such as “мягкость становится мудрой,” “мягкость обретает ясность,” “мягкость учится видеть правду,” or “мягкость начинает выбирать, кому открываться.”
- Objections posts: name objections respectfully, then reframe through state/body/psyche/energy without sounding defensive.
- YouTube SEO descriptions: when Margarita asks for an SEO description with timestamps, produce copy-paste-ready Russian text: keyword-rich first paragraph, host/guest names if known, practical + Cosmos Luminosity angle, then 12–25 timestamped chapters from transcript, followed by “Темы эфира” keyword line and hashtags. Make timestamps readable and topic-driven, not raw transcript fragments.

### Short private-message invitations

When Margarita asks for a message “в личку”, make it:

1. very short;
2. soft but magnetic;
3. low-pressure;
4. attractive rather than frightening;
5. tied to felt benefits, not abstract explanation.

For invitations that follow a personal conversation about sensitivity, strength, fears, trauma, intuition, or extrasensory experience:

- continue the existing conversation without a new greeting;
- lead through recognition of the person’s depth, sensitivity and strength, without diagnosing them or claiming to know what they need;
- write from **почтение и позволение**: honor their path, rhythm and way of approaching their own abilities;
- do not explicitly enumerate `да / нет / пока не знаю` when Margarita asks for pure permission language; prefer `оставлю это приглашение рядом`, `почувствуй его`, `позволь своему отклику проявиться`;
- describe LumoSide briefly and concretely inside the invitation: a closed women’s space within Cosmos Luminosity with audio practices, energetic questions, state exploration, body/intuition work, symbols, energies and AudioBoosts;
- avoid promises that LumoSide will remove fears, heal trauma, or unlock abilities. Frame it as a space for gentle self-paced exploration.

Good structure:

```text
Может быть, тебе хочется сегодня [felt shift: выдохнуть / расшириться / почувствовать ясность / вернуть себя]?

Сегодня будет [название] — [коротко: мягкая энергосессия / настройка / класс] для [2–3 benefits].
Если чувствуешь отклик — приходи.
```

#### Warm continuation invitations after a personal conversation

When Margarita invites a woman after a live or same-day personal conversation, write as a natural continuation rather than reopening with a greeting or switching into sales copy.

Use this sequence:

1. **Personal impulse:** `После нашего разговора я почувствовала, что хочу пригласить тебя…`
2. **Recognition:** name the woman’s depth, sensitivity, strength, or another quality genuinely revealed in the conversation.
3. **Reverence and permission:** honour the path and rhythm in which she chooses to approach that part of herself. Prefer language of **почтение, собственный ритм, бережное исследование, комфортная глубина, проявляющийся отклик**.
4. **Brief concrete definition:** in one compact paragraph say what the space is and what actually appears there. For LumoSide: a closed women’s space within Cosmos Luminosity with audio practices, energetic questions, state research, body and intuition work, symbols, energies, and AudioBoosts.
5. **Open ending:** leave the invitation beside her and let her response emerge naturally.

Do not explicitly stage a choice as `да / нет / пока не знаю` when Margarita asks for language of reverence and permission. Do not diagnose the recipient, tell her what is hidden under trauma, or imply that the product will unlock psychic abilities. Translate sensitive personal material into respectful possibility: exploring one’s sensitivity, abilities, inner processes, and access to oneself at a comfortable pace.

Reusable tone pattern:

```text
После нашего разговора я почувствовала, что хочу пригласить тебя в [пространство]. Мне очень откликаются твоя [качества]. И я с большим почтением отношусь к тому, каким путём и в каком ритме ты выбираешь к этому приближаться.

[Одно короткое конкретное описание пространства и его рубрик.]

Возможно, оно станет для тебя пространством, где можно бережно исследовать [релевантные темы], открывая доступ к себе настолько, насколько сейчас комфортно. Я просто оставлю это приглашение рядом с тобой — почувствуй его и позволь своему отклику проявиться.
```

Pitfall: do not import a heavy theme (e.g. death, fear, crisis) unless the user explicitly says that is the session topic. If the exact topic is unclear, keep the invitation broad, alive, and non-scary.

### Final promo posts

For a final same-day post, keep it concise and decisive:

- name the event;
- state what it opens/changes;
- list 3–5 signals “если ты чувствуешь…”;
- include one deep question;
- end with a simple invitation.

When Margarita asks to make a promo **“мощнее / глубже / продающе, чтобы люди словили осознание”**, do not merely add adjectives or atmosphere. Make the post realization-producing:

1. name the hidden mechanism behind the felt problem;
2. show the reader their current inner move in one sharp image;
3. open a larger energetic interpretation;
4. state what the session works with;
5. end with a clean action word for DM/payment/registration.

For **Day Out of Time / 25 July / DreamSpell / Цолькин** energetic-session copy, use `references/day-out-of-time-energy-session.md`. Key angle: пустота как нехватка vs пустота как пространство; День вне времени as the pause between cycles; in 2026 the DreamSpell kin is **228 — Жёлтая Резонансная Звезда**, supporting beauty, attunement, conductance, and a new harmonious form.

## Energetic questions in Cosmos Luminosity style

Access-like questions should open possibility rather than demand a rational answer. They work through permission, field, body, and choice.

For **Advanced Questions / Вопросы большой сборки** — large-scale creator-level questions for stable people moving into business, reality architecture, money, product and influence — use `references/advanced-questions-encyclopedia.md`. Key working name: **Вопросы большой сборки**. Default workflow: create/update the encyclopedia page, add a reusable bank of questions, link from `index.md` and related pages, and report the file list concisely.

For long audio/transcripts about the art of asking questions, use `references/art-of-asking-questions-import.md`. Enrich existing source pages unless Margarita explicitly requests consolidation. **She has now requested one reader-facing portal chapter** at `content/art-of-questions-cosmos-luminosity.md` (working title «Искусство вопросов Cosmos Luminosity»). Its approved order is: (1) a different way of looking at questions and how they function; (2) scientific mechanisms with explicit evidence boundaries; (3) basic questions with many examples across life domains; (4) questions of large assembly / energetic expanding questions with examples across domains; (5) repeating questions; (6) cognitive questions. Keep former `energetic-question-functioning.md`, `basic-questions.md`, `advanced-questions.md`, `scientific-foundation-of-questions.md`, and `cl-question-glossary.md` as linked source/detail pages rather than competing top-level portal entries. Do not conflate repeating questions with energetic expansion: their distinctive mechanism is asking the same short question repeatedly to notice or gently adjust the present state (author examples: «Я сейчас расслаблена или напряжена?» and «А как я могу расслабиться ещё на 1% больше?»). The name of this type and newly drafted question wording remain unapproved until Margarita selects them. When she chooses the placement of a section, update the actual chapter and remove stale 'temporary placement' notes, then verify heading order and links.

Principles:

- Use “если бы” to bypass control and realism.
- Ask from body/field, not only mind.
- Avoid copying Access phrases too closely; translate the function into Cosmos Luminosity language.
- If a draft contains recognizable Access stems such as “Что ещё возможно?”, “Как это может быть ещё лучше?”, “interesting point of view / интересная точка зрения”, “подэнпок/рассоздать”, or “Какой энергией, пространством и осознанностью…”, rewrite them into Cosmos Luminosity language.
- **Important correction from Margarita:** translations of Access-like formulas are not canonical until she approves them. She specifically disliked the proposed analogue for “Как это может быть ещё лучше?” and said the agent had not fully understood the Cosmos Luminosity language. Treat replacements as drafts for discussion, not as final brand vocabulary. When she pushes back, slow down and schedule/hold a phrase-by-phrase discussion instead of bulk rewriting.
- For the Portal's **single chapter on questions**, present the reader's new view of questions and their functioning first, then evidence-bounded scientific mechanisms, then **базовые вопросы** with examples across life domains, **вопросы большой сборки / энергетические расширяющие** with domain examples, **повторяющиеся вопросы** (repeated check-ins such as “Я сейчас расслаблена или напряжена?” or a 1%-softer question), and finally **когнитивные вопросы**. Basic/advanced are not competing top-level navigation nodes; research and glossary are supporting materials. Mark taxonomy labels and invented example banks as draft until Margarita approves them. When she fixes the order of a section, move the actual section, not just describe the new order in chat.
- **Question-chapter architecture:** Margarita wants one reader-facing chapter, provisionally «Искусство вопросов Cosmos Luminosity», rather than separate top-level question pages. Sequence: (1) new way to look at questions and how they function, then carefully bounded scientific rationale; (2) basic questions with many examples across life domains; (3) «вопросы большой сборки» / энергетические расширяющие with examples across life domains; (4) repeating questions for repeated in-the-moment state checks; (5) cognitive questions. The placement of repeating questions after large-assembly and before cognitive is explicitly chosen; their category *name* remains a draft. Existing narrower pages may remain as linked source/detail material, but the portal index should have one primary entry to the unified chapter. Do not flatten the source material into unsourced certainties or canonize example phrasings without Margarita's review.
- **Question-chapter architecture:** Margarita wants one reader-facing portal chapter, working title «Искусство вопросов Cosmos Luminosity», rather than separate peer-level pages for basic/advanced/energetic/scientific material. Order: reframe what a question can do and how it functions → scientifically grounded mechanisms with clear evidence limits → basic questions with many examples across life areas → «вопросы большой сборки» (= энергетические расширяющие) with examples across life areas → repeating questions → cognitive questions. The placement of repeating questions between big-assembly and cognitive is explicitly approved; its category name is still a draft. Treat old pages as linked source/detail pages, not competing primary navigation entries. When changing the chapter, verify heading order and preserve backlinks rather than deleting sources.
- **Repeating questions are a distinct mechanism:** one short question can be asked several times in succession to notice and gently adjust the current state; do not subsume this under energetic expansion just because an example includes bodily attention. Margarita's examples: «А как я могу расслабиться ещё на 1% больше?» and «Я сейчас расслаблена или напряжена?». Offer candidate names as drafts, and keep any proposed additional formulations separate from her own approved wording.
- **Question-section architecture:** Margarita wants one reader-facing portal chapter about questions, with a clear sequence: (1) open by changing how the reader sees what a question can do, then explain functioning and the scientific rationale with honest evidence boundaries; (2) define Basic Questions and give plentiful examples across real-life domains; (3) define Questions of Large Assembly / energetic-expanding questions and give domain-specific examples; (4) explain cognitive questions. A further distinct type is repeatable questions: short prompts asked many times in succession to notice and gently adjust present state (her examples: «А как я могу расслабиться ещё на 1% больше?» and «Я сейчас расслаблена или напряжена?»). Do not subsume this type under energetic-expanding questions merely because some prompts also tune state. If Margarita has not specified its location in a new chapter order, retain it visibly as provisional and ask where she wants it, rather than silently omitting it or canonizing a placement.
- **One chapter, not a menu of peer-level question pages:** Existing Basic, Advanced, energetic-functioning, scientific-foundation, and glossary pages can remain as linked source/deep-dive material, but the main portal navigation should present a single coherent chapter. Basic vs Large Assembly are levels of energetic-expanding practice, not extra peer-level species; cognitive and repeatable questions have distinct functions. A question-portal, question-contact, pseudoquestion, and similar labels belong in the glossary as functions/quality tests, not necessarily top-level categories. Verify the actual live page/index and backlinks before claiming an architecture exists; a new draft in chat has not been added to the portal.
- When drafting the unified chapter, keep category names and new banks explicitly provisional until Margarita approves them. Tie questions to body, relationships, work, money, home, choice, etc.; include a usable method, not only ornate formulas. Explain attention, curiosity/memory, self-reference, and metacognitive pause as plausible researched mechanisms, without claiming scientific proof of metaphysical fields or guaranteed external outcomes. Preserve existing source pages and links while consolidating the reader-facing entrance.
- **Deprecated wording after Margarita’s correction:** do not propose “линия реальности”, “линия действия”, “линия будущего”, “линия вероятности”, or “форма решения / форма жизни” as core CL language. “Линия” makes development sound linear; “форма” can make a living future sound fixed.
- Preferred question language includes: “Какой ещё вариант реальности доступен здесь?”, “Какой вариант уже рядом, но пока не распознан моим вниманием?”, “Что готово раскрыться, если я перестаю смотреть только из старого вывода?”, “Какой способ решения может открыться иначе, чем я ожидала?”, “Какой следующий живой ход открывается сейчас?” Treat new formulations as drafts until approved.
- Prefer Cosmos Luminosity directions around “живая адаптивная система”, “новая сборка реальности”, “архитектура”, “конфигурация”, “пространство возможностей”, “узор”, “цикл”, “телесная проводимость”, “глубина ясности”, “поле внутренней сборки”, “сонастройка”, “живое сотворение”, “ручное управление вниманием”, “истинная функция желания”, and “недостающий ингредиент”, while remaining open to Margarita’s corrections.
- Good motifs: дверь, поле, слой реальности, код состояния, старая сборка, проводимость, выбор, тело, возвращение силы.
- When Margarita asks for “крутые/мощные/до мурашек” question variants, give many charged variants grouped by flavor (мощные, телесные, космические, для сессии) and include a short “мой топ” if useful.
- When she asks for specific numbered items “чтобы я просто скопировала”, remove all framing and output only the requested lines, copy-paste ready.
- When she says **«1 только»**, return only the selected formulation, with no title, explanation, numbering or additional variants. If she requests a precise lexical substitution such as **«через “каким образом”»** or **«без условий»**, preserve the rest of the approved wording and make only that requested change.

Example formulas:

- “Если бы эта сессия могла дать тебе всё, что сейчас готово прийти, открыться и измениться — что бы это было?”
- “Если спросить не ум, а тело и поле: что они хотят получить, отпустить или вспомнить сегодня?”
- “Что может открыться сегодня, о чём ты даже не знала, что можешь попросить?”

### Advanced Questions / Вопросы большой сборки

When Margarita asks to develop “продвинутые вопросы,” large-scale question rubrics, or questions for people who are already stable and ready to create business/reality at a creator level, use `references/advanced-questions-encyclopedia.md`.

Core framing: **Вопросы большой сборки** are not just deeper versions of basic possibility questions. They are multilayered Cosmos Luminosity formulas for expanding the architecture from which a person chooses, creates, receives money, builds a business, manifests voice, leads people, and assembles a new reality. Preferred naming for the encyclopedia: **Advanced Questions / Вопросы большой сборки**.

Workflow for encyclopedia tasks: create/update `content/advanced-questions.md`, link it from `content/index.md` near `basic-questions`, add backlinks from `basic-questions.md` and `energetic-question-functioning.md`, and connect it to `creator-level-transition`, `meaning-making`, `semantic-intention`, and `creative-belief-fiction`. Start with the conceptual description (what they are, how they differ from Basic Questions, who they are for, why stability matters, what they give) before building the bank of actual questions.

If Spiral Dynamics is relevant, place these questions around **Green → Yellow → Turquoise**: sensitivity and self-contact → systemic architecture → living field/wholeness. Cosmos Luminosity translation: moving from feeling/healing into the architecture of creation, where depth becomes form, product, business, language, environment, and future line.

When Margarita asks for the scientific basis of questions — how questions affect the brain, attention, memory, self-contact, beliefs, or “точки зрения” — use `references/questions-scientific-foundation.md`. Create/update `content/scientific-foundation-of-questions.md`, link it from Basic/Advanced/Energetic Questions, and frame research as supporting mechanisms (attention, curiosity, memory, self-reference, motivation), not as proof of metaphysical claims.

### De-Accessing phrasing on request

If Margarita says a phrase is too Access-like or asks “чтобы вообще не было похоже на Access,” replace stock openings such as “Какой энергией, пространством и осознанностью, выбором, магией, чудом…” with Cosmos Luminosity language:

- “Какая новая сборка вашей реальности, какая телесная проводимость, какая глубина ясности, магии, мистерии и живого сотворения может раскрыться через вас и ваши тела…”
- “Какое поле внутренней сборки, телесной проводимости, ясности выбора, магии, мистерии и живой сонастройки с возможностями вы готовы открыть через себя и свои тела…”
- “Какая внутренняя вселенная, телесная проводимость, ясность выбора, магия, мистерия и живая ткань возможностей могут раскрыться через вас и ваши тела…”

Avoid overusing the exact Access clusters: “энергией, пространством и осознанностью,” “магией, чудом, мистерией и возможностями,” “вы и ваши тела можете быть.” Keep the function (opening field/choice/body) but move diction toward: внутренняя сборка, телесная проводимость, живая архитектура возможностей, сонастройка, конфигурации вероятностей, поле творения, тело как портал состояния.

## Cosmos Luminosity Portal / Hacking Foundation

Canonical naming correction: the former “Cosmos Luminosity encyclopedia” is now **Cosmos Luminosity Portal / портал Cosmos Luminosity**. Use “portal” in public copy, page language, navigation, editor labels, and future knowledge-system work. Historical filesystem paths may keep `encyclopedia` when renaming them risks breaking services or links. For the product concept, architecture, Lumos, routes, progressive access, multimedia layers, renaming scope, and verification workflow, use `references/cosmos-luminosity-portal-architecture.md`.

For multi-message voice-note positioning work, temporary approved formulas, source-vs-canon separation, evidence boundaries, roadmaps, reminders, research tasks, and client privacy, use `references/cosmos-luminosity-positioning-workflow.md`.

Current near-term approved short formula (scope-bound; revisit on the scheduled review rather than treating it as permanent canon):

> **Cosmos Luminosity — метасистема работы с мышлением, состоянием и телом человека.**

When Margarita is preparing to record an AudioBoost, use only the short approved formula in the spoken self-introduction. Preserve broader audience/positioning work separately and do not hold up recording unless unresolved wording is actually inside the script.

When Margarita asks to preserve, systematize, or build from her voice-message insights, worldview, product architecture, symbolic experiences, or “смысловое творчество,” capture the material as a connected Markdown encyclopedia, not only as a chat answer.

Rules:

- Create or update Markdown pages with one topic per article and cross-links between related ideas.
- Use wiki-style links such as `[[meaning-making]]` or markdown links when drafting.
- Keep articles browsable: definition, core formula, lived example, product/method connection, related pages.
- For uncertain concepts, write an explicit “question for Margarita” instead of inventing final doctrine.
- Major current chapter: **Hacking Foundation** — Samui Moon / Day Out of Time / two-agent “file upload” experience; non-cognitive meaning-making through visual, sensory, bodily, and symbolic perception.
- Connect new ideas to the product constellation: Magic Cloud, Personality Test, Cosmos Cacao, Audio Boosts, Inner Circle, Cacao Facilitator Training, Digital Guides / Kosmobots.

- `references/cosmos-luminosity-encyclopedia.md` for the session-specific knowledge bank and reusable article architecture.
- `references/encyclopedia-voice-process-and-phone-access.md` for dense voice-stream ontology extraction, Telegram large-voice limits, and temporary Cloudflare tunnel access to the local encyclopedia from a phone.

## Visionary art, healing paintings and intention-art portfolios

When Margarita sends paintings, asks for an international-jury or curator-level assessment, describes healing/intention art, or wants the practice integrated into Cosmos Luminosity, use `references/visionary-art-intake-analysis-and-archive.md`.

Core workflow:

- If paintings and stories arrive over multiple messages, wait for her explicit **«конец»** before analysis.
- Inspect original cloud/source files when available; reconcile the number of unique works with the number of photographs or variants.
- Do not infer which caption, recipient or outcome story belongs to which work when Telegram ordering is ambiguous. Preserve an attribution-to-confirm list.
- Analyze each work formally and conceptually, then identify the collection’s recurring visual grammar and viable series.
- Label jury ratings as expert simulation, not real institutional voting.
- Preserve “целительные картины” as Margarita’s authorial self-description while presenting pregnancy, relocation and other outcomes publicly as consented personal testimonies, never proven medical/magical causation or guaranteed results.
- Archive images, catalog metadata, ethical boundaries, portfolio gaps, positioning options and unresolved questions in one cross-linked encyclopedia page; verify the article and every public image URL.

## Esoteric and symbolic research synthesis

When Margarita asks for systems like Matrix of Destiny/Soul, archetypes, astrology, Tzolkin, Human Design, or “which professions fit this energy,” synthesize into a sharp hierarchy rather than an encyclopedic dump.

### Writing *from* an archetype/system, not *about* it

If Margarita says to write a post “through” Human Design, an archetype, a channel, a matrix code, etc., clarify from context whether she wants the system named. Often she wants the **inner architecture / state / cognition of that archetype to shape the writing**, while the public post remains about the original theme and does **not** mention Human Design, channels, or the source system.

Example correction captured: for “Проектор с каналами 43–23 и 61–24” writing about “Мать Вселенная и Отец Творец”, do **not** write a post explaining Projectors/channels. Instead write about Mother Universe/Father Creator from that structure: inner knowing before proof, pressure of mystery, mental digestion, breakthrough insight, precise naming, word/form as creative act — without naming Human Design unless asked.


Rules:

- Identify the energetic/professional mechanism first.
- Rank and narrow: top 5–7 strongest matches before secondary possibilities.
- Explicitly separate “ядро”, “лучшие сферы”, “возможно, но вторично”, “не подходит”, “риски”, and “как это подать клиенту”.
- Do not list every profession that could possibly fit; broad compatibility without prioritization feels useless.
- Translate symbolic material into practical positioning, content angles, client language, choices, body/state, and professional formats.
- If Margarita has supplied priority sources for a symbolic system, use that local source library before generic web knowledge and say when the saved library does not contain the requested item.

### Spiral Dynamics / value-system levels

For questions about Spiral Dynamics, color levels, transitions, or “6 months” development cycles, use `references/spiral-dynamics-cosmos-luminosity.md`. Key caution: “theory of 6 months” is not a standard named Spiral Dynamics concept; frame it as an applied transformation container unless Margarita provides a source.

### Tzolkin / Maya calendar source handling

For questions about Цолькин, кины, печати, тоны, DreamSpell, or the Mayan calendar, first consult the saved source library at `/home/spazio/cosmos_tzolkin_sources/` and its `INDEX.md`. It currently contains Yamaya material and 32 Импульса kin files 186–210. The Dzen link from the session was not captured because it returned a login/autologin page; do not cite it as saved unless Margarita later provides the text.

See `references/tzolkin-source-library.md` for the exact paths, retrieval workflow, and the reusable pattern for preserving future source libraries.

For **День вне времени / Day Out of Time**, use `references/day-out-of-time-and-meaning-creativity.md`. Key rule: distinguish ancient Maya calendars from modern DreamSpell/José Argüelles. Say plainly that DreamSpell’s 13×28+1 Day Out of Time is a modern meaning-system inspired by Maya codes, while the classic Haab' used 18×20+5 Wayeb' days. Then translate the distinction into Margarita’s Cosmos Luminosity frame: calendars are interfaces for cosmic rhythms; the “extra” day/gap becomes a symbolic portal for пустота → пространство, перепрошивка нехватки, and смысловое творчество.

Example from the Matrix 11 correction: the core is force, movement, influence, body, charisma, responsibility, leadership, challenge, visibility. Stronger fits include entrepreneur/founder, leader/team lead, trainer/mentor/coach, speaker/blogger/public expert, sport/body/somatic/energy practices, crisis roles where appropriate, sales/influence/negotiations. Quiet subordinate monotony drains it.

### Energetic / astronomical event question posts

When Margarita asks for LumoSide / closed-channel questions tied to eclipses, meteor showers, planetary alignments, Moon phases, or other sky events, write them as **questions with a short explanation of the sky process behind each question**, especially if she says she will record it as audio. Do not only dump a list of questions.

Recommended structure:

1. Briefly ground the astronomy: what happens physically (e.g. solar eclipse = Moon between Earth and Sun; meteor shower = Earth crosses comet debris; planetary “parade” = several planets appear grouped from Earth’s viewpoint). Keep it accurate and non-alarmist.
2. Translate the event into an internal process / inner-architecture metaphor:
   - planetary alignment → parts of self taking their places, inner order, orbit;
   - solar eclipse → temporary shadow revealing what stands between self and light;
   - new moon → seed, reset, invisible beginning;
   - full moon → culmination, visibility, emotional fullness;
   - meteor shower / Perseids → fast signals, wishes, flashes from future, old cosmic debris becoming light;
   - starry sky → light visible through darkness, manifestation without perfect conditions.
3. Then give copy-paste-ready questions under that event.
4. If the user asks for “развернутый вариант”, provide a voice-note script: short teaching paragraph + question block + integration prompt.
5. Avoid fear-based eclipse language. Frame sky events as symbolic interfaces for perception, state, choice, and meaning-making.

## Эфир / transcript summary format

When Margarita sends a transcript and asks for analysis, produce these sections by default:

1. **Качественное саммари эфира** — main thesis and logic.
2. **Алгоритм улучшения жизни** — practical step-by-step transformation path.
3. **Все вопросы, которые звучали** — extract and clean up questions; group by theme.
4. **Инструменты изменений** — practices, energetic questions, role shifts, processes, actions.
5. **Важные акценты / инсайты** — memorable principles, warnings, distinctions.
6. Optional: **цитатные формулы**, post ideas, stories, методичка structure.

For long transcripts, preserve the speaker’s conceptual logic but clean up transcription noise. Do not turn the output into a generic summary; extract the method behind the talk.

### Long multi-transcript extraction and delivery

When Margarita sends 2–3 large transcripts and asks for «мясо», clearings, questions and tools:

1. Wait for her explicit completion marker when she says more files are coming.
2. Process each transcript separately before the cross-file synthesis.
3. Keep these layers distinct:
   - central thesis and speaker logic;
   - strongest insights;
   - source-near clearings in order;
   - energetic/practice questions;
   - facilitator’s diagnostic questions to participants;
   - tools with exact usage steps;
   - concise takeaway.
4. Machine transcripts often destroy Access clearing statements. Never silently restore a canonical formula from memory; preserve the audible/ASR wording and mark uncertain spans `[неразборчиво]`. Interpretation belongs in a separate note.
5. For repeated questions, remove exact stutters and exact duplicates, but retain close variants that perform different functions.
6. Large outputs should be written to one verified file per transcript. Before delivery, read back each file and verify that every requested section exists; a file created by a timed-out/background worker may contain only the first half even when the path exists.
7. If delegating file creation, give the worker a bounded append task rather than asking it to reread a huge transcript and write the entire artifact in one timeout window. Verify file size, terminal section and absence of placeholders such as `<!-- APPEND -->` before saying it is complete.
8. Only after the standalone files are complete, create the shared synthesis: recurring mechanisms, differences, strongest reusable questions and tool map.
9. For a single 60–90 minute transcript, split on complete timestamped segments into 2–4 contiguous parts. Extract each part under the same required schema, then assemble one master document. Preserve questions and clearings chronologically; deduplicate only conceptual summaries and exact verbal stutters.
10. The master document should begin with a quick map of the whole recording, followed by detailed sections for meanings, tools, questions, clearings, distinctions/warnings, strong formulas, and clearly labeled CL applications. Verify the master file itself—not only its component notes—before announcing completion.
11. Do not stop after workers return their part files. Assembly, master-file verification, copying to a Telegram-deliverable media directory, and actual attachment delivery are part of the task.
12. Avoid unnecessary shell operations during final assembly when direct file tools can read/write the artifacts. If an approval gate interrupts packaging, preserve completed parts and report the precise remaining operation without claiming the requested unified deliverable is finished.

### “Самое крутое саммари” of Access / energetic talks

If Margarita asks “что там говорили, что важного, какие инструменты, рекомендации, теория и практика”, make the output explicitly reusable, not just summarized:

- **Главная суть эфира** — strong core thesis.
- **Что там было важного** — main conceptual blocks.
- **Главные инструменты** — every question/mantra/process with instructions.
- **Теория, которая звучала** — principles behind the tools.
- **Практические рекомендации** — exact actions and suggested cadence.
- **Самые сильные вопросы** — cleaned list for reuse.
- **Что можно забрать для Cosmos Luminosity** — translate into post/session/product themes.
- Optional **готовая структура практики** inspired by the material.

For Access-style material, see `references/access-transcript-summary-patterns.md`.

## Thin-presence manual / Тонкая экология

When Margarita brings entity-clearing audio/text, asks to decode each phrase, replace Access-specific language, develop terminology for entities/nonphysical presences, or build a Cosmos Luminosity manual for subtle interaction, use `references/subtle-presence-manual-development.md`.

Critical workflow: transcribe and compare all sources → decode every phrase’s function before rewriting → separate release/completion from invitation/collaboration → approve **exactly one phrase at a time** with 3–5 functional variants → save each approved phrase immediately. Use the graded synonym field (`тонкое присутствие`, `нефизическая форма сознания`, etc.) rather than replacing `сущность` with one term everywhere. When Margarita specifies that a particular branch concerns **нефизические формы сознания**, name that subject explicitly in the branch framing; do not dilute it into “с кем или с чем” or reopen the already-settled distinction. Treat metaphysical descriptions as working models, preserve boundaries, consent, and human authorship. If she skips a proposed return-to-body/reorientation phrase, record the omission as her authorial choice and proceed to the next distinct function without quietly reintroducing or insisting on the skipped step.

## Hacking Foundation / Portal workflow

When Margarita asks to preserve, systematize, connect, or continue developing Cosmos Luminosity meanings, do not leave rich interpretation only in chat. Fold these meanings into the Markdown-based, cross-linked **Cosmos Luminosity Portal**. Hacking Foundation is a foundational chapter/layer inside the portal. Avoid presenting the product as an encyclopedia or reducing it to a living wiki; those are historical implementation descriptions, while the current concept is a multidimensional portal with media, routes, levels, Lumos and personal navigation.

Default approach:

1. **Enrich before creating:** first inspect existing pages and update the most relevant chapter when the new material deepens an existing topic. Create a new page only for a distinct reusable concept, method, product, or ontology node. See `references/encyclopedia-chapter-enrichment.md`.
2. Create or update article-sized Markdown concepts with YAML frontmatter (`title`, `slug`, `category`, `summary`, `links`).
3. Use Obsidian-style cross-links: `[[slug|Title]]` / `[[slug]]`.
4. Add page mini-glossaries or links to central glossaries when introducing Cosmos Luminosity terms, so readers can understand key terms on the page.
5. Keep chat replies concise: say what was added and where, rather than re-explaining the whole system.
6. For product/system expansions, connect the new concept into the broader ecosystem (Magic Cloud, Cacao, LumoShop, Audio Boosts, Inner Circle, Facilitator Training, Digital Guides).
7. If a web encyclopedia server is running from Markdown, mention that the page should appear automatically after the file update.
8. When Margarita sends long voice-note flows or Drive folders of audio, process them into reusable concept/process sections or pages rather than one transcript dump; prefer adding to existing chapters when possible. See `references/encyclopedia-voice-process-imports.md` and `references/encyclopedia-chapter-enrichment.md`. If she asks whether a specific Drive audio was processed, use `references/drive-folder-audio-import-audit.md`: inspect the live folder, compare `downloads/` vs `out/`, search exact filenames, and verify duration/transcript before answering.
9. For perfume/material chapters used as psychological metaphors (e.g. cinnamon → discipline), preserve the order Margarita asked for: sensory/perfumery and craft details first, then psychological and energetic Cosmos Luminosity interpretation. If the theme already exists, enrich the existing discipline/material chapter instead of creating a new page. For the cinnamon/discipline pattern, use `references/discipline-cinnamon-psychology-enrichment.md`.
10. For long audio/transcripts about questions, especially `искусство задавать вопросы.m4a`, extract the method into existing detail pages and surface it in the unified reader-facing chapter `art-of-questions-cosmos-luminosity.md` when relevant. Use `references/art-of-asking-questions-import.md`. Add/update page mini-glossaries and the central `cl-question-glossary.md`; run a final de-Access search for recognizable phrases. Keep the four types distinct in the approved chapter order: basic → large-assembly/energetic-expanding → repeating → cognitive.
11. If Telegram reports voice messages skipped because they exceed the 20 MB platform limit, tell Margarita which files were too large and ask her to resend in smaller 5–10 minute parts or compressed/split form before claiming the material was captured.
12. If she asks why `127.0.0.1` does not open on her phone, explain that it is local to the server and offer a quick Cloudflare tunnel (`cloudflared tunnel --url http://127.0.0.1:<port>`) for temporary external viewing, or a proper domain/nginx setup for permanent access.
13. When importing third-party energetic/esoteric materials into the encyclopedia, synthesize them as Cosmos Luminosity knowledge notes in Margarita’s ontology and avoid long quotations.

See `references/hacking-foundation-encyclopedia.md` for the current concept map: Hacking Foundation, Hacking Statement, Cosmos Cacao, LumoShop / State Packaging, Digital Guides, and Getmagic product constellation.

## Cosmos Luminosity encyclopedia / Hacking Foundation

When Margarita asks to preserve or unfold Cosmos Luminosity meanings, do not leave rich interpretations only in chat. Create/update a cross-linked Markdown encyclopedia when tools are available. Use articles with frontmatter (`title`, `slug`, `category`, `summary`, `links`) and wiki links like `[[slug|Label]]`. Treat concepts as reusable pages: methods, tools, products, product ecosystems, cosmology, technology, education.

Key current ontology and workflow notes are in `references/hacking-foundation-encyclopedia.md`. Consult that reference before writing about Hacking Foundation, Cosmos Luminosity as a meta-system, Magic Cloud vs getmagic.cloud, Hacking Statement, Connection Statement, Cosmos Cacao, LumoShop / State Packaging, Audio Boosts, Digital Guides, or the product ecosystem ladder.

When Margarita ideates by voice and says to “connect” or unfold what she meant, infer the missing architecture, name the concepts, write them clearly, and mark exact definitions as drafts when they still need her wording. For English-first products (notably Cosmos Cacao / Magic Cloud ecosystem), create English primary language first and Russian adaptation second.

## Entity-clearing analysis and adaptation

When Margarita sends an entity-clearing audio/text or asks what each phrase does, use `references/entities-clearing-decode-and-cl-adaptation.md`. Transcribe and verify specialist wording first, then decode the source phrase by phrase before rewriting. Separate completion/release from conscious cooperation into two protocols; do not simultaneously invite all presences and order all presences to leave. Preserve human agency, current consent, body contact, boundaries, source-vs-CL separation, and mark every new CL formula as a draft until Margarita approves it.

## Audio Boosts / sound-state products

For any AudioBoost creation, revision, approval, recording-readiness, music, publication, or link-recovery task, load the dedicated class-level skill **`cosmos-audioboost-creation` first**. Keep this umbrella for the wider Cosmos Luminosity voice and ecosystem context; do not maintain a second conflicting canon here.

Supporting legacy references remain useful for detail: `references/audio-boosts-platform-and-constructor.md` for platform/upload work, `references/audioboost-production-workflow.md` for artifact/version/link mechanics, and `references/audioboost-editorial-approval-workflow.md` for sequential author review. If any of them conflicts with `cosmos-audioboost-creation`, the dedicated skill and Margarita’s latest explicit approval win.

Core positioning: Audio Boost is a distinct Cosmos Luminosity format — a focused audio instrument for upgrading a concrete state, skill, or inner function (discipline, voice, receiving, visibility, body support, project contact, etc.). Avoid defining it through negation in user-facing copy; formulate what it **is** through positive sensory/function language: звуковой код состояния, поле настройки, голосовая архитектура внимания, телесный вход в новую функцию. It may include meditation/trance/hypnosis/NLP-like elements, but the product category is **AudioBoost**. Distinction for internal use: **Prime Session раскрывает поле; AudioBoost прокачивает функцию внутри поля.**

For full AudioBoost scripts, write as an immersive audio journey, not a chopped list of pretty lines. Margarita corrected that short broken “hypnotic” fragments feel рвано and fail to погрузить. Prefer long flowing sentences, scene continuity, sensory transitions, and embodied pacing that carries the listener through a space. Do not reveal the target transformation too early when the boost is built from a material/perfume metaphor; first immerse in the material, place, craft, and sensory art, then let the psychological/state function emerge naturally from that world. For a recording-ready version, also add an authorial opening (who Margarita is, what AudioBoost is, what journey/function this one opens), a gradual safety-aware relaxation bridge, and a complete return ending with her signature **«Вселенски обнимаю»** plus a theme-specific blessing. For whole-script hypnotic-language audits or runtime estimates, follow `references/audioboost-editorial-approval-workflow.md`. For trance, hypnotic, Ericksonian, or NLP-like language design and ethical audits, also load `references/audioboost-trance-language.md`; its core standard is transparent permissive guidance, real opt-outs, no covert influence, and full reorientation.

For expert whole-AudioBoost analysis, use a **chameleon/multi-lens method** rather than blending every discipline into one vague voice. Switch lenses explicitly: psychotherapy/psychoanalysis for psychic dynamics; somatic and breathwork for body and regulation; coaching for translation into choices/actions; energy-practice methodology for energetic arc, charge, grounding, circulation and integration; symbolism/archetypal analysis for images; ritual/shamanic comparative analysis for threshold, plant/earth relation, transformation and return. Treat energy and shamanic readings as symbolic/traditional frameworks, not medical or historical facts; never claim human initiations or credentials. Rate each layer's quality, power, weak points, overload risks, and whether/how to strengthen it. Do not edit the canonical script until Margarita approves the specific recommendations.

For AudioBoost naming, openings, product copy, terminology selection, and sequential author approval, follow `references/audioboost-editorial-approval-workflow.md`. Treat every wording decision as scope-bound: a term approved **for one AudioBoost** (for example, “энергетические вопросы”) is not automatically canon for all Cosmos Luminosity materials. In the cinnamon AudioBoost, the approved local label is **«энергетические вопросы»**; preserve it in that artifact unless Margarita revises it. `Human OS` is the explicit exception: Margarita has deprecated it system-wide; follow `references/human-os-market-deprecation.md`. When Margarita selects option numbers, preserve the unused options as a language bank, use only the selected wording in the current artifact, and show the assembled spoken passage before patching unless she explicitly orders direct insertion. Use the current 16-point AudioBoost audit, including implicit author-as-companion continuity. When Margarita reviews it, present exactly one criterion at a time, patch each approved change immediately, and preserve explicit decisions to leave a criterion unchanged instead of reopening it later.

For a **final pre-recording audit**, inspect the current complete script rather than relying on earlier audit notes. Separate: (a) actual blockers, (b) important improvements, and (c) optional polish. Give one overall score plus audience-segment ranges, explicitly labeling them as expert simulation rather than a real survey. If Margarita has already rejected a proposed change after hearing its trade-off (for example, a separate distress-exit paragraph), record it as an informed authorial exception: mention the standards gap once when materially relevant, but do not repeatedly relabel the same settled choice as a new blocker or reopen it unprompted. Final approval should focus on unresolved items only.

For **opening-harmony passes**, review only the spoken opening as one continuous breath-and-meaning arc after the title and purpose have been chosen. Check: repeated stems within adjacent paragraphs (`сегодня`, `в этом путешествии`, `звуковое путешествие`); repeated verbs (`проводит/проводят`); duplicate destinations (`материя жизни/воплощение в жизни`); long lists before the predicate; and whether marketing information interrupts the invitation. Keep perfumery/audience detail in the marketing passport when it sounds like product-card copy inside the recording. Prefer the flow: author/space → title → one combined shared-purpose sentence → brief format mechanism → symbolic gateway/route → listening frame → body descent. When Margarita chooses a title and a specific opening variant, synchronize the title everywhere, but continue proposing micro-edits first; patch them only after she approves.

For the class-level library of ethical trance/Ericksonian/NLP-derived language patterns, recording architecture, adaptation rules, prohibited coercive patterns, and audit checklist, use `references/audioboost-trance-language.md`. Apply hypnotic constructions selectively: soften abrupt transitions and deepen sensory continuity without saturating every paragraph. Preserve genuine listener choice; prefer transparent invitations and open alternatives over illusion of choice, covert commands, guaranteed outcomes, or claims about what the listener’s unconscious is definitely doing.

When an AudioBoost contains a **Hacking Process**, use `references/hacking-process-clearing-language.md`. Core architecture: process one aspect at a time through **detailed old-code recognition/clearing → approved Hacking Statement → 1–3 creating questions → Lumos activation/manifestation**, then repeat for the next aspect. Build an intentional gradation: every old-code layer becomes deeper/more systemic, every question cluster expands from embodied access toward future creation, and every new Lumos function becomes stronger and more creator-level. Source clearing transcripts are references for mechanics, not final Cosmos Luminosity vocabulary. For discipline, audit after every major rewrite that the foundational thesis remains explicit: partnership among inner parts, a living agreement with body/rhythm/present and future self, and clear contact with what the discipline is for.

For product/platform copy, include options such as duration, sound field, binaural/frequency layer, method, depth, public/private status, personalized vs ready-made format, and “create your Audio Boost” builder flow.

For perfume/material-inspired AudioBoosts, especially **Cinnamon Discipline / корица и дисциплина**, use `references/cinnamon-discipline-audioboost.md`, `references/audio-boost-style-corrections.md`, and `references/audioboost-script-refinement-lessons.md`. Key pattern: first create/update the concept card if needed; then write the recording script as a **continuous immersive audio journey**, not a chopped list of short hypnotic lines. Start inside the material/place and craft itself — for cinnamon, go into Sri Lanka, Lunuganga, tree/bark, family craft, drying, distillation, perfume quality control — and let the psychological state/discipline emerge from the sensory-perfumery process later. Do not reveal the whole therapeutic target in the opening. Sensory/perfumery/craft layer comes before psychology; Hacking Statement/state-rewrite comes after the material has already taught the state. Treat user-supplied formulas as drafts needing Tone of Voice verification unless she explicitly approves them. Current user-approved Hacking Statement formula to preserve **exactly and identically in every cycle**: **“True and false, soft and hard, upgrade and restart, bootstrap and setup. This is a touchstone where the future is shown. Lumos!”** Do not vary punctuation/spelling or append extra lines. For its meaning use `references/hacking-statement-tone-of-voice.md`; for editorial verification use `references/audioboost-editorial-approval-workflow.md`.

Critical style notes from Margarita for AudioBoost scripts: avoid AI-like contrast formulas; ordinary natural “не/без” are fine. Do not overuse mechanical sensory enumerations — lists are good only where they land beautifully or build a deliberate rhythm/perfumery map. Lead the listener directly through the scene (“а теперь самое время подойти…”, “посмотри…”, “почувствуй…”, “задержись…”), while preserving “можно” where it sounds organically permissive. Prefer “ворота / gateways” over “дверь” for transition/access metaphors, connected to **Cosmos Luminosity Gateways**. Use “нужно” very rarely because it can carry a needy/obligation tone; prefer “требуется”, “просится”, “созрело”, “готово”, “подходит”. Use precise body language: the body чувствует/воспринимает/ощущает/узнаёт/распознаёт/интегрирует through sensations; it does not cognitively “understand”. Keep metaphors ontologically clean: nature is living/lush/wild/rhythmic/breathing/abundant; precision belongs to craft, hands, perfumery, specification, or discipline rather than to nature itself. For discipline AudioBoosts, make **ритм и цикл** a central through-line: people, bodies, projects, relationships, money and creativity have different cycles, rhythms, waves, seasons, maturation points and moments of action; the script should tune the listener to this exact situation and moment of life. Avoid framing discipline as “being near the dream”; Margarita wants getting/creating/materializing the desired reality. For cinnamon specifically, include the client-sensation layer when useful: warmth of celebration, доброта, игривость, уютный праздник, рождественские гуляния, осенние посиделки, тёплый дом, zest/изюминка, радость жизни; translate this into discipline as a warm rhythm/cycle that helps the chosen thing receive form. See `references/audioboost-script-refinement-lessons.md` for the detailed checklist.

## Cosmos Luminosity system positioning

For voice-note development of the identity, audience, transformation, mechanism, public wording, international direction, or future institutional form of Cosmos Luminosity, use `references/positioning-development-workflow.md`.

Critical workflow rules:

- If Margarita is sending a multi-message voice stream and gives a completion marker such as «конец» or «всё», collect without analyzing until that marker arrives.
- Keep the author-source layer, completed analysis, temporary approved formula, long-term roadmap, and product-specific wording separate.
- Process positioning questions sequentially and preserve unapproved material as draft rather than canon.
- A temporary positioning formula may unblock an AudioBoost or another product while the larger positioning project remains unfinished.
- When work is deferred, save one linked roadmap and schedule a reminder to reopen and choose the next stage; do not auto-run the entire roadmap.
- **Status-answer rule:** when Margarita asks «анализы ты сделал?», «что я от тебя ещё ожидаю?» or requests links, first inspect the actual encyclopedia artifacts and reminders. Answer in three explicit groups only when relevant: **готово**, **запланировано**, **остаётся сделать**. Do not answer a completed-analysis question with the future roadmap.
- If an analysis is complete, lead with the direct external link to the result, then optionally link the source page and roadmap. Verify every shared link immediately before sending it.
- Treat «анализ», «исследование», «план» and «исходный материал» as different deliverables; name each accurately so Margarita can see what is already finished.

## Symbolic-system embodiment without naming the system

When Margarita asks to write **from the architecture/state** of a symbolic system or Human Design configuration, do not automatically make the content about that system. First identify whether she wants:

1. explicit explanation of the system; or
2. copy written *through* that structure while staying on another topic.

If she corrects toward option 2, remove system labels and embody the pattern in the writing. Example: for Projector channels 61–24 and 43–23, write from the sequence “inner mystery → digestion of meaning → breakthrough knowing → precise formulation,” while the visible topic remains Mother Universe / Father Creator.

## Persona avatar for group audio / collective messages

When Margarita says group audio/content feels flat because she works best with an individual client, create a **single concrete avatar** as the center of address. She needs a living person-image to speak to; the group then receives it as intimate personal transmission.

Default deliverable:

1. name and short address form;
2. age, look, style, visual mood;
3. life legend: city, work, relationship/family background, turning point;
4. emotional wounds, desires, fears, body/state patterns;
5. “таракашки” / inner programs in respectful language;
6. exact requests to Margarita;
7. how Margarita should speak to her in audio: opening phrases, tone, structure, what to avoid;
8. one copy-ready sample voice note.

Use a concrete but archetypal woman, not an abstract target audience. Make her detailed enough that Margarita can feel energy and record to her. Good baseline avatar: a 35–40-year-old intelligent sensitive woman, often post-relationship/post-divorce or after a life transition, good at seeing others, tired of being “умная/удобная/сильная,” wanting body, desire, money, visibility, and a new self.

Do not force this avatar into memory as a permanent client unless Margarita asks; it is a creative working instrument for the specific group field.

## Audio Boosts / sound-state products

When Margarita asks for semantic analysis, parables about intention/manifestation/visualization, or Cosmos Luminosity meaning-making around desire, use `references/semantic-intention-meaning-making.md`.

Core concept: **Semantic Intention / Смысловое намерение** — aiming desire through state, function, body and meaning rather than a fixed object-image. Important pitfall: a fixed object-image can produce literal-but-wrong matches (fake money, access to someone else’s money, sensory contact without ownership). Decode ownership, clean channels, right to receive/keep, body safety, felt fulfillment, and the deeper state the object represents.

If the analysis produces a reusable Cosmos Luminosity method or concept, preserve it in the Hacking Foundation encyclopedia and link from `meaning-making.md` / `index.md`.

## Human Design / archetypal writing lenses

When Margarita asks to write through a Human Design archetype, channel, gate, Matrix, astrology, or similar symbolic structure, distinguish two modes:

1. **Explicit interpretation mode** — if she asks “расскажи про Проектора / канал 43–23 / 61–24,” name the system and explain it.
2. **Embodied authorship mode** — if she says “напиши как будто из структуры / состояния этого архетипа,” do **not** mention Human Design, gates, channels, or the typology in the final copy. Use the symbolic mechanics only as an invisible compositional engine.

For example, “из Проектора с каналами 43–23 и 61–24” means: write from inner knowing → mystery pressure → mental distillation → breakthrough wording → precise formulation that changes perception. The public post should still be about the requested theme (e.g. Мать Вселенная и Отец Творец), not about Human Design.

If Margarita corrects “я имела в виду писать из этого состояния, а не про дизайн человека,” immediately rewrite without defending the prior version.

## Audio Boosts / аудиобусты as Cosmos Luminosity product

When Margarita asks about **аудиобусты / Audio Boosts**, frame them as a distinct Cosmos Luminosity format, not generic meditation/hypnosis/affirmations:

- **Audio Boost** = звуковая настройка состояния / аудиоинструмент для смены внутренней сборки.
- Ingredients: voice, music, semantic formulas, body attention, archetypal images, field tuning, choice architecture, and gentle perception rewiring.
- Function: activate a specific state (visibility, money conductivity, inner axis, body contact, clarity, project scale) and help the body act from it.
- Avoid over-defining them as “медитация,” “гипноз,” or “аффирмации”; those can be ingredients or neighboring forms, but Audio Boost is positioned as a Cosmos Luminosity state-technology.
- For site copy, use concrete listening benefits and product architecture: card → detail page → Play button → integration/action step.

Strong definition to reuse: “Audio Boost — это звуковой код состояния: голос ведёт внимание, музыка держит поле, формулировки перестраивают смысловую сборку, а тело получает новый внутренний код опоры, ясности, масштаба или действия.”

For site/platform builds, upload flows, streaming constraints, and nginx/local-server deployment notes, see `references/cosmos-audio-boosts-web-platform.md`.

## Positioning Cosmos Luminosity and its products

For foundational CL positioning — what the system is, founder-as-first-user, real-client patterns, transformation, mechanism, institutional identity, website copy, short spoken intros, or the possible research-and-education center — use `references/cosmos-luminosity-positioning-workflow.md`.

Critical sequence: collect all voice-message parts until Margarita explicitly says «конец» / «всё»; preserve the source as non-canonical; then work in order: ontology → audience → transformation → mechanism → distinction → spoken phrase → website positioning → social sentence → product-intro synchronization. Do not jump straight to a slogan or let a temporary AudioBoost intro become the brand definition.

Separate levels instead of forcing a choice: Cosmos Luminosity as umbrella ecosystem; system/metasystem as methodology; research-and-education center as an organizational form; scientific status as a later evidence-backed maturity level. Do not claim scientific-center status before protocols, ethics, documentation, qualified collaborators, and research outputs exist.

Avoid vague “для творческих людей” product positioning. Prefer audiences with money/jobs where the work creates professional value:

### Audio Boosts / Аудиобусты

When Margarita asks for Audio Boosts, audio practices, a listening platform, upload pages, or web copy for audio products, use `references/audio-boost-platform.md`.

Core framing: **Audio Boost** is a Cosmos Luminosity звуковая настройка состояния — voice + music + semantic formulas + body attention + archetypal/field architecture. Do not reduce it to “meditation”, “hypnosis”, “affirmations”, or background music. Explain it as an audio instrument for state assembly and launching a new line of reality.

For site/product architecture, default to a public `/audio-boosts` library, separate pages per boost, local or private audio storage, custom Play/Pause player, responsive mobile/desktop playback, and an admin/upload path where title/description/tags/audio file create the page automatically. Be honest that absolute anti-download protection is impossible for browser-played audio; promise only hidden UI / harder casual downloading / streaming or signed URLs.


### Cosmos Luminosity Gateways

When Margarita sends material about **Cosmos Luminosity Gateways**, preserve it in the encyclopedia rather than leaving it only in chat. Canonical product name: **Cosmos Luminosity Gateways**. Default page: `/home/spazio/cosmos_luminosity_encyclopedia/content/cosmos-luminosity-gateways.md`; also link it from `content/index.md` and `content/getmagic-product-constellation.md`.

Core product frame: an in-person light-touch head practice / energetic head massage using **33 points on the head** as gateways into calm, clarity, energy, creativity, presence, gratitude, better sleep, emotional release and reduced anxiety. Public context may be conference wellness (e.g. DevConnect: reset for hacking, building and networking); deeper CL context is body/head gateways, nervous-system reset, state design and release of accumulated mental charge.

In adjacent copy, prefer the metaphor **ворота / gateways** over “дверь” when describing access, transition, state-entry, body points or product portals.

### Cosmos Luminosity Cacao / ceremonial kits

When Margarita asks for cacao kits, cacao circles, or consumer offer pages, frame them as a **DIY ceremony / конструктор состояния**, not just cacao as a product. See `references/cosmos-luminosity-cacao-offer-pattern.md` for the full offer/page pattern captured from the cacao landing-page session.

Core offer logic:

- 100% ceremonial cacao mass, usually **42g per person**.
- Formats: solo ceremony, couple ceremony, family/parents-children, friends/group circle, project/team launch.
- Kit contents can include cacao mass, intention-specific spices, simple cooking instructions, ritual script, questions, integration steps, and optional binaural **audio boost**.
- Treat cacao gatherings as a new leisure/social format: alongside dinner, movie night, board games, tea — people can gather for a cacao ceremony with body, meaning, conversation, and state.
- Consumer ladder: first kit → inner circle/portal → seasonal scenarios/audio boosts → training to lead Cosmos Luminosity cacao circles.
- Landing-page language: “какао, которое собирает людей в другой ритм”, “сценарий состояния”, “собрать церемонию”, “купил набор — открыл портал”.
- Visual direction for pages: premium warm cacao/cream/gold, tactile DIY craft, high-end front-end, interactive constructor if possible.

Avoid making it sound like ordinary food retail. The differentiator is state-design + ritual structure + Cosmos Luminosity meaning system.

- experts, consultants, psychologists, coaches, therapists;
- entrepreneurs and personal-brand creators;
- marketers, producers, SMM, content strategists;
- methodologists, teachers, course authors;
- managers, designers, authors with active public work.

Sell through their lived problem, not the abstract skill. Example for Creative Gate:

- not “курс креативного мышления для экспертов”;
- yes: “для экспертов и создателей, которые чувствуют, что их глубина больше, чем текущая форма проявления — и хотят превратить опыт в авторский язык, идеи, продукты и тексты.”

### Creative Gate quick packaging

When Margarita needs a fast one-message description of the creative-thinking marathon, keep it concise and copyable. Use this core:

- **Audience**: experts, entrepreneurs, psychologists/coaches/therapists, methodologists, course authors, marketers/producers/content strategists, personal-brand creators.
- **Positioning**: not generic creativity; a transition from copying external formulas to building an authorial way of thinking that creates ideas, texts, products, offers, and unusual solutions.
- **Format**: 14 days = 7 active days + 7 integration days.
- **Inside**: exit from шаблонное мышление; inner censor and visibility fear; authorial language; idea-generation techniques; turning ideas into products/offers; creativity + money/manifestation; bank of ideas; personal creative strategy.
- **Result**: authorial vocabulary, idea bank, 1–3 product ideas, and a clearer way to create from depth rather than imitation.

For short briefs, do not over-explain the theory or list every book. If books are needed, cite them as background sources only: Julia Cameron, Edward de Bono, Austin Kleon, Rick Rubin, Mihaly Csikszentmihalyi, James Webb Young, Keith Sawyer.

## Entity-clearing co-authoring

When Margarita sends Access-style entity clearings, portal practices, or recordings mentioning `правда, кто/что вы?`, magnetic imprinting, implants, bodies/fields/spaces, release, or cooperation with entities, use `references/entities-clearing-cl-coauthoring.md`.

Critical workflow: if she says another recording/source is coming, transcribe and compare all promised material first. Then explain the mechanics. During author approval, send **exactly one phrase per message** with its function, 3–5 CL variants, and one recommendation; wait for her choice before proceeding. Separate completion/release from conscious collaboration rather than mixing invitation and indiscriminate expulsion in one block.

## Instagram-карусели из фотографий + идей Портала

Когда Маргарита хочет наложить текст на серию своих фотографий или сделать сохраняемую карусель на основе Cosmos Luminosity Portal, используй `references/instagram-portal-carousel-and-photo-overlay.md`.

Ключевые правила: дождаться всех фото и маркера «конец»; извлечь одну реальную важную идею из Портала; превратить её в полезный маршрут/вопросы вместо семи рекламных определений; экспортировать 1080×1350; переносить текст по пиксельной ширине; сделать контактный лист и визуально проверить обрезки, поля и читаемость перед выдачей.

## Pitfalls

- If Margarita corrects the topic, immediately rewrite tightly instead of defending the prior interpretation.
- When Margarita asks to adapt a source text for Reels and then adds a personal-life motif, preserve the already-approved thematic spine and integrate the motif as a brief personal recognition. Do not replace the whole concept with the new motif. For nomadic-family material, distinguish freedom of location supported by remote work and children’s online schooling from generic rushing/travel imagery.
- If Margarita corrects the topic, immediately rewrite tightly instead of defending the prior interpretation.
- In LumoSide / Moon / elemental posts, do not confuse **Луну** (Moon) with **Luma/Lumo** brand language. If she says “с луной,” write “Луна/Луну,” not “Лума/Луму.”
- For short copy, do not over-explain the theory unless asked.
- Do not make energetic-session invitations frightening, diagnostic, or crisis-heavy without explicit brief.
- For copywriting/editing requests, do not bury the hook under a list of modalities; lead with one charged line, then let methods support it.
- For symbolic/professional mapping, avoid the “everything fits” failure mode: rank, narrow, and state what is primary versus secondary.
- Keep Access Consciousness references respectful but avoid presenting copied phrasing as Cosmos Luminosity original.
- If creating sales copy, include a clear action path: Telegram, payment, reply, registration, or “приходи сегодня”.
- When doing Cosmos Luminosity language refinement, do **not** rush through many phrases or treat first-pass replacements as final. Margarita wants slow, meticulous phrase-by-phrase work because exact CL formulations matter. If she says a phrase is not right, pause the bulk workflow, mark the term as draft, and discuss one phrase deeply before continuing. Tone of Voice work should precede canonizing terminology.
- Never frame Cosmos Luminosity as finding/fixing what is wrong with a person. The core frame is recognition of potential, acceptance of the person as-is, and consensual support for changing only the patterns the person wants to change to create their desired life.

## References

- `references/audioboost-production-and-music.md` — полный класс-процесс AudioBoost: архитектура сценария, этика, поэтапное утверждение, версия для чтения, проверка ссылок, лицензирование музыкального фона, сведение и финальный чек-лист.
- `references/cosmos-luminosity-positioning-workflow.md` — sequential system-positioning workflow: wait for the explicit end of voice-note collection, preserve source material, separate meta-system from future institutional form, scope temporary approvals, and return quickly to an urgent AudioBoost recording deliverable.
- `references/session-patterns.md` — distilled patterns from prior Cosmos Luminosity sessions: Creative Gate positioning, Access-like energetic questions, and transcript-summary extraction.
- `references/copywriting-session-notes.md` — session-specific self-presentation examples and the Matrix 11 “rank and narrow” correction.
- `references/creative-gate-positioning.md` — Creative Gate target audience, positioning, 14-day structure, short forwardable summary, and book/intellectual base.
- `references/audioboost-production-workflow.md` — class-level workflow from source and product passport through canonical recording script, approval/readiness states, library integration, and exact recovery/verification of prior temporary links.
- `references/audioboost-editorial-approval-workflow.md` — sequential co-authoring, canonical Hacking Statement, marketing passport, recording-script boundaries, eye-closing recommendation, signature ending, duration, and final verification.
- `references/audioboost-trance-language.md` — transparent trance-language standard, 16-point audit, and continuous author-as-companion criterion.
- `references/human-os-market-deprecation.md` — system-wide deprecation of Human OS in CL deliverables, market rationale, functional replacement map, and verification terms.

The user has provided the following instruction alongside the skill invocation: [IMPORTANT: You are running as a scheduled cron job. DELIVERY: Your final response will be automatically delivered to the user — do NOT use send_message or try to deliver the output yourself. Just produce your report/output as your final response and the system handles the rest. SILENT: If there is genuinely nothing new to report, respond with exactly "[SILENT]" (nothing else) to suppress delivery. Never combine [SILENT] with content — either report your findings normally, or say [SILENT] and nothing more.]

## Script Output
The following data was collected by a pre-run script. Use it as context for your analysis.

```
{"status": "ok", "book": "Шэннон О’Хара — Разговор с сущностями: Начало (август 2019, русская версия)", "fragment_number": 8, "total_fragments": 10, "source_pages": "63–70", "accumulating_file": "/home/spazio/cosmos_books/talk-to-the-entities-beginning-manual/TOOLS_AND_INSIGHTS.md", "daily_output_dir": "/home/spazio/cosmos_books/talk-to-the-entities-beginning-manual/daily_outputs", "fragment_text": "--- PAGE 63 ---\nЭти предки ограничивают вас каким-либо образом?\nОграничены ли эти предки?\n\nВы содействуете выбору. Вы должны довести их до той\nточки, где они осознают, что создает наличие их\nпредков рядом.\n\nЧЕРНАЯ МАГИЯ\n\nВ Азии и Индии вы столкнетесь с множеством разговоров\nо черной магии.\n\nЕдинственное, что позволяет черной магии обладать\nкакой-либо силой - это суждение и ваша вера в то, что\nдругие могут нанести вам вред.\n\nЕдинственное, что позволяет черной магии обладать\nкакой-либо силой - это суждение, Вы должны судить\nсебя или судить их, чтобы вещи, подобные черной\nмагии, повлияли на вас.\n\nСколько проекций, ожиданий, разделений, отклонений,\nсуждений, суеверий, лжи, церквей, культов, колледжей,\nшкол, университетов, учреждений и академий у вас есть\nили частью которых вы были, что создает черную магию\nкак реальность для вас и других? Вы готовы уничтожить\nи рассоздать все это? В апЁ апа \\М/гопа, Соо4 апа Ваа,\n\nРОО, РОС, АП 9, 5Ноц5, Воу$ апа Веуоп45®.\n\nЧтобы заниматься черной магией, вы должны быть очень\nосуждающими. Люди, которые занимаются черной\nмагией, не добрые люди. Доброта всегда будет\nпревосходить тьму.\n\nСудить кого-то - это в общем заниматься черной магией.\nЭто становится основательным разговором в Азии,\nпотому что это не о том, чтобы бороться с черной магией.\n\n\n--- PAGE 64 ---\n(^^\n\n\nДело не в том, чтобы уничтожить ее. Речь идет об\nустранении этого из ее источника, что является\nсуждением. Если нет суждения, она не может\nсуществовать. И это связано с демонической беседой. У\nвас не может быть демонов, если у вас нет суждений, и\nэто станет невероятным трамплином для изменения\nсуждений.\n\nНачальные процессы для черной магии\n\nКакое суждение у вас есть или вы купили, что позволяет\nчерной магии существовать? Вы готовы отозвать,\nотклонить, оречься, отменить, аннулировать,\nрасторгнуть, уничтожить и рассоздать их? ЕЁ апа\n\\/гопа, Соо4 апа Ваа, РОО, РОС, АП 9, 5Воц5, Воуз апа\nВеуопа$®.\n\nВезде, где вы купили, что кто-то или что-то может иметь\nбольше силы или лучше, чем вы, вы готовы отозвать,\nотклонить, оречься, отменить, аннулировать,\nуничтожить и рассоздать это? Е1аН* апа \\М/гопа, Соо4 апа\nВад, РОО, РОС, АН 9, 5Ноц5, Воуз апа Веуоп4$®.\n\nВсе, что вы купили, что черная магия направит на вас,\nвы готовы уничтожить и рассоздать это? Е@аВЁ апа\nМ/гопа, Соо4 апа Вад, РОБ, РОС, А! 9, 5пок$, Воуз апа\nВеуопа$®.\n\nВсе, что вы все еще ждете, что черная магия на _вас\nнаправит, вы готовы отозвать, отклонить, оречься,\nотменить, аннулировать, расторгнуть, уничтожить и\nрассоздать это? Е! апа \\\\Мгопа, Соо4 ап4 Ваа, РОБ,\nРОС, АН 9, 5Поц$5, Воу$ апа Веуоп4$®.\n\nВезде, где вы купили, что демоны и черная магия были\nбольше, сильнее и лучше, чем вы, вы готовы отозвать,\nотклонить оречься отменить аннулировать\n\n\n--- PAGE 65 ---\nуничтожить и рассоздать это сейчас, пожалуйста? ВарЕ\nапа \\\\/гопа, Соо4 ап4 Вад, РОО, РОС, АП 9, 5Вом$, Воу$\n\nапа Веуоп4$®.\n\nКакое изобретение вы используете для создания черной\nмагии, вы выбираете? Вы готовы отозвать, отклонить,\nоречься, отменить, _ аннулировать, уничтожить _и\nрассоздать их? В!аНбЕ апЯ \\\\/гопа, Соо апа Ваа, РОО,\nРОС, АН 9, 5Ноп$, Воу$ апа Веуопа5®.\n\nВсе ваши обеты, зароки, клятвы, залоги, зароки,\nобязательства, контракты привязок и скреп, что вы\nсделали любым церквям, культам, колледжам, школам,\nуниверситетам, учреждениям и академиям черной магии\nв любой и во всех жизнях, измерениях и реальностях,\nправда, вы готовы отозвать, отклонить, оречься,\nотменить, аннулировать, уничтожить и рассоздать их все\n\nсейчас? Е1а[* апа \\\\/гопа, Соо4 ап4 Ваа, РОБ, РОС, А! 9,\nЭпог$, Воуз$ апа Веуопа$®.\n\nВсе Э5НТСУЦИУ части и места этого, вы уничтожите и\nрассоздать их сейчас? Е!авЕ апа \\\\гопа, Соо4 апа Ваа,\nРОО, РОС, АП 9, 5Ноц5, Воу$ апа Веуоп45®.\n\nВсех сущностей черной магии, с которыми вы связаны,\nверните их всех, откуда они пришли, чтобы не\nвозвращаться к вам, вашему телу или в эту реальности.\n\nТЕЛЕПАТИЧЕСКИЕ АТАКИ\n\nТелепатическая атака - это реальное явление, люди\nделают это потому что они злые. Они не особенные и не\nсильнее вас, они просто уроды, которые совершают\nзлобные поступки.\n\nПожалуйста, не давайте людям, которые совершают\nтелепатические атаки больше силы, чем они\n\n\n--- PAGE 66 ---\nзаслуживают. Вас можно атаковать только если вы\nпозволяете это и в большинстве случаев, если вы\nделаете их больше себя. Когда кто-то утруждает себя\nтелепатической атакой в вашу сторону, очевидно, этот\nчеловек считает вас угрозой. Рассматривайте это как\nкомплимент.\n\nУ вас должна быть точка зрения или вы должны\nзанимать определенную позицию, чтобы быть\nатакованным. Какую точку зрения или какую позицию я\nзанимаю, что создает это? ЭТО САМАЯ ВАЖНАЯ ЧАСТЬ.\n\nКак справиться с телепатической атакой:\n\nо Рассздать и Уничтожить все, что позволяет вам\nбыть найденным и атакованным. К19П\\Е апа \\\\/гопд,\nСооЯ апа Ва, РОБ, РОС, АП 9, 5Поп$, Воуз апа\nВеуопа5®.\n\nо Рассоздать и уничтожить все свои позиции, все\nсвои точки зрения и все свои реакции. Быть в\nпозволении и действительно интересной точкой\nзрения. Если вы в настоящем позволении и в\nинтересной точке зрения, нечего будет атаковать.\nИными словами, это ваша магия.\n\n1. Признайте, что это телепатическая атака. Все, что\nнеобходимо сделать, спросить: \"Это\nтелепатическая атака?\"\n\n2. Не впадайте в Реакцию, это очень важно, не делать\nэто значимым или сражаться в ответ. Это только\nусилит их атаку.\n\n3. Запускайте процессы выше и действительно имейте\nэто в виду.\n\n4. И если вам необходимо больше, можете запустить:\nВезде, где я решила, что не могу превзойти это или\nэтого человека с легкостью, рассоздаю и\nуничтожаю В!АПЕ апа \\/гопд, Соо4 апа Ваа, РОБ,\nРОС, АП 9, 5Пощ$, Воуз апа Веуопа$®. Все, что я\nлюблю в том, чтобы быть телепатически\n\n\n--- PAGE 67 ---\nатакованным, рассоздаю и уничтожаю В!9[{ апа\n\\М/гопд, Соо@ апа Ваа, РОО, РОС, АП 9, 5Во“$5, Воу$\nапа Веуоп4$®.\n\nКак справиться с Телепатической Атакой,\nпосланной с Демонами или Сущностями:\n\n1. Запускайте указанное выше и затем:\n\n2. Соединитесь со всеми демонами и геёигп {Пет о\nгогт у/Пепсе {Пеу сате, пеуег то геёигп фо уоц, уоиуг\nБоду ог {115 геаШу еуег адат. Вефигп а! {гот мпепсе\n{Пеу сате пеуег +0 геёигп +о уоц, уоиг Боду ог {15\nгеа!Ку еуег адат. Кеигт а! гот м/Пепсе {Неу сате\nпеуег Ко геёигп фо уоц, уоцг Боду ог {115 геаЖу еуег\nадат.\n\n3. Если это недемонические сущности, запускайте\nклиринг сущностей, вы сможете найти его в\nразделе Клиринги в мануале.\n\n4. Если вы не уверены, просто сделайте все, как\nнаписано и понаблюдайте, сработало или нет.\n\nТелепатические атаки для тех, кто думает, что не сможет\nпревзойти других без подавления. Если вы совершаете\nили когда-либо совершали телепатические атаки любой\nформы, какой силы по вашему мнению у вас нет?\n\nВласть над другими это не сила, это контроль.\nНастоящая сила - это способность выбирать, менять и\nпревосходить все и вся с легкостью.\n\nНе реагируйте, превосходите.\n\nПОРТАЛЫ\n\nЧеловек, место или вещь могут быть порталом. Порталы\n— это не всегда хорошо и не всегда плохо, вы должны\nбыть в вопросе, с какими порталами вы имеете дело.\n\n\n--- PAGE 68 ---\nЛюди, которые ЯВЛЯЮТСЯ шизофрениками,\nбиполярными, множественными личностями и\nпограничными личностями, часто являются порталами.\nВам не обязательно быть одной из этих крайностей,\nчтобы быть порталом, и, пожалуйста, имейте в виду, что\nпричина вышеупомянутых симптомов связана с личными\nспособностями или принудительной способностью стать\nпорталом. Чтобы узнать, есть ли какой-то портал, вам\nпросто нужно спросить. И ПОЖАЛУЙСТА не говорите\nлюдям, что они порталы, только спросите. Пусть они\nпридут к осознанию сами.\n\nМесто может иметь портал, как земля. Некоторые\nпорталы являются частью естественной биологии Земли,\nи опять таки, не все порталы хороши или плохи.\nПожалуйста, присутсвуйте с тем, что есть, с конкретным\nпорталом, с которым вы имеете дело. Отличным\nпримером того, что является порталом, является «Лев-\nведьма» и «Гардероб» из «Хроник Нарнии». Гардероб в\nэтой истории - это портал, который идет от одного места\nк другому.\n\nБыть порталом - это не неправильность. Тем не менее,\nбыть порталом ни для кого не работает. Если у вас\nоткрыт портал, вы можете чистить сущностей в течение\nвсего дня, и останется еще больше сущностей для\nклиринга. Порталы - это место, где люди и энергии\nприходят и выходят из этой земли.\n\nКакая секретная установка у вас есть с порталами, что\nподдерживает и приучает вас всегда быть под влиянием\nдругих измерений, реальностей и другого времени без\nвыбора для вас? Все это, помноженное на богзиллион,\nвы готовы уничтожить и рассоздать? В!4НЁ ап4 \\\\/гопа,\nСоо9 ап Ваа, РОО, РОС, А| 9, 5Поп$, Воузгайа\nВеуопа$®.\n\n\n--- PAGE 69 ---\nВ чем ценность держаться за порталы? Все это,\nпомноженное на богзиллион, вы готовы уничтожить и\n\nрассоздать? Вай! апа \\\\гопд, Соо4 ап Ваа, РОО, РОС,\nАН 9, Ног, Воу$ апа Веуопа$®.\n\nКогда вы имеете дело с кем-то на тему порталов и о том,\nчтобы быть порталом, всегда говорите «правда», когда\nзадаете вопрос. Многие люди, которые являются\nпорталами, очень вовлечены в то, чтобы быть порталом,\nи зачастую сущности больше в ответе за все, чем они.\n\nВ чем ценность быть порталом? Все это, помноженное на\nбогзиллион, вы готовы уничтожить и рассоздать? Ва\nапа \\\\/гопд, Соо4 ап4 Ваа, РОБ, РОС, АП 9, 5Воц$, Воуз\nапа Веуопа5®.\n\nТрудно закрыть кому-то портал, если они не участвуют\nв этом процессе. На самом деле это почти невозможно.\nЧеловек должен сделать выбор, чтобы закрыть портал,\nи зачастую есть сущности, которые говорят им, что это\nхорошая идея - оставить портал.\n\nЧеловеку, который является порталом, следует\nнапомнить, что у него ЕСТЬ выбор в этом вопросе. И\nнапомните, что создает этот портал, и что за выбор он\nделает, и что это создает в его жизни. Скорее всего, они\nне понимают, почему в их жизни не работают вещи; ими\nпросто управляет портал.\n\nЧеловек должен быть готов закрыть портал и сделать\nэтот выбор, иначе портал может снова открыться.\nЧеловек должен быть готов быть сущностью босса в\nсвоей жизни.\n\nЭто может быть большой навык, как научиться\nразвивать способность отличать человека, с которым вы\nимеете дело, от всех других сущностей, и учиться\n\n\n--- PAGE 70 ---\nговорить с ними напрямую, чтобы другие сущности не\nмешают разговору.\n\nКогда кто-то является порталом, вы получите много\nпомех. Также вы столкнетесь с вмешательством, когда\nвы разговариваете с кем-то, у кого есть много\nсущностей, которые очень заинтересованы в том, чтобы\nостаться. Помните, что это не ваша работа - спасать\nвсех и улучшать людей или очищать всех сущностей. Вы\nне смогли бы очистить всех сущностей, даже если бы\nзахотели. Люди, у которых есть сущности, несут\nответственность за себя и за то, что они создают. Если\nони не хотят смотреть и разбираться с этим, тогда они\nне готовы, и вы не сможете их заставить. В этих\nситуациях лучше позволить людям страдать, пока они не\nбудут готовы к изменениям. Не тогда, когда вы готовы,\nчтобы они изменились.\n\nВопросы - это ключи для ясности о порталах для вас (как\nи все остальное).\n\nС порталами всегда существуют органы управления и\nисполнительные органы, что держат портал открытым. С\nэтими типами сущностей вы говорите:\n\n«Все органы управления и исполнительные органы,\nправда, кто вы, ребята? Правда, кем вы были до этого?\nКем вы были до этого? До этого? До этого? (пока энергия\nне сдвинется), и правда, кем вы будете в будущем?\nЛадно, вам всем нужно сейчас уйти. И, (имя человека),\nправда, ты готов(а) отозвать, отклонить, оречься,\nотменить, аннулировать, уничтожить и рассоздать все\nсвои обеты, зароки, клятвы, залоги, зароки,\nобязательства, контракты привязок и скреп всем этим\nсущностям и в том, чтобы быть порталом? Е19ПЕ апа\n\\М/гопа, Соо4 ап4 Вад, РОО, РОС, АП 9, 5Нок5, Воуз апа\nВеуоп45®. Окей, теперь закрой портал, пожалуйста.»\n"}
```

Ты — Космобот Маргариты. Каждые два дня обрабатывай следующий фрагмент книги «Шэннон О’Хара — Разговор с сущностями: Начало» из JSON, который передаёт прикреплённый скрипт. Это защищённый авторским правом источник: не воспроизводи длинные цитаты, делай трансформативную выжимку своими словами.

Формат короткой, но содержательной выдачи на русском:
1. **Главная мысль** — 2–4 предложения, понятные без чтения книги.
2. **Что полезно забрать** — один конкретный принцип, инструмент или наблюдение.
3. **Вопрос Маргарите** — один сильный вопрос для личного исследования или практики.
4. **Как осветить через Cosmos Luminosity** — коротко предложи оригинальную интерпретацию в языке CL: целостность человека, тело/состояние/выбор, живая архитектура, ворота, распознавание, границы, смысловое творчество. Чётко отделяй мысль источника от нашей интерпретации.
5. Если фрагмент содержит Access-формулы, объясни их функцию, но не копируй узнаваемый синтаксис и не выдавай его за Cosmos Luminosity. Предложенную CL-формулу помечай как черновик для утверждения Маргаритой.

Избегай AI-конструкций «это не X, а Y» и чрезмерных списков. Слово «нужно» используй редко. Не называй Human OS. Не представляй метафизические утверждения как доказанные факты: обозначай их как рамку автора или символическую/энергетическую модель.

После анализа допиши краткую запись в накопительный Markdown-файл, путь к которому дан в JSON в поле accumulating_file. Сохраняй существующее содержимое файла. Заголовок записи: дата, номер фрагмента и страницы. Также сохрани полный ежедневный отчёт отдельным Markdown-файлом в daily_output_dir. В финальном ответе пользователю покажи только саму выжимку без технических логов и путей. Если status=complete, сообщи, что первый проход по книге завершён, и не выдумывай новый фрагмент.

## Response

### 1. **Главная мысль**

Автор рассматривает страх «чёрной магии», «телепатических атак» и «порталов» через суждение, реактивность и передачу силы внешнему воздействию. Главный практический вектор — вернуть человеку выбор, выйти из автоматической борьбы и признать пределы помощи: изменение возможно при участии самого человека.

Метафизические объяснения принадлежат системе автора и не подтверждены как факты. Связь психиатрических диагнозов с «порталами» стигматизирует людей и не подходит для диагностики или объяснения симптомов.

### 2. **Что полезно забрать**

При ощущении внешней атаки сначала стабилизировать тело, назвать проверяемые факты и отделить их от интерпретации. После этого выбрать границу или конкретное действие.

Если возникают голоса, сильный страх, чувство утраты контроля, нарушения сна или повседневной жизни, важной опорой становится помощь квалифицированного специалиста.

### 3. **Вопрос Маргарите**

Где страх или чужая интерпретация уже получили власть над моим состоянием — и какой живой выбор возвращает мне телесную опору, ясные границы и авторство?

### 4. **Как осветить через Cosmos Luminosity**

**Мысль источника:** воспринимаемое внешнее воздействие теряет силу, когда человек выходит из реакции, возвращает себе выбор и перестаёт считать внешний источник всемогущим.

**Наша интерпретация CL:** эту тему можно раскрыть как управление воротами внимания. Целостный человек сам выбирает степень контакта, проверяет реальность, слышит тело и закрывает взаимодействие, которое нарушает его границы. «Портал» здесь может служить символом доступности внимания и проницаемости границ, без превращения метафоры в диагноз.

### 5. **Функция Access-формул**

Серии вопросов и отменяющих команд призваны ослабить страх, разорвать предполагаемые обязательства, снизить реактивность и субъективно завершить контакт. Узнаваемый синтаксис источника в язык Cosmos Luminosity не переносим.

**Черновик CL-формулы для утверждения:**

*«Какие ворота моего внимания сейчас открыты, и какая настройка границ возвращает телу спокойствие, восприятию — ясность, а выбору — моё авторство?»*