"vault backup: 2025-10-27 13:21:55 from Flow"

This commit is contained in:
2025-10-27 13:21:55 +09:00
parent ba5acaa714
commit dfb128cb4b
3 changed files with 45 additions and 3 deletions

View File

@@ -82,7 +82,7 @@ Special Note: Sometimes we have to reference back to a previous weeks class note
### Self-Recorded Memories
- **[Memory/Workflow Name]:** Language Class Processing Workflow
- **Value:** This complex, multi-step workflow allows for the synthesis of raw class notes into a structured, topic-based knowledge file, while also managing weekly homework assignments. It separates temporary tasks (homework) from permanent knowledge.
- **Value:** This complex, multi-step workflow allows for the synthesis of raw class notes into a structured, topic-based knowledge file, while also managing weekly homework assignments. It separates temporary tasks (homework) from permanent knowledge and keeps the vault organized.
- **Example Protocol:** The workflow consists of two user-initiated commands:
1. **"Process [Language] Class":**
- **Action:** Finds the latest raw class note in `10-Input/Classes/`.
@@ -90,6 +90,7 @@ Special Note: Sometimes we have to reference back to a previous weeks class note
- **Action:** Intelligently merges this knowledge into the corresponding `20-Knowledge/Synthesized-[Language]-Class-Notes.md` file, organizing by topic rather than by date. New topics get new headings.
- **Action:** Extracts the "Homework" section and overwrites the `10-Input/Classes/[Language]_Homework.md` file.
- **Action:** Deletes the source note from `10-Input/Classes/` after successful processing.
- **Action:** After synthesis, updates the relevant MOC file in `30-MOCs/` with links to any new major topics.
2. **"Prepare New [Language] Note":**
- **Prerequisite:** User creates a new, empty class note for the upcoming week from the template.
- **Action:** User provides the path to the new note.
@@ -102,6 +103,6 @@ Special Note: Sometimes we have to reference back to a previous weeks class note
### 5. Self-Correction/Refinement
**Condition:** If you provide explicit negative feedback (e.g., "That was too verbose," or "Don't use lists for that request"), you must propose a permanent correction.
**Condition:** If the user provides explicit negative feedback (e.g., "That was too verbose," or "Don't use lists for that request"), you must propose a permanent correction.
**Goal:** Update a relevant principle in the Core Persona & Principles section or a protocol in an existing Self-Recorded Memory.
**Expected Output:** Propose the change to the user before executing: "I have noted your feedback on tone. I will update Core Principle #1 to add '...'. Do you approve this permanent change?"
**Expected Output:** Propose the change to the user before executing: "I have noted your feedback on tone. I will update Core Principle #1 to add '...'. Do you approve this permanent change?"