Interactive graph
Note Maturity
Table of Contents
Notes pass stages from raw capture to trusted claim to archive - match effort to where the note actually sits.
Key Concept
- Match polish to stage - a seedling is not an evergreen, and forcing both speeds wastes time.
- Seedling: raw capture, tagged, dated - enough to find later.
- Budding: idea survived a second read; links start forming.
- Evergreen: claim you would cite next year; typed relationships wired.
- Archive: season ended; keep the record, stop daily maintenance.
- The Knowledge Lifecycle names capture through fade; Evergreen vs Fleeting Notes is the two-speed fork at the start.
Level 1 - Recognize
Note maturity is the stage a note sits in - seedling, budding, evergreen, or archive - and effort should match that stage.
Level 2 - Explain
Like a plant tray, garden bed, and compost pile - same garden, different jobs at each stage.
Level 3 - Use
Tag a new capture as seedling; promote to budding only when you would open it twice in one month.
Level 4 - Connect
Polishing every seedling burns time notes never repay - archive without shame when the project closed and the idea did not return.
Level 5 - Create
Build one promotion rule with Promote on Reuse and Periodic Knowledge Review - stages stay honest when the calendar asks.
Examples
- Glad the hot take about last night's game stayed on the fridge three weeks - I archived it instead of forcing evergreen polish.
- The safety rule we cite every quarter graduated from seedling to evergreen after the second near-miss made it real.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | Evergreen Notes | when stage-matched effort beats evergreen polish on every spark |
| extends | Evergreen vs Fleeting Notes | Two speeds at capture; maturity names the path between |
| extends | The Knowledge Lifecycle | Lifecycle tracks fade; maturity names the stages you file under |
| implements | Promote on Reuse | Promotion rule moves a note up one stage when reuse is real |
