loom-write

Loom Write

Write from research, then settle knowledge. Pipeline: draft → topic → index.

Read First

• ../shared/references/schemas.md

Stage 1 — Draft

Write article prose from a Synthesis Pack (or reviewed Daily Notes if user explicitly wants a lighter workflow).

Writing flow — 5-step critical writing

1. State the viewpoint: put the core viewpoint on the table explicitly.
2. First cut — counter-question/deeper inquiry/flip: first cut — challenge with counter-question, deeper inquiry, or perspective flip.
3. Second cut: second cut pushes further into the tension.
4. Cut to the bottom: cut to the bottom — reach the irreducible position.
5. Synthesize: synthesize into 1000-1500 word output with the user's voice.

Output formatting

• Detect article type and apply appropriate structure.
• Consistent heading hierarchy (H1 title, H2 sections, H3 subsections).
• Proper markdown: links, emphasis, blockquotes for cited material.
• YAML frontmatter with metadata.

Draft rules

• Draft may polish, reorganize, and strengthen the user's voice.
• Draft must NOT overwrite Raw Capture, Daily Note, Source Brief, Synthesis Pack, or Topic Note.
• Draft content must be derivable from the Synthesis Pack.
• Default destination: 01_Daily_Notes/YYYY/working/.
• Do not move to published/ unless user explicitly confirms.
• Preserve high-risk claim markers until verified or consciously accepted.

Quality check — 9 red lines

Apply as final pass on the draft:

1. Speaking test: if you can't say it aloud naturally, rewrite.
2. Zero jargon: no unexplained jargon.
3. Short words first: prefer short words.
4. One sentence, one thing: one idea per sentence.
5. Concrete first: concrete over abstract.
6. Reason first: give reason before conclusion.
7. No filler: no filler phrases.
8. Trust the reader: trust the reader's intelligence.
9. Honesty: be honest about uncertainty.

Stage 2 — Topic Note

Convert trusted research into durable knowledge.

Input priority

1. Synthesis Pack.
2. reviewed Daily Notes.
3. Final or Published Article.

Topic creation flow

Structural decomposition:

• Identify the irreducible generators of the topic.
• Map how they combine to produce observed phenomena.
• Draw ASCII structural diagram.

Depth layers:

• Layer: surface facts → mechanisms → principles → axioms.
• Mark where knowledge is solid vs. uncertain.

Output

• Synthesis Topic Note in 02_Topic_Notes/<Category>/.
• Category directories use Pascal_Case.
• Filename: YYYY-MM-DD_Title-With-Words.md.
• When updating, increment minor version (1.0.0 → 1.1.0).

Topic rules

• Use calm knowledge-base voice. Not article rhetoric or platform tone.
• Focus on structure, mechanisms, applicability, boundaries, related work, reusable insights.
• Do not default to unreviewed Draft input. If user insists, mark source confidence explicitly.
• Preserve link-only Topic Notes unless user requests synthesis.

Stage 3 — Index

Update vault indexes after Topic Note creation or changes.

Index files

• 00_Index/TOPIC_INDEX.md — match rows by exact title, update in place, append new.
• 00_Index/TIMELINE_INDEX.md — months newest first, all three sections per month (New Topics, Updated Topics, Archived), newest first within sections.

Index scripts

# Dry run (default)
python3 ../shared/scripts/build_indexes.py <vault-root>

# Write when explicitly requested
python3 ../shared/scripts/build_indexes.py <vault-root> --write

Index rules

• Prefer dry-run before writing.
• Do not generate new knowledge insights during indexing.
• Do not run connection analysis here — that belongs to loom-maintain.

Full Pipeline Rules

• Draft/Final must not overwrite any upstream artifact.
• Topic Notes remove article rhetoric and return to knowledge-base voice.
• Index updates happen after Topic Note creation, not before.