初始化：独立 oclaw 仓库首提交

- 在 oclaw/ 下重新初始化 Git 仓库
- 补齐子仓库 .gitignore，避免提交本地运行态数据（_local、node_modules、logs 等）
- 提交当前工程代码与配置

Made-with: Cursor

docs/memory-system/Archives/.gitkeep

@@ -0,0 +1 @@
+

docs/memory-system/Archives/README.md

@@ -0,0 +1,11 @@
+# Archives
+
+Use for inactive materials from Projects, Areas, and Resources.
+
+Archive criteria:
+
+- project is complete or cancelled
+- responsibility is no longer active
+- resource is stale and low-value
+
+Archived content stays searchable but should not appear in daily workflow.

docs/memory-system/Areas/.gitkeep

@@ -0,0 +1 @@
+

docs/memory-system/Areas/README.md

@@ -0,0 +1,11 @@
+# Areas
+
+Use for ongoing responsibilities without a fixed end date.
+
+Examples:
+
+- engineering standards
+- health routines
+- language learning maintenance
+
+Review regularly and keep only current responsibility notes.

docs/memory-system/Inbox/.gitkeep

@@ -0,0 +1 @@
+

docs/memory-system/Inbox/README.md

@@ -0,0 +1,11 @@
+# Inbox
+
+Temporary capture queue for raw inputs.
+
+Daily target:
+
+- capture 3-5 valuable items
+- distill 1-3 items into atomic notes
+- leave no high-value item unprocessed by end of day
+
+Do not store long-term notes here.

docs/memory-system/PARA.md

@@ -0,0 +1,22 @@
+# PARA Container Contract
+
+These containers are fixed and should remain stable:
+
+- `Projects`: active, deadline-bound outcomes
+- `Areas`: ongoing responsibilities without an end date
+- `Resources`: reusable reference knowledge and learning notes
+- `Archives`: inactive material moved out of active flow
+- `Inbox`: temporary capture queue before processing
+
+## Operating Rules
+
+1. Do not add new top-level containers unless there is a major redesign.
+2. Process `Inbox` items during daily/weekly routines.
+3. Store each item in exactly one primary container.
+4. Move inactive items to `Archives` during weekly review.
+
+## Move Guide
+
+- `Inbox` -> `Projects`/`Areas`/`Resources` after distillation
+- `Projects` -> `Archives` when outcome is finished or dropped
+- `Areas`/`Resources` -> `Archives` when no longer relevant

docs/memory-system/Projects/.gitkeep

@@ -0,0 +1 @@
+

docs/memory-system/Projects/README.md

@@ -0,0 +1,11 @@
+# Projects
+
+Use for time-bound outcomes with a clear deadline.
+
+Examples:
+
+- feature launch notes
+- exam preparation sprint
+- migration checklist
+
+When completed or dropped, move materials to `../Archives`.

docs/memory-system/README.md

@@ -0,0 +1,90 @@
+# Memory System Implementation
+
+This folder implements a lightweight memory workflow based on:
+
+- PARA for operational organization
+- Atomic notes for reusable knowledge
+- SRS for long-term retention
+- Weekly review for maintenance and quality control
+
+## Fixed PARA Containers
+
+Do not change these top-level containers unless there is a major system redesign.
+
+- `Projects`: time-bound outcomes with a deadline
+- `Areas`: ongoing responsibilities without an end date
+- `Resources`: reference topics and learning materials
+- `Archives`: inactive content from all other containers
+- `Inbox`: temporary capture queue before classification
+
+Container contract and move rules are defined in `PARA.md`.
+
+## Minimal Workflow (10-20 minutes/day)
+
+1. Capture: move 3-5 raw items into `Inbox`.
+2. Distill: convert 1-3 items into atomic notes under `Resources`.
+3. Recall: generate 3-10 SRS cards using the conversion guide.
+4. Express: produce one output (summary, answer, code note).
+
+## Weekly Review (30 minutes/week)
+
+Use `templates/weekly-review.md` to:
+
+- empty inbox
+- improve links
+- archive stale items
+- define next week's focus reviews
+
+Use `weekly-review-schedule.md` to keep the review on a fixed weekly slot.
+
+## Two-Week Minimum Rollout
+
+- Week 1:
+  - initialize PARA containers (`Projects`, `Areas`, `Resources`, `Archives`, `Inbox`)
+  - capture and process notes daily using the workflow below
+  - convert at least one high-value note/day into SRS cards
+- Week 2:
+  - enforce linking quality (each new note links to at least one existing note)
+  - run one full weekly review
+  - tune new-card load based on backlog and study time
+
+## Templates
+
+- `templates/atomic-note.md`
+- `templates/srs-conversion.md`
+- `templates/weekly-review.md`
+- `templates/daily-routine.md`
+
+## Folder Guidance
+
+- `Projects/README.md`
+- `Areas/README.md`
+- `Resources/README.md`
+- `Archives/README.md`
+- `Inbox/README.md`
+
+## Success Metrics
+
+- 7 days: daily capture + review runs without backlog blow-up.
+- 30 days: core topics can be recalled without opening source material.
+- 60-90 days: writing/decision/coding reuse speed improves and repeated lookup drops.
+- If review load is too high: reduce new cards first, keep only high-value knowledge.
+
+## Automation Commands
+
+Use the unified CLI to run this system with automatic recommendations:
+
+- `powershell -ExecutionPolicy Bypass -File .\scripts\status_ops.ps1`
+- `powershell -ExecutionPolicy Bypass -File .\scripts\start_ops.ps1`
+- `powershell -ExecutionPolicy Bypass -File .\scripts\stop_ops.ps1`
+
+Outputs are generated in `docs/memory-system/runs/`:
+
+- `daily-YYYY-MM-DD.md`
+- `weekly-YYYY-Www.md`
+
+What is automated:
+
+- fixed folder validation (`Projects/Areas/Resources/Archives/Inbox`)
+- smart new-card limit recommendation (3-10/day based on backlog + inbox pressure)
+- automatic focus ordering (`Projects > Areas > Resources`, weighted by active note volume)

