Files

T

History

windyboy b182762e14 refactor(vault): Phase 3 — metadata convergence

- Backfill `created` frontmatter on 266 active notes (git date or mtime)
- Normalize `status` to 4 values: draft/active/done/archived (11 notes)
  - Active/进行中/needs-review → active
  - archive → archived
  - 待执行/conditional → draft
  - 完成/accepted → done
- Declare clipper boundary: 04_Archive/Inbox-Clippings/** exempt from migration
- Update depth rule: max 3 → max 4 levels (new notes only)
- Add metadata-converge.mjs script for reproducibility

2026-09-26 11:37:19 +08:00

..

refactor(vault): Phase 3 — metadata convergence

2026-09-26 11:37:19 +08:00

Home-Automation

refactor(vault): Phase 3 — metadata convergence

2026-09-26 11:37:19 +08:00

refactor(vault): Phase 3 — metadata convergence

2026-09-26 11:37:19 +08:00

refactor(vault): Phase 3 — metadata convergence

2026-09-26 11:37:19 +08:00

refactor(vault): Phase 3 — metadata convergence

2026-09-26 11:37:19 +08:00

README.md

refactor(vault): Phase 3 — metadata convergence

2026-09-26 11:37:19 +08:00

README.md

created

created
2025-09-13

Projects

Purpose: Time-bound initiatives with clear completion criteria.

What is a Project?

A project has:

A specific goal or deliverable
A clear end date or completion criteria
Multiple tasks or actions

Examples: Writing a paper, launching a product, planning an event, learning a new skill

Recommended Structure

For each project folder, create:

Research/ - Source materials and references
Drafts/ - Work in progress
Output/ - Final deliverables
README.md - Project objectives, timeline, and status

Project Lifecycle

Start: Create folder with subfolders and README
During: Keep all related materials in the project folder
Complete: Create summary note, then move to 04_Archive/

Active Project Folders

01_Projects/Personal-Tech/LLM_Evaluation/README

Tips

Link to relevant Areas and Resources
Commit regularly to track progress with git
Review weekly to check status and next actions