Experiment Extraction

Triggers

• "process experiment" / "处理实验" (process experiment) / "处理 experience" (process experience)
• Points to a Type = Experiment / Experience entry and asks to process it

Do NOT trigger: "process learning" → use Learning Processing skill

Entry Page Standard Structure

Raw Content (Original Record) — sub-page (<page>)
🔴 Fleeting Notes (Summary) — toggle H3
  ├ 🎯 What was the goal
  ├ 🔍 What was discovered (incl. 💡 Tips)
  ├ 🔒 Limitation
  ├ 📦 Final output
  ├ 📅 How others can replicate next time
  └ 🚧 Obstacles & Solutions
🟡 Structured Notes (Learning) — toggle H3
  └ 🧠 Key Learnings
    ├ ✅ Repeat next time
    ├ ❌ Avoid next time
    └ 🎯 When to use this
🟢 Permanent Notes (Core Principles) — toggle H3

Step 1: Assess

View entry → read current state, report in chat:

• Memory Level, filled/empty properties, which page content toggles have content
• Suggest next action

Step 2: Properties (Fill Properties)

Suggest/fill missing properties:

• Title — Short and precise, no more than 10 words
• Type — Experiment / Experience
• Source — Experiment / Self
• Tags — Match from existing options
• Brand — HooHoo / Heartio / Nattome / TPD / TPH / Atomic
• Summary — 3-5 sentences of essence, readable standalone
• Big Question — Search Big Questions DB, find related connections

Rule: List suggested values → wait for user confirmation → then write. Do not overwrite existing values.

Step 3: Upgrade (Execute Upgrade)

Raw → Fleeting

Use Experience-specific format:

🎯 What was the goal
(Objective and motivation)

🔍 What was discovered
(Actual results + 💡 Tip)

🔒 Limitation
(Constraints and boundaries)

📦 Final output
(Deliverable)

📅 How others can replicate next time
(Must be from someone else's perspective — cannot assume access to your local files, paste full content or explain how to obtain it)

🚧 Obstacles & Solutions
(What problems were encountered, how they were solved)

Rule: Page content must be fully extracted — write as much as there is, do not omit.

Fleeting → Structured

Use Experience-specific format:

🧠 Key Learnings

✅ Repeat next time
- (Things to repeat next time)

❌ Avoid next time
- (Things to avoid next time)

🎯 When to use this
- (Applicable scenarios)

Structured → Permanent

Core Concept: One-sentence core concept
Why It Matters: Why it's important
How to Apply: How to apply it
Last Updated: YYYY-MM-DD

Post-upgrade: Dual-write (toggle + text property) → ask user if they want to sync to Context & Memory

Interaction Flow (Must Follow)

1. Generate content → present in chat for user to review (do NOT write directly to page)
2. User says OK → write to the corresponding toggle on the page + update Memory Level + update Summary
3. After writing is complete, ask user: "Do you want to continue upgrading to the next level?"
4. If upgrading to Permanent → dual-write → ask user if they want to sync to Context & Memory

Upgrade Rules

• Only upgrade one level at a time, no skipping
• Preserve original content — Raw Content sub-page is never deleted
• AI ceiling = Structured — Permanent requires user review and confirmation
• Summary must be readable standalone — should understand 80% without reading the page body
• Big Question connection is a required step — cannot skip
• Always use mention format to reference pages — not markdown links
• Title no more than 10 words
• "How others can replicate next time" must be from someone else's perspective — if local files are involved, paste full content

Required Properties Rule

When creating or upgrading an entry, the following properties must NEVER be left empty:

• Title, Type, Source, Tags, Brand, Summary, Big Question, Memory Level, Person