Free tool · works now

Note maintenance checklist builder

Plan conservative, human-reviewed vault cleanups with strict stop conditions and zero automatic deletion.

Conservative Vault Maintenance Planner

Generate an actionable, prioritized maintenance schedule based on verified issue counts, backup status, and cognitive time budgets.

Zero Cloud TelemetryNo Auto-DeletionStop Conditions Enforced
Identifies the target knowledge repository in generated reports.
If unverified, destructive restructuring & archival tasks are automatically locked.
Caps task volume to prevent cognitive fatigue and accidental deletions.
Filter checklist items according to your immediate cleanup objective.

Verified Vault Audit Counts

Enter the number of detected issues from your vault health reports. Values are used to estimate review duration and prioritize risk tiers.

Non-existent targets
0 inbound backlinks
Unreferenced files
Exact / near collisions
Syntax errors in properties
NFD / Unicode / reserved
Case / synonym variants
< 50 words
Analyzed notes
Excluded folders
Total Tasks9
Est. Time~142m
Scan Coverage88%
High-Risk Tasks1
Locked Tasks0

Mandatory Safety Stop Conditions

  • 🛑 UNSCANNED MATERIAL GUARD: 60 notes or folders were excluded from the scan. The engine refuses to assume unscanned materials are clean or orphaned. Do not delete cross-folder links or shared assets.
  • 🛑 FATIGUE BOUNDARY: Never review more than 30 notes in a single maintenance pass. Decision fatigue causes accidental deletions of valuable early drafts.
# Vault Maintenance Plan: Personal Research Vault
**Generated:** 2026-11-19
**Backup Status:** ✅ Verified External Backup
**Scan Coverage:** 420 scanned / 60 unscanned (88% coverage)
**Estimated Maintenance Time:** ~142 minutes

## Mandatory Stop Conditions
- 🛑 **UNSCANNED MATERIAL GUARD: 60 notes or folders were excluded from the scan. The engine refuses to assume unscanned materials are clean or orphaned. Do not delete cross-folder links or shared assets.**
- 🛑 **FATIGUE BOUNDARY: Never review more than 30 notes in a single maintenance pass. Decision fatigue causes accidental deletions of valuable early drafts.**

## Prioritized Review Checklist
### [ ] Step 1: Verify Off-Vault Snapshot / Git Commit (5m · 🟢 LOW RISK)
- **Category:** Safety Preflight
- **Action:** Ensure a full, separate backup (Time Machine, external drive, or committed Git branch) exists before beginning any maintenance.
- **Safe Procedure:** Run git status or duplicate the vault folder into an archive directory before making changes.
- **Verification Question:** *Have you verified that yesterday’s or today’s snapshot exists on a separate storage volume?*
- **Stop Condition:** ⚠️ Stop immediately if no secondary copy exists.

### [ ] Step 2: Triage 14 Broken Wikilinks (21m · 🟡 MODERATE)
- **Category:** Link Health
- **Action:** Audit wikilinks pointing to non-existent notes. Determine whether the target note was renamed, never created, or deleted.
- **Safe Procedure:** Create a placeholder stub note for missing targets or update the link to point to the correct renamed note. Never remove links blindly.
- **Verification Question:** *Does the missing destination warrant a new stub note, or was the target filename misspelled?*
- **Stop Condition:** ⚠️ If more than 15 broken links share a common path prefix, check if a folder was moved rather than editing links individually.

### [ ] Step 3: Correct 7 Malformed YAML Frontmatter Headers (14m · 🟢 LOW RISK)
- **Category:** Metadata Integrity
- **Action:** Repair unclosed YAML delimiters (---), illegal tab characters, or unquoted colons in note properties.
- **Safe Procedure:** Replace raw tab characters with two spaces and wrap string values containing colons in double quotes.
- **Verification Question:** *Check that YAML keys match your vault taxonomy schema without removing valuable metadata.*
- **Stop Condition:** ⚠️ Do not bulk-strip unparsed YAML blocks; manually review custom Dataview fields.

