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
parent aff829a1e2
commit b182762e14
263 changed files with 1281 additions and 13 deletions
@@ -1,3 +1,6 @@
+---
+created: 2026-01-05
+---
 # The Methodology
 The P.A.R.A system is surprisingly simple at first glance but very powerful when applied. At its core, it's just a four folder wide hierarchy with four-layer deeps, starting with those four root folders:

@@ -1,3 +1,6 @@
+---
+created: 2026-01-05
+---
 ## Start here
 - General how-this-work
 - What to expect
@@ -1,3 +1,6 @@
+---
+created: 2026-01-05
+---
 # PKM Content Organization - Decision Note

 ## Analysis (2025-12-29)
@@ -1,3 +1,6 @@
+---
+created: 2026-01-05
+---
 # How to use this for work
 The workflow of P.A.R.A. is based on projects, as they are the most actionable information, but the information also flows in other ways. Most of the flowing and moving in the system will happen when you use the notes or when you are done with a project; that's why starting and finishing projects are crucial moments. As notes can flow to/from each part of the P.A.R.A, it's best to show with examples: