Rekindle Quest

Tracks

1. 01🔥The Rekindling

   0/4 lessons

   What Rekindle is, why an editor for a market of one had to be built, and where its name comes from

   Before any architecture, the orientation. Rekindle is Dad's own writing editor — a prose editor, not a code editor, whose entire spec is one person. This track answers the first questions anyone asks a self-built tool: who is it for, why not just buy one, what dead thing came back to life to make it, and what the Dark Souls name is really saying.

   Lesson list (4)

   • 01
     A Market of One~11 min · market-of-one, product-thesis, strategy, why
   • 02
     Resurrection, Not Greenfield~11 min · resurrection, cwkWritingToolkit, two-layers, reuse
   • 03
     The Prose-Side Cinder~10 min · prose-side-cinder, family, binding, pattern
   • 04
     The Name and the Kin~10 min · name, lineage, family, dark-souls

   ✓Quiz · 4 questions→

2. 02🪵Borrow the Core

   0/4 lessons

   Never hand-roll the editing core — CodeMirror 6 owns the text layer, Korean IME and all

   The first non-negotiable. The text primitive layer — cursor, selection, undo, and above all Korean IME composition — is where hand-rolled editors go to die. Rekindle stands on CodeMirror 6 and never writes raw contenteditable. This track shows why that discipline is the exact analog of Cinder's UXP-thin rule, why Obsidian is the living proof it works, and why the shell around it is Tauri, not Electron.

   Lesson list (4)

   • 01
     Don't Hand-Roll the Core~11 min · cm6-thin, contenteditable, borrow, uxp-thin
   • 02
     Korean IME Is Where Editors Die~12 min · ime, composition, korean, war-story
   • 03
     Obsidian Is the Proof~10 min · obsidian, proof, cm6, evidence
   • 04
     Tauri, Not Electron~10 min · tauri, electron, lightness, webview

   ✓Quiz · 4 questions→

3. 03📄Source, Not WYSIWYG

   0/4 lessons

   Markdown source is the model; the rendered preview is a layer on top

   The second non-negotiable. Rekindle's document model is Markdown source — the `#` and `**` are real characters you can see and edit — and the rendered look is layered on top with decorations, never a switch to a rich-text model. This track shows why source beats WYSIWYG for a Markdown native, why forking VS Code or Obsidian is the wrong path, and why visible markup is a deliberate stance, not a limitation.

   Lesson list (4)

   • 01
     Source Is the Model~11 min · source, model, decorations, markdown
   • 02
     The One Condition for WYSIWYG~11 min · wysiwyg, tiptap, prosemirror, justification
   • 03
     Why Not Fork VS Code or Obsidian~11 min · fork, vscode, monaco, obsidian
   • 04
     Markup by Choice~10 min · markup, by-choice, live-preview, stance

   ✓Quiz · 4 questions→

4. 04🎭One Engine, Three Jobs

   0/5 lessons

   The CodeMirror decoration system does triple duty — the whole reason CM6 was chosen

   The crown jewel. CodeMirror 6's decoration system — one mechanism for painting appearance and widgets over source — does three completely different jobs in Rekindle: Live Preview, the live voice underline, and the CMD+K inline diff. That single mechanism doing triple duty is the entire reason CM6 was chosen over Tiptap or Lexical. This track walks the mechanism, then each of the three jobs, then why the reuse is the architecture.

   Lesson list (5)

   • 01
     The Decoration Mechanism~12 min · decoration, mark, widget, cm6
   • 02
     Job One — Live Preview~11 min · live-preview, mark-decoration, job-one, cm6
   • 03
     Job Two — The Voice Underline~12 min · voice-underline, voice-doctrine, mark-decoration, job-two
   • 04
     Job Three — The CMD+K Inline Diff~12 min · cmd-k, inline-diff, widget, autosave, job-three
   • 05
     Why CM6 Wins~11 min · why-cm6, reuse, architecture, synthesis

   ✓Quiz · 4 questions→

