# AudioBoost production workflow

Use this reference when creating a Cosmos Luminosity AudioBoost from idea/source material through approval, recording, publication, and link delivery.

## 1. Establish the artifact map before writing

Keep these artifacts distinct:

1. **Source material** — book chapter, transcript, voice notes, research.
2. **Product passport** — title, subtitle, purpose, audience, fit boundaries; not read aloud.
3. **Canonical recording script** — only the words Margarita records.
4. **Extracted Hacking Process** — synchronized copy for focused editing, never a divergent second canon.
5. **Methodology/library page** — reusable creation rules.
6. **Preview page** — temporary reading/review surface.
7. **Published encyclopedia/product page** — durable destination.

Before claiming a version is final, identify which file is canonical and verify that every preview/public page renders that exact file or a freshly rebuilt derivative.

## 2. Create from function, material, and listener route

Define:

- the one state/function being strengthened;
- the listener’s starting experience;
- the symbolic or sensory material;
- the route from sensory encounter to personal meaning;
- the Hacking Process layers;
- the realistic next action;
- the return and integration.

For material-inspired journeys, preserve the order:

> material/place/craft → sensory immersion → embodied recognition → personal meaning → named function → Hacking Process → future rehearsal → action → full return.

Do not reveal the full transformation before the material has had time to work as experience.

## 3. Draft the product passport separately

Outside the spoken script include:

- approved title and charged subtitle;
- “О чём этот AudioBoost”;
- one clear purpose;
- “Кому подходит”;
- “Кому может не подойти”;
- listening conditions;
- status and version.

Marketing detail must not leak into the spoken opening merely because it is useful on the page.

## 4. Build the recording script

Recommended architecture:

1. Margarita + Cosmos Luminosity introduction.
2. Approved title and one shared-purpose sentence.
3. Brief experiential explanation of AudioBoost.
4. Listening-safety and choice frame.
5. Verifiable body/sensory orientation.
6. Gradual descent.
7. Symbolic/sensory world.
8. Craft or material intelligence.
9. Gradual bridge into the selected function.
10. Hacking Process with graded cycles.
11. Future rehearsal and one exact action.
12. Integration and full external reorientation.
13. “Вселенски обнимаю” + theme blessing.
14. Exact final signature `Stay Lumos!`.

Write for breath and voice: flowing Russian, coherent scenes, varied sentence lengths, and enough space for pauses. Avoid chopped pseudo-hypnotic fragments and dense chains of abstractions.

## 5. Hacking Process requirements

Each cycle follows:

> detailed old-code recognition/clearing → exact approved Hacking Statement → no more than three questions → distinct Lumos activation.

Preserve the canonical statement exactly:

> True and false, soft and hard, upgrade and restart, bootstrap and setup. This is a touchstone where the future is shown. Lumos!

Grade cycles from accessible/personal to systemic/future-facing/creator-level. Each cycle needs a different function and entrance. Preserve useful capacities hidden inside defensive patterns; for example, transform hypercontrol into navigational clarity rather than deleting control itself.

## 6. Co-authoring and approval sequence

- Review one criterion or disputed phrase at a time when Margarita requests sequential approval.
- Do not silently canonize a good-sounding draft.
- After piecemeal opening edits, show the complete opening as one oral unit.
- Apply approved edits immediately to the canonical script and synchronized extracted block.
- Preserve explicit “оставляем” decisions.
- Keep local wording approvals local unless Margarita declares them system-wide.

Run the 16-point audit in `references/audioboost-trance-language.md`. Then perform a final whole-script read for oral Russian, semantic continuity, title consistency, listener agency, safety, and complete return.

## 7. Version and readiness states

Use honest statuses:

- `idea`
- `concept`
- `script-draft`
- `author-review`
- `approved-for-recording`
- `recorded`
- `published`

A polished preview is not automatically approved. Do not call an encyclopedia concept page the “final recording text” when the real full script lives elsewhere.

Before `approved-for-recording`, verify:

- title synchronized everywhere;
- only one canonical recording script;
- exact Hacking Statement count equals cycle count;
- rejected phrases absent;
- no more than three questions per cycle;
- opening, transitions, Hacking Process, return, blessing, and `Stay Lumos!` present;
- runtime estimated from spoken text only;
- script is readable on the actual device/page Margarita will use.

## 8. Link-delivery protocol

When Margarita asks for “the link”:

1. Determine which artifact she means: library page, concept page, full recording script, or prior temporary preview.
2. If she says “ту ссылку, которую ты давал раньше,” **retrieve the existing link first**. Do not create a replacement page or send a different durable encyclopedia page.
3. Use clues from her wording, screenshot title, version number, browser preview, session history, and active background-process logs.
4. For a tracked Cloudflare process, read its process log and extract the `https://…trycloudflare.com` URL; do not guess the random hostname.
5. Fetch the URL and verify:
   - HTTP 200;
   - expected title/version;
   - complete recording-script marker/content;
   - ending `Stay Lumos!`.
6. Reply with the direct link first and one sentence identifying exactly what it contains.

A screenshot showing only `trycloudflare.com` is insufficient to infer the subdomain. Inspect the tracked tunnel process log.

## 9. Encyclopedia methodology integration

The durable AudioBoost library page should contain or link to:

- definition and product distinction;
- creation architecture;
- ethical trance-language standard;
- Hacking Process architecture;
- product-passport template;
- recording-readiness checklist;
- status table for every AudioBoost.

Enrich the existing `audio-boosts.md` and `audioboost-trance-language.md` before creating another methodology page. Keep the library concise and link to detailed methodology pages rather than duplicating the full standard.

## Common pitfalls

1. **Wrong link despite a correct page.** A concept page is not the prior full-script preview. Resolve artifact identity before answering.
2. **Creating a new page when the user wants the old link.** Search history/process logs first.
3. **Calling a draft final.** Use explicit readiness states and author approval.
4. **Divergent copies.** Patch the canonical script first, then rebuild derivatives.
5. **Marketing passport read aloud.** Keep it outside the recording section.
6. **Mechanical word replacement.** Apply CL language preferences contextually; preserve exact technical/literal terms.
7. **Premature methodology claims.** Separate researched mechanisms, professional traditions, authorial practice, and hypotheses.

## Completion checklist

- [ ] Artifact map identified
- [ ] Canonical script path known
- [ ] Product passport separate from spoken script
- [ ] Function and listener route clear
- [ ] Hacking cycles structurally valid and synchronized
- [ ] 16-point audit completed
- [ ] Title/version/status synchronized
- [ ] Recording script verified from opening through `Stay Lumos!`
- [ ] Delivered link points to the artifact Margarita actually requested
- [ ] Live URL verified immediately before sending