Spaced Review Knowledge Backlog

Template Overview

Writing notes is easy; maintaining a living, trustworthy knowledge garden over years requires deliberate pruning. Over time, facts change, early opinions evolve, and new connections emerge. The Spaced Review Knowledge Backlog organizes notes into structured review queues, tracks conceptual decay, and documents refinement logs in plain Markdown.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Spaced Review Backlog: [Current Month / Quarter]"
date_initiated: [YYYY-MM-DD]
vault_curator: "[[Your Name]]"
notes_in_active_queue: 20
notes_reviewed_this_cycle: 8
notes_graduated_to_evergreen: 3
notes_pruned_or_archived: 1
tags: [pkm, spaced-review, vault-maintenance, knowledge-audit, zettelkasten]
---

# Spaced Review Knowledge Backlog — [Current Quarter]

## 1. Review Objectives & Cadence Principles
- **Core Philosophy:** Treat the vault like a living orchard: water the fruitful branches, prune dead wood, and graft new insights.
- **Review Cadence:** Spend 20 minutes every Sunday morning reviewing 5 queued notes.
- **Graduation Criteria:** A note graduates to 'Evergreen' when its claims have withstood at least two reviews over 6 months without fundamental contradiction.

## 2. Active Spaced Review Queue
| Note Link | Date Created | Last Reviewed | Review Tier (Days) | Action Required | Status |
|---|---|---|---|---|---|
| [[Local Speech Models Outperform Server Latency]] | 2026-04-10 | 2026-07-12 | 90 Days | Update with M4 benchmark metrics | **Done** |
| [[The Limitations of Edge Quantization]] | 2026-05-18 | 2026-08-20 | 90 Days | Verify if Q4_K_M noise is still an issue | **In Review** |
| [[Memory Bandwidth as the Bottleneck of AI]] | 2025-10-02 | 2026-04-05 | 180 Days | Add 2026 unified memory figures | Queued |
| [[Early Thoughts on Cloud Sync Conflicts]] | 2024-08-12 | 2025-02-14 | 365 Days | Prune: Obsolete due to local CRDT engine | Queued |

## 3. Spaced Review Session Log
### Session Log: 2026-10-04 (Reviewed 3 Notes)
1. **[[Local Speech Models Outperform Server Latency]]:**
   - *Refinements Made:* Updated the note to reflect newly published Apple Silicon memory bandwidth benchmarks. Rewrote paragraph 2 to contrast local zero-latency audio buffering against cloud WebSocket packet jitter.
   - *Status:* Promoted maturity status from *Budding* to *Evergreen*.
2. **[[The Limitations of Edge Quantization]]:**
   - *Refinements Made:* Added wikilink to newly read NeurIPS 2026 paper on ternary weight quantization.
3. **[[Early Spec on Hybrid Cloud]]:**
   - *Decision:* **PRUNED & ARCHIVED.** Our commitment to 100% offline local processing rendered this hybrid proposal obsolete. Moved to `4_Archives/`.

## 4. Vault Health & Link Rot Audit
- [ ] Checked for dangling wikilinks using vault linter script.
- [ ] Verified that all newly reviewed notes link to at least one Map of Content (MOC).
- [ ] Confirmed zero duplicate tags in YAML frontmatter.

## 5. Review Retrospective & Insights
> [!NOTE] Reflection
> Reviewing notes written 6 months ago revealed how much our understanding of local inference has matured. What once felt like a speculative hypothesis is now proven engineering reality.

## 6. Action Items for Next Session
- [ ] Queue 5 notes from `03_PKM/` tagged `#systems-design`.
- [ ] Run automated orphaned-note scan across vault.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Review Backlog: October 2026"
date_initiated: 2026-10-01
vault_curator: "[[Elena Rostova]]"
notes_in_active_queue: 15
notes_reviewed_this_cycle: 5
tags: [pkm, review]
---

# Spaced Review Knowledge Backlog — October 2026

## 1. Summary
Elena Rostova audited 5 notes on cryptographic zero-knowledge proofs.

## 2. Key Action
Updated 3 notes with references to 2026 post-quantum lattice cryptography standards and deleted one duplicate note, maintaining a tight, high-signal vault.

When to Use and When to Avoid

When to Use

• Use during weekly or monthly vault maintenance rituals to revisit older notes.
• Use to graduate emerging seedlings into robust permanent evergreen notes.
• Use to ruthlessly prune obsolete hypotheses, broken links, and duplicate files.

When to Avoid

• Avoid using during fast real-time note capture during live meetings.
• Avoid turning this into an anxiety-inducing backlog (review only 3-5 notes at a time).

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the list of vault notes with creation and last-modified dates:
1. Identify notes due for spaced review based on 30, 90, 180, and 365-day intervals.
2. Flag potential conceptual decay or outdated claims requiring empirical updates.
3. Generate a structured Spaced Review Knowledge Backlog in Markdown with action items.

Your data remains securely on your Mac with zero cloud exposure.