### [ ] Step 4: Normalize 4 Unicode & Illegal Filenames (8m · 🟡 MODERATE)
- **Category:** Filesystem Portability
- **Action:** Resolve NFD vs NFC character decompositions, illegal Windows characters (\, :, *, ?, ", <, >, |), or Cyrillic homoglyphs.
- **Safe Procedure:** Rename files through your note editor interface rather than the operating system Finder/Terminal to preserve link graph integrity.
- **Verification Question:** *Verify whether your note app automatically updates backlinks across the vault when a note is renamed.*
- **Stop Condition:** ⚠️ If your editor does not support automated backlink refactoring, stop and plan a staged rename script.

### [ ] Step 5: Harmonize 12 Tag Variants & Case Collisions (18m · 🟢 LOW RISK)
- **Category:** Taxonomy Review
- **Action:** Identify casing discrepancies (#project vs #Project) and synonymous tag clusters (#todo vs #task).
- **Safe Procedure:** Review tag occurrences in context before merging. Prefer converting ambiguous tags into structured wikilink MOCs.
- **Verification Question:** *Are these tags genuinely synonymous, or does one convey a distinct sub-context or workflow state?*
- **Stop Condition:** ⚠️ Never automatically merge tags with distinct semantic definitions without inspecting sample notes.

### [ ] Step 6: Manually Review 5 Suspected Duplicate Notes (20m · 🟡 MODERATE)
- **Category:** Synthesis & Merging
- **Action:** Compare near-duplicate notes created by filesystem transfer conflicts, multi-device imports, or duplicate capture prompts.
- **Safe Procedure:** Combine unique ideas into the canonical note, verify backlinks point to canonical target, then safely move the duplicate to an _archive folder.
- **Verification Question:** *Does note B contain unique marginalia, newer timestamps, or alternative backlinks not present in note A?*
- **Stop Condition:** ⚠️ NEVER delete duplicate notes permanently on disk. Always retain an archive folder until the end of the year.

### [ ] Step 7: Assess 16 Stub Notes (< 50 Words) (20m · 🟢 LOW RISK)
- **Category:** Content Maturation
- **Action:** Review stub notes containing only a heading or single bullet. Determine if they should be expanded, linked to an MOC, or tagged #seedling.
- **Safe Procedure:** Add a two-sentence definition or tag with #seedling. Do not delete stub notes that hold incoming backlinks from other ideas.
- **Verification Question:** *Is this stub note an intentional placeholder for future research or an accidental leftover from quick capture?*
- **Stop Condition:** ⚠️ If a stub note has 2+ incoming backlinks, it serves an active structural purpose in your knowledge graph.

### [ ] Step 8: Integrate 9 Orphan Notes (0 Inbound Links) (18m · 🟡 MODERATE)
- **Category:** Network Integration
- **Action:** Connect isolated notes to high-level index notes (Maps of Content) or tag them by project/discipline.
- **Safe Procedure:** Add a reciprocal link to an appropriate index or dashboard note. Do not categorize unlinked notes as low quality.
- **Verification Question:** *What broader topic or project does this note inform? Can it be linked from an index note?*
- **Stop Condition:** ⚠️ Never purge notes merely because they lack inbound links; exploratory thinking often begins in isolation.

### [ ] Step 9: Archive 18 Unused Attachments to Quarantine (18m · 🔴 HIGH RISK)
- **Category:** Storage Review
- **Action:** Audit media files (.png, .pdf, .mp3) that have zero markdown link references in the scanned notes.
- **Safe Procedure:** Move unreferenced attachments to a designated _quarantine/attachments/ folder rather than deleting them permanently.
- **Verification Question:** *Is this attachment referenced by an unscanned folder, canvas board, or external project file?*
- **Stop Condition:** ⚠️ MANDATORY STOP CONDITION: Never run automated deletion scripts. If backup is unverified or unscanned notes exist, quarantine is postponed.
StepTask TitleCategoryRisk TierEst. TimeStatus
#1Verify Off-Vault Snapshot / Git CommitSafety PreflightLow Risk~5mReady
#2Triage 14 Broken WikilinksLink HealthModerate~21mReady
#3Correct 7 Malformed YAML Frontmatter HeadersMetadata IntegrityLow Risk~14mReady
#4Normalize 4 Unicode & Illegal FilenamesFilesystem PortabilityModerate~8mReady
#5Harmonize 12 Tag Variants & Case CollisionsTaxonomy ReviewLow Risk~18mReady
#6Manually Review 5 Suspected Duplicate NotesSynthesis & MergingModerate~20mReady
#7Assess 16 Stub Notes (< 50 Words)Content MaturationLow Risk~20mReady
#8Integrate 9 Orphan Notes (0 Inbound Links)Network IntegrationModerate~18mReady
#9Archive 18 Unused Attachments to QuarantineStorage ReviewHigh Risk~18mReady
Priority,Title,Category,Risk Tier,Est Minutes,Locked By Backup,Safe Procedure,Stop Condition
1,"Verify Off-Vault Snapshot / Git Commit","Safety Preflight","low-risk",5,"No","Run git status or duplicate the vault folder into an archive directory before making changes.","Stop immediately if no secondary copy exists."
2,"Triage 14 Broken Wikilinks","Link Health","moderate-risk",21,"No","Create a placeholder stub note for missing targets or update the link to point to the correct renamed note. Never remove links blindly.","If more than 15 broken links share a common path prefix, check if a folder was moved rather than editing links individually."
3,"Correct 7 Malformed YAML Frontmatter Headers","Metadata Integrity","low-risk",14,"No","Replace raw tab characters with two spaces and wrap string values containing colons in double quotes.","Do not bulk-strip unparsed YAML blocks; manually review custom Dataview fields."
4,"Normalize 4 Unicode & Illegal Filenames","Filesystem Portability","moderate-risk",8,"No","Rename files through your note editor interface rather than the operating system Finder/Terminal to preserve link graph integrity.","If your editor does not support automated backlink refactoring, stop and plan a staged rename script."
5,"Harmonize 12 Tag Variants & Case Collisions","Taxonomy Review","low-risk",18,"No","Review tag occurrences in context before merging. Prefer converting ambiguous tags into structured wikilink MOCs.","Never automatically merge tags with distinct semantic definitions without inspecting sample notes."
6,"Manually Review 5 Suspected Duplicate Notes","Synthesis & Merging","moderate-risk",20,"No","Combine unique ideas into the canonical note, verify backlinks point to canonical target, then safely move the duplicate to an _archive folder.","NEVER delete duplicate notes permanently on disk. Always retain an archive folder until the end of the year."
7,"Assess 16 Stub Notes (< 50 Words)","Content Maturation","low-risk",20,"No","Add a two-sentence definition or tag with #seedling. Do not delete stub notes that hold incoming backlinks from other ideas.","If a stub note has 2+ incoming backlinks, it serves an active structural purpose in your knowledge graph."
8,"Integrate 9 Orphan Notes (0 Inbound Links)","Network Integration","moderate-risk",18,"No","Add a reciprocal link to an appropriate index or dashboard note. Do not categorize unlinked notes as low quality.","Never purge notes merely because they lack inbound links; exploratory thinking often begins in isolation."
9,"Archive 18 Unused Attachments to Quarantine","Storage Review","high-risk",18,"No","Move unreferenced attachments to a designated _quarantine/attachments/ folder rather than deleting them permanently.","MANDATORY STOP CONDITION: Never run automated deletion scripts. If backup is unverified or unscanned notes exist, quarantine is postponed."

The Architecture of Safe Vault Maintenance: Stop Conditions and Quarantine Systems

In personal knowledge management (PKM), digital entropy is inevitable. Over months and years of active writing, research synthesis, and rapid web clipping, knowledge vaults accumulate broken wikilinks, dangling media files, conflicting tag hierarchies, and ambiguous duplicate notes. In response to this friction, many software tools propose automated "one-click vault cleaners" or aggressive deletion scripts that silently scan directories and purge files.

These automated cleaners represent an extreme hazard to personal knowledge. In plain-text Markdown systems, a note that appears unreferenced may actually represent an embryonic research idea, a deliberate placeholder, or an asset embedded within an unscanned canvas board or script. Our Master Plan (§TOOL-074) mandates that vault maintenance must adhere to two absolute engineering principles: zero automatic deletion and complete refusal of certainty regarding unscanned material.

1. The Catastrophe of Automated Vault Cleaners

Automated cleaning utilities typically rely on simplistic pattern-matching scripts (such as finding all image files with zero markdown link matches and invoking rm). This approach routinely triggers catastrophic data loss due to several architectural blind spots:

2. Borrowing Stop Conditions from High-Reliability Engineering

High-reliability organizations (such as commercial aviation, nuclear engineering, and trauma surgery) operate under complex, ambiguous environments where errors have severe consequences. Rather than relying solely on checklists that instruct workers on what actions to take, safety-critical workflows incorporate Stop Conditions: unambiguous operational triggers that mandate an immediate halt to all forward activity until a safety condition is resolved.

The Note Maintenance Checklist Builder introduces three non-negotiable stop conditions for knowledge bases:

  1. The Backup Preflight Stop Condition: If the user cannot confirm that an external, independent backup (e.g., Apple Time Machine, an offline external drive snapshot, or a pushed Git commit) exists, the engine locks all archival, deduplication, and bulk rename steps. Zero restructuring is permitted until disaster recovery is guaranteed.
  2. The Unscanned Material Guard: If a subset of the vault was excluded from the audit (for example, a large PDF archive, a vendor documentation directory, or a private client folder), the engine prohibits marking unreferenced assets as expendable. The existence of unscanned material mathematically destroys the assumption that an attachment is unreferenced.
  3. The Cognitive Fatigue Boundary: Evaluating whether two notes represent duplicates or deciding whether an orphan note should be linked to an index note requires intense semantic judgment. After 25 to 30 consecutive decisions, human mental fatigue induces "confirmation blindness," causing writers to click "archive" or "merge" prematurely. The checklist enforces strict batch limits to preserve judgment quality.

3. The Quarantine Pattern: Non-Destructive Archival vs Permanent Deletion

When an attachment or note appears to be truly redundant, the safe procedure is never permanent deletion. Instead, the engine specifies the Quarantine Pattern.

Suspected unused attachments are moved into an isolated, internal folder designated as _quarantine/attachments/YYYY-MM/. This approach preserves the filesystem inode and timestamp metadata while removing the file from everyday search views. The quarantine directory is preserved for a grace period of 90 days. If, during that quarter, no canvas board breaks, no Dataview query throws a missing reference error, and no project reports a missing diagram, the user can safely archive the folder to cold storage. If a broken reference does surface, restoring the asset is a simple one-click drag operation.

4. Risk Stratification: Staging Maintenance from Safe to Sensitive

A successful maintenance session must never tackle the most dangerous restructuring tasks first. Our engine stages maintenance across three risk tiers:

5. Formula Injection Protection and Spreadsheet Safety

Vault maintenance schedules are frequently exported to spreadsheet software (such as Excel or Google Sheets) for team auditing or multi-week tracking. If a task description or note title begins with characters like =, +, -, or @ (common in mathematics or task shorthand), spreadsheet applications can interpret them as executable dynamic formulas. Our CSV generator automatically sanitizes every exported field with single-quote escaping, guaranteeing safe, inert spreadsheet rendering across all operating systems.

6. Zero Telemetry and Local-First Privacy

Your knowledge vault contains personal reflections, unreleased intellectual property, confidential company strategies, and private research notes. Cloud-based vault cleaners often require uploading folder structures and file names to remote servers. The Note Maintenance Checklist Builder runs entirely client-side. No note titles, folder inventories, or maintenance counts are ever transmitted over the network.

7. Managing Bi-Directional Link Integrity During Note Renames & Slugification

One of the most delicate operations in vault maintenance involves renaming notes to repair malformed Unicode strings, resolve casing collisions, or normalize title slugs. In naive folder cleanups, users frequently rename files directly via the operating system shell or file explorer (e.g., using mv old_note.md new_note.md).

This filesystem-level rename instantly shatters every incoming wikilink ([[old_note]]) across the rest of the vault, transforming dozens of functional cross-references into broken targets. When performing filename cleanups:

8. The Seedling & Evergreen Note Life Cycle: Why Stub Notes Are Assets, Not Waste

Automated vault cleaning utilities frequently treat stub notes (files with fewer than 50 words) as "garbage" and recommend their outright deletion. This reflects a profound misunderstanding of the Zettelkasten and Evergreen note methodologies.

In a mature thinking environment, a stub note frequently serves as an indispensable structural anchor:

9. Long-Term Vault Architecture: Annual Snapshot Rituals and Cold Storage Tiering

Maintaining a multi-year personal knowledge base requires distinguishing between active working memory and archival reference material. As projects conclude and academic terms finish, attempting to keep every historical meeting log and draft in your active search index degrades search speed and clutters graph visualizations.

Establish a recurring quarterly maintenance ritual:

  1. Freeze Completed Project Folders: Move concluded client engagements or completed research papers into an _archive/YYYY/ directory. Mark the root note of the project with a frontmatter status of status: archived.
  2. Export Verified Snapshots: Once per quarter, create a compressed tarball or zip archive of your entire vault directory and transfer it to redundant, read-only storage (such as an encrypted external SSD or cold cloud storage).
  3. Maintain Permanent Inode Stability: By relying on the Quarantine Pattern and periodic cold storage tiering, your daily working vault remains lean, fast, and free of digital clutter—without ever risking the accidental destruction of your irreplaceable intellectual work.

Questions

Why does this tool strictly prohibit automatic deletion commands?

Automated vault cleaning scripts that run background "rm" or delete commands are notorious for causing irreversible data loss. A note or attachment identified as "orphaned" may be intentionally isolated, referenced inside an unscanned canvas board, or linked from an external script. Our tool generates human-reviewed review checklists and safe quarantine procedures (_quarantine/), ensuring you never destroy valuable intellectual work.

What is a "Stop Condition" in personal knowledge management?

Borrowing from high-reliability engineering, a stop condition is an explicit trigger that halts maintenance operations immediately. For example, if your external backup is unconfirmed, all restructuring and archival tasks are locked. If you discover that multiple broken links share an identical prefix, the stop condition halts individual link edits to prevent wasting time on a moved folder.

Why does the tool refuse to assume certainty about unscanned material?

If your vault contains excluded directories (such as archive folders, raw PDF attachments, or private work projects), an attachment that appears unreferenced in scanned notes might be actively transcluded in an excluded folder. The engine explicitly flags unscanned materials and refuses to mark unreferenced assets as expendable without cross-folder verification.

How does the tool prevent cognitive fatigue during large cleanups?

Reviewing dozens of ambiguous notes requires sustained semantic evaluation. Cognitive fatigue inevitably causes note-takers to click "delete" or "merge" without careful scrutiny. The tool enforces session boundaries (capping reviews to 20–30 decisions) and stratifies tasks into low-risk metadata fixes versus high-risk archival steps.

Are my vault metrics, folder names, or note contents transmitted to cloud servers?

Never. The entire checklist compiler, risk stratification matrix, and Markdown/CSV exporters execute 100% locally in your browser memory. Zero vault metadata leaves your device.

Maintain Your Knowledge Vault with Confidence on Oyma

Keep your Markdown notes healthy, clean, and durable without surrendering your private files to destructive automated scripts.

tools note maintenance checklist builder downloadDownload for Mac

No account needed. Intel Mac build