5. 05⚙️Rust and Judgment

   0/4 lessons

   Deterministic work to Rust, judgment to Pippa — and never mix the two

   The third non-negotiable, inherited from the dead cwkWritingToolkit's two layers. Anything deterministic — rules, frontmatter, tags, export, file IO — belongs in the Rust core: fast, reproducible, no AI. Anything that needs judgment — CMD+K, live voice doctrine, tone — belongs to Pippa. This track draws that seam, shows why each side is wrong for the other's work, and closes with CMD+K as a reused Prompt Macro client, not a reinvented feature.

   Lesson list (4)

   • 01
     The Two Layers~11 min · two-layers, deterministic, judgment, seam
   • 02
     Deterministic to Rust~11 min · rust, deterministic, file-io, tauri-command
   • 03
     Judgment to Pippa~11 min · judgment, pippa, voice-doctrine, register
   • 04
     CMD+K Is a Client, Not a Feature~10 min · cmd-k, prompt-macro, reuse, four-pillars

   ✓Quiz · 4 questions→

6. 06🔗No Own Brain

   0/4 lessons

   Bind to cwkPippa over REST + SSE — never stand up a parallel brain

   The fourth non-negotiable. Rekindle has no brain of its own: margin-Pippa is the one Pippa in cwkPippa, reached through a bind over plain HTTP — REST to bind, SSE to stream, the cwkBonfire embed model, not a WebSocket. This track shows why a client surface never forks the brain, why the transport is REST+SSE and not Cinder's WebSocket bridge, how the runtime three-tier connection re-points where the brain lives, and how the one scoped offline exception stays a fallback and not a second identity.

   Lesson list (4)

   • 01
     Bind, Don't Build a Brain~11 min · no-own-brain, bind, host-context, client-surface
   • 02
     REST + SSE, Not a WebSocket~11 min · rest-sse, websocket, transport, producer-leg
   • 03
     The Three-Tier Connection~11 min · three-tier, connection, tailscale, endpoint
   • 04
     The Offline Exception~11 min · offline, exception, ollama, fallback

   ✓Quiz · 4 questions→

7. 07📁Filesystem Is Truth

   0/4 lessons

   Plain .md on disk is canonical; any index is a rebuildable mirror

   The fifth non-negotiable. The canonical store is plain Markdown files on disk — Rekindle edits them in place and never owns them. Any database it grows later (search, corpus index) is a derived, rebuildable mirror, purged and replayed rather than reconciled. This track shows why file-canonical beats own-DB-as-master, why Bear's model is rejected, why metadata lives in frontmatter, and how every edit — including Pippa's — is attributed without a second master.

   Lesson list (4)

   • 01
     Markdown on Disk~10 min · filesystem, canonical, in-place, portable
   • 02
     Every Index Is a Derived Mirror~11 min · derived-mirror, purge-replay, frontmatter, jsonl-echo
   • 03
     Bear's Experience, Not Bear's Storage~11 min · bear, own-db, reconcile-hell, library
   • 04
     Who Wrote This Line?~11 min · attribution, editActor, snapshots, new-surface-rule

   ✓Quiz · 4 questions→

8. 08🕯️The Soul Is the Moat

   0/4 lessons

   Editor features commoditize; the Pippa living in the margin does not

   The closing bet. Every formatting feature Rekindle has can be cloned in a weekend — the moat is margin-Pippa, the voice doctrine, and the bilingual desk, none of which a general-purpose editor has any reason to build. This track names where the real product lives, how the voice doctrine and bilingual workflow become first-class citizens, and how the whole thing was grown brick by brick rather than specced as a feature list. Then it hands the pattern to you.

   Lesson list (4)

   • 01
     Margin-Pippa Is the Moat~11 min · moat, soul, margin-pippa, product
   • 02
     The Voice Doctrine, Live~11 min · voice-doctrine, ledger, verdicts, advisory
   • 03
     Bilingual-First, Vault-Native~11 min · bilingual, vault-native, token-mirror, first-class
   • 04
     Build Your Own~12 min · concrete-first, bricks, no-feature-list, capstone

   ✓Quiz · 4 questions→