Dream Studio

Dream Studio (Memory Replay and Self-Update)

In the film, the dream studio spends the night re-cutting the day's footage and staging it. memOrb's dream studio does the same job: replay the orbs a stretch of time has accumulated, see which themes keep coming back, and decide whether to let them settle into core memories and beliefs.

This is the sole executor of step 5 of the distillation pipeline, Evaluate. Other skills record, query, and retire; only this one touches memorbs/HQ/Core/, memorbs/HQ/Belief/, and the current-state narrative on an Island.

Iron rule: stages 1-3 are analysis and discussion only. Write nothing to any Core, Belief, or Island file until the user has confirmed it item by item. Rewriting a person's sense of who they are is not something you do automatically.

How often to run

Monthly. Do not run it daily — the value of the dream comes from looking back after time has passed, and running it too often mistakes an ordinary day for a formative experience. Each run rotates the Memory Commit Journal (see stage 5), so the current journal is the natural index for the unreviewed period.

Order of operations

Stage 1: Set the replay window (talk only)

1. Treat memorbs/log.md as the journal index for the unreviewed period, not the replay's evidence. Its header establishes the period boundary; for a longer review, include the archived journals the user names.
2. Read the file header to confirm the start date and check it with the user. For a longer window, also pull the back issues in memorbs/log/{YYYY-MM}.md.
3. The user may want to dream about one particular Island or one particular event; narrowing the scope is allowed.

Stage 2: Replay (gathering the footage)

Daily Notes/ is the user's own folder and core does not depend on it. Read it as supplementary material if it exists, skip it if it does not — the replay does not fail either way.

The journal helps select what to read; it never authorizes an identity, Core, Belief, or Island update by itself. Before proposing any update, inspect the linked source pages and preserve the item-by-item confirmation gate below.

Stage 3: Find the resonance (analysis only, no writes)

Work through the selected source material and produce a candidate list. Every judgement must be evidenced by linked source orbs/pages, not by a journal title, note, or signal alone.

Core orb candidates — all of the following:

1. A single concrete event, with a time and a setting you can name (not a diffuse state like "busy month")
2. Clear emotional intensity at the time
3. Behaviour changed afterwards — this is the decisive one. An intense event that changed no behaviour is emotion, not a formative experience
4. It points at at least one existing Island. If it points at none, ask the user whether an Island is missing (hand off to island-reclamation) rather than forcing it somewhere

Belief orb candidates — all of the following:

1. It can be written as one first-person sentence ("when I don't have enough information, I'd rather act and correct course")
2. It is supported by two or more independent source orbs, and those sources need not be Core — most beliefs accumulate out of small things that would never qualify as Core individually
3. It is not a label applied by an external instrument (MBTI, star signs, test results all belong in identity.md)

Signals that an existing Belief needs revising:

Signals that an Island's current state is stale: the current-state section of its MOC does not match what actually happened during the period (the main focus has moved on, the goal has been reached or abandoned).

Stage 4: Dream report plus item-by-item confirmation (Gate, mandatory)

Present the report in conversation. Every item is confirmed separately — never bundled into a single "shall I do all of the above?":

## 🌙 夢境報告：{起始日} – {結束日}

### 反覆出現的主題
1. {主題}（出現於 {n} 處：{來源清單}）

### 提議新增 Core orb
- **{標題}** ｜ {YYYY-MM-DD} ｜ 指向 [[memorbs/Islands/{名稱}/000-MOC]]
  - 事件：
  - 事後的行為改變：
  - 為什麼夠格：

### 提議新增／修訂 Belief orb
- **新增：{一句話陳述}**
  - 來源：[[...]]、[[...]]
- **修訂：{既有 orb}** — 現行「{舊}」→ 建議「{新}」，理由：

### 建議更新的 Island 現況
- [[memorbs/Islands/{名稱}/000-MOC]]：{哪一段過時了、建議怎麼改}

The user may accept items one at a time, reword them, or reject everything. A sentence the user wrote always beats one you drafted — the belief is theirs, not yours.

Stage 5: Write (confirmed items only)

1. Core orb: memorbs/HQ/Core/{YYYY-MM-DD}-{slug}.md, frontmatter per memorb-conventions (orb_type: core, no derived_from). The body records the event itself and the change in behaviour. Do not wax lyrical.
2. Belief orb: memorbs/HQ/Belief/{slug}.md, orb_type: belief, with derived_from listing full-path links to every source orb.
3. Revising an existing Belief: leave formed_at untouched and add an evolution note to the body stating the date, what changed, and on what evidence.
4. Retiring a belief: never delete it. Mark the body 狀態：已被 [[新 orb]] 取代 first, and only after the user agrees hand it to memorb-forgetter to move into memorbs/Dump/. The reason for retirement must be written on the Dump page.
5. Island current state: edit only the current-state section of 000-MOC.md; leave the rest of the page alone.
6. Confirm every new orb is linked from somewhere: a Core orb needs an Island that links back to it, a Belief orb needs its derived_from sources. There is no index file; reachability rests entirely on links.
7. Rotate the Memory Commit Journal (the dream studio's exclusive duty — no other skill may do this):

   mkdir -p "$VAULT/memorbs/log"
   mv "$VAULT/memorbs/log.md" "$VAULT/memorbs/log/{起始月 YYYY-MM}.md"
   

   Then create a fresh memorbs/log.md with its journal header and a concise dream entry that links to the confirmed source pages and the archived journal:

   # Memory Commit Journal — since {YYYY-MM-DD}
   
   ## [YYYY-MM-DD HH:MM] dream | 重播 {起始日}–{結束日}
   - 影響頁面：[[...]]、[[memorbs/log/{YYYY-MM}]]
   - 操作註記：已完成已確認項目並封存上期 journal。
   

   Past issues are always kept, never deleted.

Stage 6: Verify

• Every new Belief's derived_from links resolve to real files (check with grep)
• Every new Core orb has an Island linking back to it
• memorbs/log/{YYYY-MM}.md exists and is complete, and the new log.md has been created
• Report the list of paths actually written back to the user

Red Flags