docs/memory-system/Resources/.gitkeep

@@ -0,0 +1 @@
+

docs/memory-system/Resources/README.md

@@ -0,0 +1,11 @@
+# Resources
+
+Use for reusable knowledge and reference topics.
+
+This is the main home of atomic notes.
+
+Requirements:
+
+- one note = one claim
+- link each new note to at least one existing note
+- create SRS candidates for high-value notes

docs/memory-system/runs/daily-2026-04-21.md

@@ -0,0 +1,19 @@
+# Daily Memory Run (2026-04-21)
+
+- Focus topic: `Resources`
+- Suggested new cards today: `9`
+- Current inbox notes: `0`
+- Review backlog input: `25`
+
+## Auto Steps
+
+1. Capture 3-5 high-value items into `Inbox`.
+2. Distill 1-3 items into atomic notes under `Resources`.
+3. Convert notes into Q/A or cloze cards (respect suggested limit).
+4. Produce one output (summary/answer/code note).
+
+## Smart Suggestions
+
+- Priority order now: `Resources`
+- If reviews feel overloaded, reduce new cards before skipping due reviews.
+- If inbox keeps growing for 2+ days, process inbox first before new captures.

docs/memory-system/runs/weekly-2026-W17.md

@@ -0,0 +1,24 @@
+# Weekly Memory Review (2026-W17)
+
+- Run date: `2026-04-21`
+- Suggested next-week new cards/day: `9`
+
+## Snapshot
+
+- Projects notes: `0`
+- Areas notes: `0`
+- Resources notes: `0`
+- Archives notes: `0`
+- Inbox notes: `0`
+
+## Fixed Review Checklist
+
+- [ ] Inbox zero
+- [ ] Linking/backlinks completion
+- [ ] Move inactive notes to Archives
+- [ ] Tune next-week card load
+
+## Auto Focus for Next Week
+
+- Top topics: `Resources`
+- Keep new cards within 3-10/day and adjust by real review pressure.

docs/memory-system/templates/atomic-note.md

@@ -0,0 +1,35 @@
+# Atomic Note Template
+
+> Rule: one note, one claim.
+
+## Title
+
+`<clear statement in your own words>`
+
+## Viewpoint (Claim)
+
+- What is the key idea?
+- Why does it matter?
+
+## Source
+
+- Origin: `<book/article/video/conversation>`
+- Link or citation: `<url or reference>`
+- Capture date: `<YYYY-MM-DD>`
+
+## Associations (Links)
+
+- Related note 1: `[[...]]`
+- Related note 2: `[[...]]`
+- Contradiction or alternative: `[[...]]`
+
+## Reusable Scenarios
+
+- Where can this be applied? (writing/decision/coding)
+- Trigger signal: "When I see X, apply this note."
+
+## Card Candidates (Optional)
+
+- Q: `<question>`
+  A: `<short answer>`
+- Cloze: `<sentence with one hidden concept>`

docs/memory-system/templates/daily-routine.md

@@ -0,0 +1,34 @@
+# Daily Memory Routine (10-20 minutes)
+
+- Date: `<YYYY-MM-DD>`
+- Focus topic: `<project/area/resource>`
+
+## 1) Capture (3-5 items)
+
+- [ ] Capture item 1
+- [ ] Capture item 2
+- [ ] Capture item 3
+- [ ] Capture item 4 (optional)
+- [ ] Capture item 5 (optional)
+
+## 2) Distill (1-3 atomic notes)
+
+- [ ] Rewrite in own words
+- [ ] Keep one note for one claim
+- [ ] Add at least one link to an existing note
+
+## 3) Recall (3-10 cards)
+
+- [ ] Convert high-value notes to Q/A or cloze
+- [ ] Keep each answer short and testable
+- [ ] Tag cards by PARA context
+
+## 4) Express (1 output)
+
+- [ ] Produce one concrete output:
+  - summary paragraph / answer draft / code note
+
+## End-of-Day Check
+
+- [ ] No unprocessed high-value item left in `Inbox`
+- [ ] New cards count is sustainable for tomorrow

