Q4 capacity model — early sketch
"Headcount-aware ship velocity, working assumptions only."
The notes you keep coming back to deserve a permanent place. The ones you don't deserve a graceful exit. Knovya watches the maturity signals — backlinks, NoteRank, edit cadence, age — and graduates the right ones for you. Andy Matuschak's philosophy. The system's discipline.
§ 2 — The Library
Three columns, one workspace, one weekly graduation pass. The notes on the left are still in motion. The notes in the middle have stopped moving — they earned the right to be considered. The notes on the right have graduated. Hit the run button and watch the candidates make their move.
Working 4
Active drafts and in-progress thinking. Edits are still landing.
Q4 capacity model — early sketch
"Headcount-aware ship velocity, working assumptions only."
Customer call · Acme Co · this Tue
"They asked about predictable releases."
Pricing tier rewrite v3 — outline
"Three tiers, hybrid usage cap, working through edge cases."
Hiring plan — open senior IC slots
"Three slots open, capacity-gap-prioritized."
Candidate 3
Completed and well-cited. Maturity signals stacked. Ready for the weekly check.
Q3 OKRs — leadership offsite
"Cross-team OKRs, finalized after the offsite."
Pricing tier review — April spike
"Three flat tiers, no usage caps. Tested for one cycle."
Senior IC retention study — 2024 cohort
"Stalled mid-tenure work weighted heavier than comp."
Evergreen 3
Graduated. Carries an outcome and an agent badge — your long-term reference shelf.
Auth security review · April
"7-day token rotation policy, replaces 30-day plan."
well-cited and consistently surfaced; load-bearing for the auth flow
Onboarding rewrite — v2
"Three-step flow, voice-first option, OAuth retry path."
matured over 90 days; some hypotheses landed, OAuth retry partial
Dual-pricing experiment · postmortem
"Both anchors hurt conversion. Documented as cautionary."
kept precisely because it failed; future plans on this shape get flagged
§ 3 — The anatomy
Every note in Knovya has a lifecycle. Most notes never reach the last stage — that's the point. The ones that do, do so for reasons the workspace can name. The ones that get archived earn an outcome that becomes precedent for future work.
3a · Lifecycle stages
A note's path from draft to long-term reference.
Draft
The early shape — first sketches, partial structure.
Active
The working phase — being edited, linked, used.
In-progress
The iteration phase — checklists in motion, decisions firming up.
Completed
The closure phase — the work is done, edits stabilized.
Evergreen
The long-term phase — load-bearing for future work, kept active.
3b · Outcomes when archived
The five categories that turn an archive into precedent.
Success
It worked. Stamp it as positive precedent — Experience Envelope will surface this as encouragement next time you face the same shape of problem.
Partial
It half-worked. Some hypotheses landed, some didn't. Stays useful as nuanced reference rather than clean evidence either way.
Cautionary
It failed. Worth keeping precisely because it failed — future plans on the same shape get flagged with the lesson.
Cancelled
It was abandoned before resolution. Not a failure — just dropped. Kept for traceability when someone asks "what happened to that?"
Superseded
It was replaced by a later version. The supersedes chain points to the successor — agentic memory walks it during temporal recall.
§ 4 — The problem
Scene 01
The manual evergreen practice — Andy Matuschak's five years, Maggie Appleton's seedling-to-evergreen garden — is admirable and effective. It's also a discipline almost nobody sustains for a quarter, let alone half a decade. The framing is right; the friction wins.
Scene 02
Notion, Obsidian, Roam, Logseq give you the buttons — archive, pin, tag with "evergreen." None of them carry an opinion about when. Every user reinvents their threshold every Monday, and most users abandon the practice within a quarter.
Scene 03
Apple Notes, Bear, Day One ship the archive button and stop there. No maturity intelligence, no outcome enrichment, no precedent record. Archiving means "I'm done with this" and nothing more.
The signals that distinguish a working note from a long-lived one are knowable — backlinks accumulate, NoteRank rises, edit cadence stabilizes, age compounds. Knovya watches the signals so the discipline doesn't have to be yours. The philosophy stays Andy's. The discipline becomes the system's.
§ 5 — Lineage
The idea that some notes are meant to last is older than the personal computer. Each milestone in the lineage is the same insight — that knowledge work needs a long-term reference layer — implemented with the technology of its time. Smart Archive is the first version where the curation runs on its own.
1960s—1990s
German sociologist Niklas Luhmann ran a Zettelkasten of 90,000 paper index cards, each one an atomic permanent note linked to others by hand. The first systematic evergreen practice; the foundation everyone after him cites.
2017
Sönke Ahrens' book formalizes Luhmann's method for the digital era — fleeting notes, literature notes, permanent notes — and makes "permanent notes" a term the broader knowledge-work audience knows.
2019—
notes.andymatuschak.org publishes a working notes site as a public artifact. Andy's evergreen-notes framing — atomic, declarative, statement-titled, evolving across projects — becomes the canonical reference for the modern PKM movement.
2020—
Maggie Appleton's digital garden establishes the seedling → budding → evergreen growth-stage metaphor and visualizes the maturity arc most note-takers feel intuitively but rarely encode.
2026
First automated evergreen curation. The maturity signals — backlinks, NoteRank, edit cadence, age — feed a daily graduation engine. Andy's philosophy. Maggie's growth stages. The system's discipline.
§ 6 — First mover
Andy Matuschak · Maggie Appleton · the manual practice
A discipline practiced by people who can sustain it. Five years of evergreen-note maintenance is admirable, rare, and not within reach for most knowledge workers managing a normal job alongside their note-taking.
Notion · Obsidian · Roam · Logseq
Buttons to archive, pin, tag — but no opinion about when, and no signal aggregation. Every user reinvents the threshold. Most users abandon the practice within a quarter; the buttons stay, the curation doesn't.
Apple Notes · Bear · Day One
Archive UI exists; maturity intelligence does not. Archiving means "done with it" and nothing else — no outcome stamp, no precedent record, no link back to future work.
Knovya — Smart Archive
Automated graduation from maturity signals plus outcome-stamped archive. The signals that distinguish a long-lived note from a transient one — watched daily, surfaced weekly, applied with your consent. The Andy Matuschak philosophy without the Andy Matuschak workload.
§ 7 — Surfaces
The library runs in the background. The surfaces are the touchpoints where you decide — daily suggestions, pre-archive impact previews, precedent banners on similar work, and the evergreen library itself.
Surface 01 · Daily inbox
Every morning, Smart Archive surfaces the notes whose maturity signals stacked overnight. You see three actions, one click each — graduate to evergreen, archive with an outcome, deprecate with a reason. Inbox-shaped, not settings-shaped.
Surface 02 · Pre-archive
Archiving isn't a one-click destruction — it's a lifecycle transition. Knovya shows the impact (dependent notes, backlinks, active shares) and asks for the outcome stamp before the move. The outcome becomes precedent, not just metadata.
Archive: "Pricing tier review · April spike"
Before this archives, here's what's connected:
Pick the outcome — feeds Experience Envelope:
Surface 03 · Precedent
When you start a new note that looks like one you've shipped before, a precedent banner surfaces the past outcome — Experience Envelope's read of which similar notes succeeded, partially landed, or went cautionary. Past work, applied to present work.
Surface 04 · The library
The evergreen library is a real workspace view. Filter by outcome to surface the success archive (what worked), the cautionary archive (what didn't), or the partial archive (what nuanced). The shelf you actually go back to.
§ 8 — Bonded with
The maturity signals come from somewhere. NoteRank weighs which notes are load-bearing. Experience Envelope reads the outcome stamps as precedent. Reflect's Crystals graduate naturally to evergreen. Knowledge Graph supplies the link density that distinguishes a working note from a long-lived one.
The ranking signal — Smart Archive watches NoteRank for graduation candidates.
Reads the outcome stamps as precedent — what's archived informs what's drafted.
Crystals are pre-graduated by definition — the AI synthesis lands as evergreen.
Backlink density is the clearest maturity signal — graph reads feed graduation.
Andy Matuschak ran his evergreen practice for five years. Maggie Appleton has tended hers for six. You won't. That's not a personal failure — that's how friction works. Knovya watches the signals so you don't have to remember to.
An evergreen note is a long-lived, declarative, atomic note that earns its place in your knowledge base because you keep coming back to it. The term was popularized by Andy Matuschak's working notes — short, statement-titled notes that evolve, contribute, and accumulate across projects rather than getting archived after one use. Maggie Appleton's digital-garden growth-stage metaphor calls them the final stage after seedling and budding. The practice predates the name: Niklas Luhmann's Zettelkasten slip-box ran on the same idea with index cards.
Knovya watches the signals that distinguish a working note from a long-lived one — how often it's edited, how many other notes link to it, whether NoteRank consistently surfaces it, how old it is, whether it's reached a closure status. When the signals stack up, the note becomes a graduation candidate; the daily archive-suggestions surface it for one-click acceptance, or the workspace can apply graduations automatically based on your settings.
Yes. Every lifecycle transition has a manual control — promote, archive, deprecate, restore — and your manual choice always overrides the system. The Smart Archive runs as a daily suggestion engine; you stay in charge of what graduates and what gets archived. Manual promotions skip the candidate phase entirely.
Archived means the work is done and the note is being kept for reference — it leaves the active workspace but stays searchable. Evergreen means the work is done AND the note is load-bearing for future work — it stays in the active workspace as a long-term reference. A failed experiment gets archived with a cautionary outcome; a successful pattern gets graduated to evergreen. Both keep their backlinks and supersedes chains intact.
Yes. Every graduation comes with a short qualitative reason — "well-cited and consistently surfaced," "matured over 60 days, edits stabilized," "linked from four downstream decisions." The reasons are natural-language summaries of the maturity signals; the underlying weights and thresholds stay internal because they're an implementation detail you don't need to argue with.
Smart Archive needs a few weeks of activity before its signal is reliable — there's no useful maturity score for a workspace that's three days old. Until then, you can promote notes manually; the daily suggestions become meaningful around the time the workspace itself does. Cold-start workspaces see manual lifecycle controls only; the suggestion engine activates as the signal accumulates.
Yes — workspace settings carry three knobs. You can leave Smart Archive in suggest-only mode (the system flags candidates, you accept manually), turn on auto-graduation for high-confidence cases (the system promotes, you can revert), or scope the whole feature to specific folders so a personal-projects folder stays manual while your work folder runs on autopilot.