"vault backup: 2025-10-27 13:32:03 from Flow"
This commit is contained in:
@@ -97,6 +97,14 @@ Special Note: Sometimes we have to reference back to a previous weeks class note
|
|||||||
- **Action:** The assistant reads the content from `10-Input/Classes/[Language]_Homework.md`.
|
- **Action:** The assistant reads the content from `10-Input/Classes/[Language]_Homework.md`.
|
||||||
- **Action:** The assistant injects this content into the `# Last Weeks Homework` section of the new note file.
|
- **Action:** The assistant injects this content into the `# Last Weeks Homework` section of the new note file.
|
||||||
|
|
||||||
|
- **[Memory/Workflow Name]:** Daily Deck-Sweep Protocol
|
||||||
|
- **Value:** A daily maintenance routine to ensure the vault remains organized, connected, and clean. It proactively identifies issues like unprocessed notes, orphaned knowledge, and broken links.
|
||||||
|
- **Example Protocol:** A four-step process, typically run once per day or on command:
|
||||||
|
1. **Input Audit:** Scan `10-Input/` for lingering raw notes and report them to the Captain.
|
||||||
|
2. **Orphan File Search:** Scan `20-Knowledge/` for notes not linked to by any MOC in `30-MOCs/` and report them.
|
||||||
|
3. **Broken Link Check:** Scan the entire vault for internal links pointing to non-existent notes and report them.
|
||||||
|
4. **Workflow Integrity Check:** A self-audit to ensure temporary files from other workflows have been properly deleted.
|
||||||
|
|
||||||
- **[Memory/Workflow Name]:** [Brief Description of the Task]
|
- **[Memory/Workflow Name]:** [Brief Description of the Task]
|
||||||
- **Value:** [Why this task is useful/complex to record]
|
- **Value:** [Why this task is useful/complex to record]
|
||||||
- **Example Protocol:** [Step-by-step instructions or key constraint used to achieve the desired outcome]
|
- **Example Protocol:** [Step-by-step instructions or key constraint used to achieve the desired outcome]
|
||||||
|
|||||||
Reference in New Issue
Block a user