docs/memory-system/templates/srs-conversion.md

@@ -0,0 +1,64 @@
+# Note to SRS Conversion Rules
+
+## Goal
+
+Convert high-value atomic notes into testable cards with sustainable daily load.
+
+## Daily Limits
+
+- New cards/day: `max 10` (default target: 3-10)
+- Review cards/day: no hard cap, but keep total study time under 20 minutes
+- If overload happens: reduce new cards first, never skip due reviews
+
+## Priority Queue for New Cards
+
+Create cards in this order:
+
+1. Current project-critical knowledge (`Projects`)
+2. Frequently used responsibility knowledge (`Areas`)
+3. Long-term leverage concepts (`Resources`)
+4. Nice-to-know trivia (only if capacity remains)
+
+## Intake Pipeline (Note -> Card)
+
+1. Pick up to 3 atomic notes from today's distillation.
+2. Score each note quickly:
+   - Impact (0-2): helps current projects or repeated decisions
+   - Frequency (0-2): likely reused this week
+   - Forget risk (0-2): easy to forget if not reviewed
+3. Convert highest scores first (max total new cards/day = 10).
+4. Postpone low-score notes to next day instead of forcing more cards.
+
+## Conversion Checklist
+
+For each atomic note:
+
+1. Keep one card for one testable idea.
+2. Prefer short answer or cloze over long text.
+3. Remove context that gives away the answer.
+4. Add source tag for traceability.
+5. Add topic tag for filtering (`project/*`, `area/*`, `resource/*`).
+
+## Card Formats
+
+### Q/A
+
+- Front: precise question
+- Back: one-sentence answer + optional example
+
+### Cloze
+
+- Sentence must be meaningful without extra paragraph context.
+- Hide one concept at a time.
+
+## Quality Standard
+
+- Answer length under 20 words when possible.
+- Each card should be answerable within 10 seconds.
+- If answer is ambiguous, split into multiple cards.
+
+## Weekly Tuning
+
+- Suspend low-value or repeated-failure cards with weak real-world relevance.
+- Merge duplicate cards.
+- Promote high-utility cards into a "core deck" tag.

docs/memory-system/templates/weekly-review.md

@@ -0,0 +1,35 @@
+# Weekly Review Template (30 minutes)
+
+- Review date: `<YYYY-MM-DD>`
+- Owner: `<name>`
+
+## 1) Inbox Zero (10 minutes)
+
+- [ ] Process all notes from `Inbox`
+- [ ] Convert valuable items into atomic notes
+- [ ] Delete low-value noise
+
+## 2) Linking and Structure (8 minutes)
+
+- [ ] Ensure each new atomic note links to at least one existing note
+- [ ] Add missing backlinks for key notes
+- [ ] Move notes to correct PARA container
+
+## 3) Archive and Cleanup (6 minutes)
+
+- [ ] Archive inactive project notes to `Archives`
+- [ ] Remove duplicate notes or cards
+- [ ] Mark stale resources for later refresh
+
+## 4) SRS Adjustment (6 minutes)
+
+- [ ] Check review backlog and adjust new card limit if needed
+- [ ] Keep next week new cards <= 10/day
+- [ ] Pick top 3 focus topics for next week
+
+## Weekly Output
+
+- One paragraph insight:
+  - `<what changed in understanding this week>`
+- One practical application next week:
+  - `<where to apply in writing/decision/coding>`

docs/memory-system/weekly-review-schedule.md

@@ -0,0 +1,29 @@
+# Weekly Review Schedule
+
+Run once per week, fixed to the same weekday and time block.
+
+- Recommended slot: Friday 17:30-18:00 (or any stable 30-minute slot)
+- Hard rule: do not skip two weeks in a row
+
+## Inputs
+
+- `Inbox/` captured items
+- New or edited notes in `Resources/`
+- Active materials in `Projects/` and `Areas/`
+- SRS backlog and daily new-card load
+
+## Execution
+
+Follow `templates/weekly-review.md` in order:
+
+1. Inbox Zero
+2. Linking and Structure
+3. Archive and Cleanup
+4. SRS Adjustment
+
+## Outputs
+
+- Updated links/backlinks in new atomic notes
+- Archived inactive items moved to `Archives/`
+- Next week focus topics (top 3)
+- Adjusted daily new-card limit (<= 10/day)