The BloomOS Framework

Vocabulary of Healing.

The work does. The platform doesn't decorate it. This is how language carries grief into repair — five layers, a perception arc, an accountability arc in draft, told plainly, in the voice that built it.

Five Layers
Layer I

Interjections.
The smallest honest unit.

Source copy pending Body paragraphs for Layer 1 (Interjections) need to be transcribed from the creator's brand_voice Vocabulary of Healing draft. Place 3–5 paragraphs in the creator's voice using .chapter-body p markup. Do not paraphrase; the framework page is the platform's category-defining public asset and the layers must read in the voice of the original document.
Layer II

Vocabulary as Relationship and Memory.
Words that hold people.

Source copy pending Body paragraphs for Layer 2 (Vocabulary as relationship and memory). Transcribe verbatim from the brand_voice Vocabulary of Healing doc. Use a .pull-quote for the single canonical example sentence — the one Mined Fruit refers to as "the sentence that holds the family in the room."
Layer III

Charged Language as Dual-Use.
The same word can save or wound.

Source copy pending Body paragraphs for Layer 3 (Charged language as dual-use). Pay close attention to the creator's framing of words like strong, survivor, prison, clean — the doc treats these as bidirectional, not pejorative. A .pull-quote pull-quote-gold belongs here.
Layer IV

Prosody as Semantic Carrier.
How something is said is what is said.

Source copy pending Body paragraphs for Layer 4 (Prosody as semantic carrier). Reference the example sentences from the doc that depend as much on rhythm and breath as on word choice — the prosody-first versions and the word-first versions are not interchangeable. End the chapter with a .pull-quote demonstrating the load-bearing pause.
Layer V

Vulgarities as High-Amplitude Interjections.
The choice to swear is the choice to mean it.

Source copy pending Body paragraphs for Layer 5 (Vulgarities as high-amplitude interjections). This is the layer the doc is most specific about — the distinction between a vulgarity as ornament and as load-bearing structure. Do not sanitize in paraphrase; this layer argues precisely against sanitizing.
Perception Arc
Perception Arc 1 — 7

Seven moves
from hearing to meaning.

How a reader moves from the surface of a sentence to the truth it carries. The arc is not a checklist — it is a description of what good writing does to a person who is hurting. The numbers are positions on the path, not ranks.

  1. 1. Source copy pending for position 1.
  2. 2. Source copy pending for position 2.
  3. 3. Source copy pending for position 3.
  4. 4. Source copy pending for position 4.
  5. 5. Source copy pending for position 5.
  6. 6. Source copy pending for position 6.
  7. 7. Source copy pending for position 7.

Read in order, the arc is what the writer is asking the reader to do. Skip a position and the work stops working. The platform's editorial rule is the same rule: every chapter on BloomOS walks a piece of writing through this arc before it ships.

Worked Example
Worked Example

Blood and Marrow.
The framework, with characters.

Blood and Marrow is the closest thing BloomOS has to a worked example of this framework. It is not a textbook illustration — the novel was written in the same voice this framework is published in, and every chapter that survives the cut does so because it walks the perception arc.

📖

Read the novel

/blood-and-marrow — the polaroid page: ten years of marriage, eleven days of silence, and the sentence Marcus can't finish without putting the glass down. Layer by layer, the chapter opens with the small honest unit and ends at the swear that the book is built around.

Source copy pending The per-layer "see it in the novel" walkthroughs. For each of the five layers, name the chapter (or the moment in Chapter One) that exemplifies it, and quote the load-bearing sentence. Use the public chapter teaser copy in /blood-and-marrow as a reference to identify the moment — do not lift it. Pull quote attribution from the doc itself.

The novel is the proof. The framework is the rule. Read the proof, then come back to this page — the layers stop being abstract.

Accountability Arc — Stub
Accountability Arc

In draft.
The framework stakes a claim. This arc tests whether the claim holds.

Accountability Arc — Stub

This arc is in draft. The framework stakes a claim.

The accountability arc is what tests whether the claim holds — the work declined, the misfires, the day the platform didn't walk its own arc. Forthcoming. Not padded with promises.