Personal Knowledge Lifecycle Map

A worksheet for building a small capture-to-retrieval system around real, recurring anchors. Companion to A personal knowledge system that helps you retrieve, not hoard.

Step 1: Pick a small starting set of anchors

An anchor is a decision or output tied to a real task you can describe. Choose a small starting set you can test. Frequency and look-back period should match the task; if you cannot identify a past use, label the anchor experimental rather than treating it as a permanent capture category.

Anchor	Decision or output?	Last three times I needed it
1.
2.
3.

Step 2: Capture criteria per anchor

For each anchor, define what is worth keeping and what fields every note must have.

Anchor 1: ______________________

Worth capturing if: ______________________
Required fields: Source / Date / Why it mattered / Status (settled, evolving, exception)
Where it lives (one tool, not scattered): ______________________

Anchor 2: ______________________

Worth capturing if: ______________________
Required fields: Source / Date / Why it mattered / Status
Where it lives: ______________________

Anchor 3: ______________________

Worth capturing if: ______________________
Required fields: Source / Date / Why it mattered / Status
Where it lives: ______________________

Step 3: A task-derived retrieval test

For each anchor, define a target that fits the real decision or output, then try to find and use your most relevant existing note. A time target may be useful for a time-sensitive task, but no single duration is a universal measure of successful retrieval.

Anchor	Target and reason	Actual result	Correct/current item?	Unrelated data exposed?	Improvement
1.
2.
3.

If an anchor misses its chosen target, returns the wrong or stale item, or exposes unrelated data, investigate the capture and retrieval structure before adding more notes.

Step 4: Review trigger or schedule

Anchor	Review frequency	Next review date	What gets checked
1.			Accuracy, duplicates, delete unused
2.			Accuracy, duplicates, delete unused
3.			Accuracy, duplicates, delete unused

Step 5: Deletion rule

Check the boxes that apply to your system, and add your own:

Review momentary or time-sensitive material when its documented purpose expires.
Do not keep another person’s private information without a justified purpose and appropriate authority; minimise, protect, or delete it as required.
Review never-retrieved “just in case” notes against purpose-specific legal, tax, warranty, dispute, safety, archival, and personal needs before deleting them.
Other rule: ______________________

Sensitive-notes checklist

I have identified which of my three anchors could involve sensitive material (health, financial, relationship, disputes, another person’s information).
For sensitive anchors, I know the actual retention and deletion policy of the tool I use — not just assumed it is private because the account is personal.
For notes about another person, I asked myself whether they would be comfortable knowing I kept this record, at this level of detail.

Prompt to review a batch of notes

Here are my notes tagged for the anchor "[name it]":
[paste notes]

1. Flag anything that looks outdated, contradicted by a later note, or
   a one-off exception that should not be treated as a general rule.
2. Group near-duplicate notes and suggest which single version to keep.
3. For each note, ask me: would losing this change a future decision?
   If I say no, mark it for deletion.

Do not summarize the notes into new claims I have not made. Only
organize and flag what is already there.